Socket Readers

Currently using WebLogic 6.1 SP2 on Win NT 4.0 with jdk 1.3.1. 2 servers in a cluster.
The following message is seen.
<ExecuteThread: '10' for queue: 'default'> <> <> <000000> <There are: '7' active
sockets, but the maximum number of socket readers allowed by the configuration
is: '6', you may want to alter your configuration.>
How do we ensure our configuration is correct? Whenever this message is seen and
the servers need to start. If we do not restart them, after a while they will
hang and we need to restart them. Is there any way to resolve this issue? Thanks.

Hi,
Thanks for your info on Native IO.
There is a JVM error message thrown when we are trying to do the thread dump.
From the JDK website, we realise it is a bug for jdk 1.3.1. Thanks.
Regards,
Ai Ling
Arunabh Hazarika <[email protected]> wrote:
When native i/o is used, there are a fixed number of threads that are
dedicated to reading
incoming requests from clients. These threads are non-blocking i.e. they
do not block
waiting for data to arrive at a socket. When using Java i/o, the threads
block waiting for
data to arrive at a socket. In this case, if the number of sockets opened
is greater than
the number of threads available to read them, data on the remaining sockets
will remain
unread, until a thread becomes available to read it and response time
will increase. This is
basically what the message means.
It is not surprising that performance has degraded by turning off native
i/o. The message is
not the problem - turning off native i/o is.
I do not recall there being a problem with taking thread dumps with JDK
1.3.1 - what
indicates that the thread dump is not complete?
Arunabh
apple wrote:
Hi Arunabh,
Is this message critical? As we encounter this message, the server'sperformance
is very slow. Without this message, the access to the server is muchfaster. We
will like to know whether we can ignore this message or this messagehas any implication
to our servers.
As for your proposal to enable the native io and take thread dump,we have already
done that. But due to our jdk version used, we are not able to getthe full thread
dump.
Thanks.
Regards,
apple
Arunabh Hazarika <[email protected]> wrote:
To answer your second message first, yes, this message comes when
native
i/o is
disabled. For the first problem, I am not sure how disabling nativeio
would help
resolve a server hang - Please take a thread dump when the serverhangs
with native
i/o enabled and post it here.
Thanks,
Arunabh
apple wrote:
Hi Arunabh,
Our application server will use up the threads very fast and not
releasing
them
after usage, causing our servers to hang once we enable native io.Thus we have
no choice but to disable the native io. Is there any resolution
for
this? Is it
due to we disable native io which cause the following message to
appear?
<ExecuteThread: '10' for queue: 'default'> <> <> <000000> <Thereare:
'7' active
sockets, but the maximum number of socket readers allowed by the
configuration
is: '6', you may want to alter your configuration.>
Thanks for your prompt reply.
Regards,
Apple
Arunabh Hazarika <[email protected]> wrote:
It looks like you have native io disabled. Is there a reason why?
Arunabh
apple wrote:
Currently using WebLogic 6.1 SP2 on Win NT 4.0 with jdk 1.3.1.
2
servers
in a cluster.
The following message is seen.
<ExecuteThread: '10' for queue: 'default'> <> <> <000000> <There
are:
'7' active
sockets, but the maximum number of socket readers allowed by
the
configuration
is: '6', you may want to alter your configuration.>
How do we ensure our configuration is correct? Whenever this
message
is seen and
the servers need to start. If we do not restart them, after a
while
they will
hang and we need to restart them. Is there any way to resolve
this
issue? Thanks.

Similar Messages

  • Error message when access WLS: active sockets and socket readers configuration

    Hi,
    I got the following error when I tried to access the WLS using a program to get
    the mbeans data.
    This error happens when I have 3 or more servers running ( 1 admin server, 2 or
    more managed servers). With cluster with more than 2 servers running, this error
    also occurs.
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    I creased the socket readers from 33% to 66%, but I still got the same error.
    I'm using WLS version 6.0 sp2
    My configuration is:
    Execute Threads = 15,
    Socket Readers = 33% or 66%
    Does anyone know how to fix this ? I am really appreciate for any suggestions.
    thanks,
    Kieu

    thank you, I just found out about setting those sockets using command line options
    an hour ago. But thanks a lot.
    -Kieu
    Kaye Wilcox <[email protected]> wrote:
    Kieu,
    You could try increasing the number of execute threads, you can do this
    via
    the admin console on the <server> --> Tuning tab.
    See http://edocs.bea.com/wls/docs60/perform/WLSTuning.html#1104317 for
    guidelines on setting the thread pool size and the number of socket readers.
    Here is a link that talks about socket communication in a cluster
    http://edocs.bea.com/wls/docs60/cluster/features.html#1007001.

  • Identifying Execute Queue Threads as Socket Readers

    Hi All,
    Preface: I am trying to identify at any given instance the percentage of
    socket reader threads that are in use - this will help me to identify when
    all threads are in use and unable to service user requests. Thus my goal is
    to identify threads that are socket readers and whether they are active or
    idle.
    Through JMX I can obtain an instance of each
    weblogic.management.runtime.ExecuteThread, which lists the same information
    that you see in the console if you drill down to the thread level, for
    example:
    mydomain> Servers> myserver> Active Execute Queues> default> Execute Threads
    That information includes:
    - thread number
    - total requests
    - last request
    - current request
    - transaction
    - user
    - is the thread idle?
    Now my question is from this information can you identify which of these
    threads are being used as socket readers?
    Here are some excerpts from my JMX calls:
    Name: ExecuteThread: '0' for queue: 'default'
    Execute Queue Runtime Name: default
    Current Request: null
    Last Request: Http Request: /bookstore/en/authors/showauthors.jsp
    User: null
    Is Idle?: true
    Name: ExecuteThread: '15' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: null
    Last Request: Scheduled Trigger
    User: null
    Is Idle?: true
    Name: ExecuteThread: '26' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: null
    Last Request: ListenRequest for a new connection on: 'Socket
    addr=127.0.0.1,port=2061,localport=7001]'
    User: null
    Is Idle?: true
    Name: ExecuteThread: '59' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: Socket Reader Request
    Last Request:
    weblogic.transaction.internal.ServerCoordinatorDescriptor$2@138786
    User: null
    Is Idle?: false
    It would appear that the "ListenRequest" last request would identify a
    socket reader, only I have 60 threads in my default execute queue with 70%
    dedicated to socket readers and the number of threads that say their last
    request was "ListenRequest ..." is only 5.. Furthermore there is only one
    "Socket Reader Request" identified thread.
    Are threads identified as socket readers permanently or constantly reused
    for whatever purpose is required (with a cap of use based off of the socket
    reader perspective)?
    Thanks in advance for your help!
    Steve

    Hi Achhi,
    Socket Reader Threads are the Threads which are responsible for reading the incoming request data. We can divide the Socket reader threads in two categories:
    Pure Java Socket Reqders: The pure-Java socket reader implementation, where the socket reader threads continually poll all opened sockets to determine whether they contain data to be read, even if the sockets have no data to read. (From Performance Point This is Not Good that the Sockets will be in Opened Mode even if there is no Data to read)
    Native Socket Readers: (These are the Dafault Socket Readers) The native IP socket reader provided by the host machine's operating system, where the socket reader threads target only active sockets that contain data to be read. Native socket readers never poll sockets because they are immediately notified when a socket needs to be serviced. For Better Performance You should always prefer using Native Socket Readers.
    To Enable Native Socket Readers You can Login to AdminConsole--->Servers ---><SERVER_NAME>--->configuration (Tab)--->Tuning (SubTab)---> "Enable Native IO" (This checkbox must be checked)
    Still If you want to use the Java Socket Readers .... still you can improve the performance of socket communication by configuring the proper number of socket reader threads for each server instance. For best performance, the number of socket reader threads in WebLogic Server should equal the potential maximum number of opened sockets.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Identifying Execute Threads as Socket Readers

    Hi All,
    Preface: I am trying to identify at any given instance the percentage of
    socket reader threads that are in use - this will help me to identify when
    all threads are in use and unable to service user requests. Thus my goal is
    to identify threads that are socket readers and whether they are active or
    idle.
    Through JMX I can obtain an instance of each
    weblogic.management.runtime.ExecuteThread, which lists the same information
    that you see in the console if you drill down to the thread level, for
    example:
    mydomain> Servers> myserver> Active Execute Queues> default> Execute Threads
    That information includes:
    - thread number
    - total requests
    - last request
    - current request
    - transaction
    - user
    - is the thread idle?
    Now my question is from this information can you identify which of these
    threads are being used as socket readers?
    Here are some excerpts from my JMX calls:
    Name: ExecuteThread: '0' for queue: 'default'
    Execute Queue Runtime Name: default
    Current Request: null
    Last Request: Http Request: /bookstore/en/authors/showauthors.jsp
    User: null
    Is Idle?: true
    Name: ExecuteThread: '15' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: null
    Last Request: Scheduled Trigger
    User: null
    Is Idle?: true
    Name: ExecuteThread: '26' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: null
    Last Request: ListenRequest for a new connection on: 'Socket
    addr=127.0.0.1,port=2061,localport=7001]'
    User: null
    Is Idle?: true
    Name: ExecuteThread: '59' for queue: 'default'
    Execute Queue Runtime Name:default
    Current Request: Socket Reader Request
    Last Request:
    weblogic.transaction.internal.ServerCoordinatorDescriptor$2@138786
    User: null
    Is Idle?: false
    It would appear that the "ListenRequest" last request would identify a
    socket reader, only I have 60 threads in my default execute queue with 70%
    dedicated to socket readers and the number of threads that say their last
    request was "ListenRequest ..." is only 5.. Furthermore there is only one
    "Socket Reader Request" identified thread.
    Are threads identified as socket readers permanently or constantly reused
    for whatever purpose is required (with a cap of use based off of the socket
    reader perspective)?
    Thanks in advance for your help!
    Steve

    Hi Achhi,
    Socket Reader Threads are the Threads which are responsible for reading the incoming request data. We can divide the Socket reader threads in two categories:
    Pure Java Socket Reqders: The pure-Java socket reader implementation, where the socket reader threads continually poll all opened sockets to determine whether they contain data to be read, even if the sockets have no data to read. (From Performance Point This is Not Good that the Sockets will be in Opened Mode even if there is no Data to read)
    Native Socket Readers: (These are the Dafault Socket Readers) The native IP socket reader provided by the host machine's operating system, where the socket reader threads target only active sockets that contain data to be read. Native socket readers never poll sockets because they are immediately notified when a socket needs to be serviced. For Better Performance You should always prefer using Native Socket Readers.
    To Enable Native Socket Readers You can Login to AdminConsole--->Servers ---><SERVER_NAME>--->configuration (Tab)--->Tuning (SubTab)---> "Enable Native IO" (This checkbox must be checked)
    Still If you want to use the Java Socket Readers .... still you can improve the performance of socket communication by configuring the proper number of socket reader threads for each server instance. For best performance, the number of socket reader threads in WebLogic Server should equal the potential maximum number of opened sockets.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Threads as Socket Readers

    What does mean by Socket Readers?
    How it improves the performance of Application by configuring percentage of threads as socket readers?
    Can someone please answer my questions?

    Hi Achhi,
    Socket Reader Threads are the Threads which are responsible for reading the incoming request data. We can divide the Socket reader threads in two categories:
    Pure Java Socket Reqders: The pure-Java socket reader implementation, where the socket reader threads continually poll all opened sockets to determine whether they contain data to be read, even if the sockets have no data to read. (From Performance Point This is Not Good that the Sockets will be in Opened Mode even if there is no Data to read)
    Native Socket Readers: (These are the Dafault Socket Readers) The native IP socket reader provided by the host machine's operating system, where the socket reader threads target only active sockets that contain data to be read. Native socket readers never poll sockets because they are immediately notified when a socket needs to be serviced. For Better Performance You should always prefer using Native Socket Readers.
    To Enable Native Socket Readers You can Login to AdminConsole--->Servers ---><SERVER_NAME>--->configuration (Tab)--->Tuning (SubTab)---> "Enable Native IO" (This checkbox must be checked)
    Still If you want to use the Java Socket Readers .... still you can improve the performance of socket communication by configuring the proper number of socket reader threads for each server instance. For best performance, the number of socket reader threads in WebLogic Server should equal the potential maximum number of opened sockets.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Increasing max number of socket readers on client

    How can you increase the number of socket readers on a client
              application which
              uses JMS, EJB and talks to multiple WLAS servers.
              I get the following message
              Muxer> <There are: '3' active sockets, but the maximum number of socket
              readers allowed by theconfiguration is: '2', you may want alter your
              configuration.>
              But I cant find out how to increase the socket readers or better yet can
              I use the native IO for Solaris and NT clients??
              

    Try to use the WebItem Parameter "MAX_TEXT_LINES":
    <object>
    <param name="OWNER" value="SAP_BW"/>
    <param name="CMD" value="GET_ITEM"/>
    <param name="NAME" value="DOCUMENT_1"/>
    <param name="ITEM_CLASS" value="CL_RSR_WWW_ITEM_DOC"/>
    <param name="DATA_PROVIDER" value="DATAPROVIDER_1"/>
    <b><param name="MAX_TEXT_LINES" value="50"/></b>
    ITEM:            DOCUMENT_1
    </object>

  • Increasing Weblogic client Socket Readers etc

    How can you increase the number of socket readers on a client
    application which
    uses JMS, EJB and talks to multiple WLAS servers.
    I get the following message
    Muxer> <There are: '3' active sockets, but the maximum number of socket
    readers allowed by theconfiguration is: '2', you may want alter your
    configuration.>
    But I cant find out how to increase the socket readers or better yet can
    I use the native IO for Solaris and NT clients??

    Hi,
    You can control the number of threads and the precent of socket readers
    through the properties: weblogic.ThreadPoolSize and
    weblogic.ThreadPoolPercentSocketReaders. You would have to pass them to the
    jvm machine at startup for example:
    -Dweblogic.ThreadPoolSize=10 -Dweblogic.ThreadPoolPercentSocketReaders=50
    Guy
    "Larry Presswood" <[email protected]> wrote in message
    news:[email protected]..
    How can you increase the number of socket readers on a client
    application which
    uses JMS, EJB and talks to multiple WLAS servers.
    I get the following message
    Muxer> <There are: '3' active sockets, but the maximum number of socket
    readers allowed by theconfiguration is: '2', you may want alter your
    configuration.>
    But I cant find out how to increase the socket readers or better yet can
    I use the native IO for Solaris and NT clients??

  • Java client socket readers

              I'm running a cluster of 3 WL 6.0 servers and when I do a JNDI lookup to run methods
              on a remote interface stub on the client side it gives me the following:
              <Apr 26, 2001 2:16:34 PM MST> <Warning> <JavaSocketMuxer> <There are: '3' active
              sockets, but the maximum number of socket readers allowed by theconfiguration
              i
              s: '2', you may want alter your configuration.>
              I re-ran my client with the two following properties:
              -Dweblogic.system.executeThreadCount=5
              -Dweblogic.system.percentSocketReaders=60
              it still gives me the exception. How do I get this to work properly so I have
              as many socket readers as servers?
              Thanks in advance.
              

    Thanks,
              I had understood this wrong, I was configuring on the server, not the client
              application,
              it's all working well now.
              Cheers
              Sioux
              "Kumar Allamraju" <[email protected]> wrote in message
              news:[email protected]...
              > i.e. if percentSocketReaders = 50, and execute Threadcount is 20, 50% of
              20 = x?
              >
              > you will get x percentSocketReaders. You might want to tune this value ,
              > according to the above
              > formula.
              >
              >
              > Sioux France wrote:
              >
              > > Hi,
              > > I'm getting these errors too. I've enabled native IO, upped the number
              of
              > > Threads to 20 and the percentage of readers to 50% but I still get the
              error
              > > about 3 active sockets when I am only allowed 2 in a cluster of 3
              servers.
              > > Did you resolve this?
              > > Thanks
              > > Sioux
              > >
              > > "Kumar Allamraju" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > The following syntax was correct in 510. , not in 60 anymore.
              > > > I would suggest you to increase the execute Thread count & percent
              socket
              > > readers from
              > > > console.
              > > >
              > > > or else set the following from the command line.
              > > > -Dweblogic.ThreadPoolPercentSocketReaders
              & -Dweblogic.ThreadPoolSize..
              > > (i'm not 100%
              > > > sure)
              > > > --
              > > > Kumar
              > > >
              > > > "W. Wen" wrote:
              > > >
              > > > > I'm running a cluster of 3 WL 6.0 servers and when I do a JNDI
              lookup to
              > > run methods
              > > > > on a remote interface stub on the client side it gives me the
              following:
              > > > >
              > > > > <Apr 26, 2001 2:16:34 PM MST> <Warning> <JavaSocketMuxer> <There
              are:
              > > '3' active
              > > > > sockets, but the maximum number of socket readers allowed by
              > > theconfiguration
              > > > > i
              > > > > s: '2', you may want alter your configuration.>
              > > > >
              > > > > I re-ran my client with the two following properties:
              > > > >
              > > > > -Dweblogic.system.executeThreadCount=5
              > > > > -Dweblogic.system.percentSocketReaders=60
              > > > >
              > > > > it still gives me the exception. How do I get this to work properly
              so I
              > > have
              > > > > as many socket readers as servers?
              > > > >
              > > > > Thanks in advance.
              > > >
              >
              

  • Increasing socket readers in client program

    I am trying to connect to multiple Weblogic servers from a single client at
    the same time and get the following message:
    <Sep 14, 2001 10:21:15 AM CDT> <Warning> <JavaSocketMuxer> <There are: '3'
    active
    sockets, but the maximum number of socket readers allowed by
    theconfiguration is
    : '2', you may want alter your configuration.>
    How do I change the configuration in my client so I can have more the two
    connections.
    Thanks,
    Jim Anderson

    java -Dweblogic.ThreadPoolSize=15 -Dweblogic.ThreadPoolPercentSocketReaders= 75
    (means 75% of ThreadPoolSize)
    -classpath %classpath%;. etc...
    James Anderson wrote:
    I am trying to connect to multiple Weblogic servers from a single client at
    the same time and get the following message:
    <Sep 14, 2001 10:21:15 AM CDT> <Warning> <JavaSocketMuxer> <There are: '3'
    active
    sockets, but the maximum number of socket readers allowed by
    theconfiguration is
    : '2', you may want alter your configuration.>
    How do I change the configuration in my client so I can have more the two
    connections.
    Thanks,
    Jim Anderson

  • Error message on active sockets & socket readers configuration

     

    hi Kieu,
    I am having the same problem. Were you able to figure out why you had that
    problem and how you resolved that issue. I am seeing slow performance on client
    as well. I am assuming this could be the reason for slow performance.
    thanks,
    Zeeshan.
    "Kieu Tram" <[email protected]> wrote:
    >
    Hi,
    I got the following error when I tried to access the WLS using a program
    to get
    the mbeans data.
    This error happens when I have 3 or more servers running ( 1 admin server,
    2 or
    more managed servers). With cluster with more than 2 servers running,
    this error
    also occurs.
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are:
    '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    I creased the socket readers from 33% to 66%, but I still got the same
    error.
    I'm using WLS version 6.0 sp2
    My configuration is:
    Execute Threads = 15,
    Socket Readers = 33% or 66%
    Does anyone know how to fix this ? I am really appreciate for any suggestions.
    thanks,
    Kieu

  • Socket threads problem after SOA installation

    Hi all,
    I am getting below error after sending request to the server(after weblogic and SOA servers started properly.
    <Warning><Socket>'There are: '5' active sockets, but the maximum number of
    socket readers allowed by the configuration is: '4', you may want to alter
    your configuration.>'
    I am not able to deploy the application into the SOA Server(I am getting http response 502 error in my Jdeveloper's log).
    I have seen forums about this ,they told to change the socket threads in weblogic console(mine is weblogic 10.3.5 server) ,but I am not able to change in the console.It has already some value as 33 and when I change and save ,it is telling value can not be changed dynamically.
    I was told to change like below.But Where do I need to change like below and how
    java -Dweblogic.ThreadPoolSize=10 -Dweblogic.ThreadPoolPercentSocketReaders=60 ... your.client ...
    I am stuck(I am not able to deploy the applications into SOA server)
    Thanks in advance

    Hi
    1. What you are seeing is <Warning> and mostly you can ignore this. This may not be the root cause for your error.
    2. Can you access your soa server url from browser like http://soahost:soaport/bpm/workspace url should work. Try soahost with direct ip address or dns name of that machine.
    3. In Jdeveloper, when you configure this, I hope you Tested the connection and does it show success.
    4. One way to quickly test is, deploy the SOA Workflow JAR directly from EM Console. The .jar file should be under your soaproject/deploy folder. If you have EAR for TaskForms, deploy EAR also from Console or EM Console. If all this works, this means, JDeveloper is not able to connect to soa server. Search for Proxy settings forJDeveloper in this forum. I remember seeing some posts to enable/disable Proxy for Jdeveloper like that.
    5. Look in the log files for any errors while deployment. But if server itself is NOT accessible, you may not see any deployment errors at all.
    Thanks
    Ravi Jegga

  • Socket based application - Performance Issues - Suggestions Needed

    Hi All,
    We have an application which basically has been developed using core java. Here is a high level information about the application:
    a) It opens a serversocket which allows clients to connect to it.
    b) For every new client connection, a separate thread is created and this thread deals with requests from clients, processing the data and replying back to clients.
    c) Each socket is polled continuously and sockettimeout is 2 seconds. If there is a timeout, we handle the situation and socket is again read. So basically sockets is read every 2 seconds. If number of timeouts reaches a configurable value, we close the connection and thread is dropped as well.
    d) In production, three instances of this application are running with the help of a cisco load balancer. It is there for last 5 years.
    However there has always been some minor performance isssues and we have sorted them out using different types of garbage collectors, by introducing hardware load balancers, upgrading the code for new Java versions. It is currently running on 1.4.2.
    However there has always been some performance issues and today while googling over internet I came across following on the bea website which says that core java sockets are not as efficients as native API. BEA has implemented its own APIs for weblogic. My queries are:
    a) Are there any better Java Socket/network API (for solairs, I know Java is plateform independenet but there could be lib which also using native libs) which are much more efficient than Core Java.
    b) We are getting the InputStream/OutputStream and creating objects of DataInputStream/DataOutputStream to read the data 'Byte-By-Byte'. Each byte can have different information thats why it is required. Are there any better way of getting info than what we are currently doing.
    c) As I mentioned, we are continously polling the socket for read operation with a timeout value of 2 seconds. What is the better among the following from performance point of view: (1) Frequent read operation with a lesser timeout value or (2) Less Frequent read operations with larger timeout value. (3) Any better idea??
    Please suggest few things or pointers which I could do to improve the performance of the applcations. Many thanks.
    Thanks,Akhil
    From BEA website:-
    "Although the pure-Java implementation of socket reader threads is a reliable and portable method of peer-to-peer communication, it does not provide the best performance for heavy-duty socket usage in a WebLogic Server cluster. With pure-Java socket readers, threads must actively poll all opened sockets to determine if they contain data to read. In other words, socket reader threads are always "busy" polling sockets, even if the sockets have no data to read. This unnecessary overhead can reduce performance."

    My recommendations:
    - Always use a BufferedInputStream and BufferedOutputStream around the socket streams
    - Increase the socket send and receive buffers to at least 32k if you are on a Windows platform where the default is a ridiculous 8k, which hasn't been enough for about 15 years.
    - Your 2-second timeout is far too short. Increase it to at least 10 seconds.
    - Your strategy of counting up to N short timeouts of S seconds each is completely pointless. Change it to one single timeout of N*S seconds. There is nothing to be gained by the complication you have introduced to this.

  • Increasing socket muxer threads

    Hello,
    Had production performance issue today that was resolved by creating an execute queue with 200 threads and placing the offending servlet on that queue.
    However, I noticed that the socket muxer with 3 threads is constantly busy. Is there any way to increase the number of threads for the muxer, or is this not a concern? Is it different if we are using native socket muxer? Have read several docs but still have no clear answer if we should be concerned about socket muxer.
    Thanks,
    Rich

    Thanks,
    I'm familiar with that parameter. However, from some docs I got the, probably confused, impression that those are non-native (java?) threads, and that the socket readers parameter didn't have much to do with anything once you started using the native-io performance pack.
    Thanks again,
    Rich

  • Socket reader problem even if Native IO is enabled

    Hi,
    I am using weblogic 6.1 sp1 on a hp windows2000 quad box. weblogic server hosts
    all the ejbs. Resin is used as a servlet engine. Sometimes the message
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    is seen in resin log.
    I thought this should not happen if NativeIO is enabled. I am sure nativeIO is
    enabled because when weblogic startup , I am able to see the PerformancPack tag.
    thanks
    arock

    This is a client-side configuration. You can increase WLS thread pool size by
    setting these 2 system properties (if I remember their names correctly):
    weblogic.ThreadPoolSize=10
    weblogic.ThreadPoolPercentSocketReaders=60
    on the client side.
    arock <[email protected]> wrote:
    Hi,
    I am using weblogic 6.1 sp1 on a hp windows2000 quad box. weblogic server hosts
    all the ejbs. Resin is used as a servlet engine. Sometimes the message
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    is seen in resin log.
    I thought this should not happen if NativeIO is enabled. I am sure nativeIO is
    enabled because when weblogic startup , I am able to see the PerformancPack tag.
    thanks
    arock--
    Dimitri

  • Weblogic Socket Error

    I am seeing the below message in the standard output. (FYI – WebLogic 10.0.1.0 is set up on the Linux server)
    <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
    Increasing the “thread-pool-percent-socket-readers” parameter in config.xml from 50 to 75 did not resolve this error. The below link talks about patch CR263825.
    Is this patch applicable for WebLogic 10 ?
    Weblogic Thread Management
    Thank you

    I am seeing the below message in the standard output. (FYI – WebLogic 10.0.1.0 is set up on the Linux server)
    <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
    Increasing the “thread-pool-percent-socket-readers” parameter in config.xml from 50 to 75 did not resolve this error. The below link talks about patch CR263825.
    Is this patch applicable for WebLogic 10 ?
    Weblogic Thread Management
    Thank you

Maybe you are looking for