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>

Similar Messages

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

Increase max number of adjustments?

Does anyone know of a way to increase the maximum number of adjustment bricks for any one type of adjustment? I believe the current limit is 5, but sometimes when working with ver complex photos I find the need to go beyond this limit. In particular, I'd really like to be able to increase the number of color bricks. I am already combing color adjustments within a single brick as much as possible, with separate red, blue or yellow adjustment, but frequently I'll find that the red/oranges within a photo require very different adjustments and I find that adjustments to one eye-dropped color ends up having too much of effect on another (close but not quite) eye-dropped color. I've tried limiting these interactions as much as possible with the range slider, but it seems to have very limiting effect.
Is there a plist for bumping the max up to 6?
Thanks!
John

had to implement a quick & dirty program from OSS (note 370021) to fix this.
Edited by: Trond Stroemme on Nov 20, 2009 12:48 PM

Max number of sockets provided by JVM

Hi,
I am currently working on a program that creates a vast number of stream-oriented sockets and I encountered some problems that made me wonder whether there is a maximum number of sockets available.
I searched the forum for a hint but only found vague answers. What I am particularly interested in is a statement whether there is a maximum number of sockets that can be managed by the virtual machine regardless of the hardware provided or the operating system in use.
Thanks in advance.

If I were to write Java, I would not impose an
arbitrary limit but would rely upon the operating
system and thus "inherit" the limit from there.Correct. It's the OS that specifies the limitations in this case.

How to increase max. number of mutex lock at a time

In my application , when trying to lock mutex with pthread_mutex_lock() ,
this returns ENOMEM.
I found that ENOMEM error occurs when locking over 2000 mutex in a thread
by execute a sample program.
In those mutex,PTHREAD_PRIO_INHERIT attribute is set to lock mutex in a sequential FIFO order.
Does anyone knows how to prevent ENOMEM error and how to increase maximum number of mutex lock at a time in a thread ?

Check these 2 articles
https://support.mozilla.org/en-US/kb/change-firefox-behavior-when-open-file?esab=a&s=how+to+put+a+file+in+download+queue&r=2&as=s
https://support.mozilla.org/en-US/kb/find-and-manage-downloaded-files?esab=a&s=limit+maximum+number+of+downloads+and+create+a+download+queue&r=1&as=s
This might help you.
Thank you.

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.
          > > >
          >

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.

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.

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

Is there a max number of iCloud clients

iCloud supports my iPhones and Windows 8.1 calendars, but structurally discards my iPad. Is there a max number of iCloud clients ina network?

Hallo James, It seems that your suggestion did work! The sync, however, came much later than those on the smart phones. I reentered my Apple password and turned the iPad calendar iCloud button OFF and ON and after, say, half an hour I got missing calendar items on the iPad.
10 Points for you! Thanks.

1252 - Max Number of Clients

I have customer that is looking at deploying 1252 access points. I was wondering what the maximum number of clients that can associate to a single 1252. Does this count differ between 1252s running autonomous and LWAPP? The proposed configuration is using B/G radios at 54Mbps but quoting the A/B/G model for future 802.11n deployment (5Ghz radios would be turned off for now).
Any information would be greatly appreciated.
Thx
Joe

Its not as simple as the max number of clients but you also have to consider the type of client. Also food RF deisign and survey are critical to maximising client throughput.
There are rules for existing aps of approx 20-25 max for data. This would be 7 for voice in mixed mode b/g or 14 for g only and 20 for a only.
The ap can theoretically support many more clients, I think the figure is 256. With very simplistic data transfer such as bar code scanning I have seen as may as 50 clients with no issues.
As you ar lookig at abg these figures seem realistic.
With 802.11n you hav more bandwith available, better utilisation of the spectrum and therefore more client but its about being realistic and looking at what you are trying to connect.
Streaming multimedia would be lower than data only. Data only I would say 50 clients no issues but thats quite a density considering the RF footprint. For voice you are stuck with the above figures as you are still only dealing with abg clients.
Hope that helps

Increasing maximum number of Logical Processors in a Processor Group greater than the default (64)

Can the maximum number of Logical Processors allowed in a Processor Group be increased by Bcdedit command or registry key to a number greater than the default (64) to allow non-group-aware applications to seamlessly scale via multithreading across more cores
MSDN documents methods to reduce the max number of LP's in a Processor Group to 1 or any power of 2 less than 64 in order to increase the number of Processor Groups. But there is no discussion of how to increase the maximum number of Logical Processors
allowed in a Processor Group to a number greater than the default (64), e.g. to 128 or 256.
Since a non-group-aware application/process can only run on 1 Processor Group, increasing this limit is needed to allow non-group-aware multithreaded applications to scale seamlessly for parallel computation across more than 64 cores simultaneously on systems
with more than 64 cores (for example, a quad-socket Intel Xeon system with 24 cores per socket, including true and hyper cores). If that limit can be set via registry key or command line, or if there is another way to force all the cores on
all 4 sockets (4 NUMA nodes in this case) to join in 1 Processor Group, then non-group-aware applications will not need to be rewritten using group-aware thread-affinity APIs.

Hi John,
Are you trying to specify a static NUMA-node-to-group assignment, rather than letting Windows dynamically assign NUMA nodes to groups at boot time? If yes, You can refer the
following related KB:
How to manually configure K-Group assignment on multiprocessor machines
http://support.microsoft.com/kb/2506384
Systems with fewer than 64 logical processors always have a single group, Group 0. On systems with 64 or fewer processors, existing applications will operate correctly without
modification. Applications that do not call any functions that use processor affinity masks or processor numbers will operate correctly on all systems, regardless of the number of processors. To operate correctly on systems with more than 64 logical processors,
the following kinds of applications might require modification:
•Applications that manage, maintain, or display per-processor information for the entire system must be modified to support more than 64 logical processors. An example of
such an application is Windows Task Manager, which displays the workload of each processor in the system.
•Applications for which performance is critical and that can scale efficiently beyond 64 logical processors must be modified to run on such systems. For example, database
applications might benefit from modifications.
•If an application uses a DLL that has per-processor data structures, and the DLL has not been modified to support more than 64 logical processors, all threads in the application
that call functions exported by the DLL must be assigned to the same group.
By design, a non-NUMA computer is considered to have one NUMA node. Because NUMA nodes cannot span groups, the system creates a node for each group after you restart the computer.
The related KB:
Processor Groups
http://msdn.microsoft.com/en-us/library/windows/desktop/dd405503(v=vs.85).aspx
More information:
Uneven Windows Processor Groups
http://blogs.msdn.com/b/saponsqlserver/archive/2011/10/08/uneven-windows-processor-groups.aspx
Boot Parameters to Test Drivers for Multiple Processor Group Support
http://msdn.microsoft.com/en-us/library/windows/hardware/ff542298(v=vs.85).aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

"max number of thread"

We are running a java web app on a Ubuntu Oracle WebLogic server version 10.3.3.
The java web app performs long polls with open tcp socket to keep the client connection open. The clients are long polling the WebLogic at 30 seconds.
Currently we are not able to maintain stability for greater than 24 hours with approximately 200 simultaneous sessions on WebLogic server. Session to me is active client/server tcp connection. We have re-written our application to use continuations, but we are seeing ConcurrentModificationException errors in performance testing.
Is there any setting in WebLogic for “max number of thread” that can handle?
Edited by: user9316392 on Jul 8, 2010 11:07 AM

First, WebLogic since 9.0 has a self-tuning thread pool where WLS will automatically grow and shrink the number of threads based on some internal algorithms. I'm not aware of a hard limit so theoretically there is no max thread count as long as the JVM has memory and WLS thinks more threads will help. You can read up on it here:
http://www.oracle.com/technology/pub/articles/dev2arch/2006/01/workload-management.html
Practically, I wouldn't expect more than several hundred threads to be helpful.
As for your situation, how does WLS become unstable? Out of memory, out of file descriptors, errors on new requests, etc. I think you're going to have to use some JVM tools to see what happens to your JVM over time. Is there a memory leak somewhere, is it non-heap memory, etc. JRockit Mission Control is helpful if running on JRockit. If you're on Sun Hotspot, them presumably you can use some of the Hotspot tools. You'll want to compare the state of the JVM towards the beginning of your load test, but after a slight warm-up period with a snapshot after the load test has been running for a long period of time.

Max number of streams

Hello,
My application is running out of stdio streams. There is a note in stdio man pages: no more than 255 files may be opened using fopen(), and only file descriptors 0 through 255 can be used in a stream.
The application creates a bunch of sockets (>255) and eventually calls fopen() that is failing because of the 255 limit. The application increases number of file descriptors that a process may create. This helps for socket() and open() calls but not for fopen(). Is there any workaround for this problem (other than use open() instead of fopen()?)
Regards,
--Stas

Hi
First of all lot depends on which OS you are using. For all 32 bit
OS stdio(3S) the limit is 256. This is because the fd itself is
defined as an unsigned 8 bit value. On Sparc Solaris 7 and beyond with
64 bit option turned on it is 65536 (64K).
Having said that however there are ways to manipulate it. No guarantees that it will work, but try it anyways.
All versions of Solaris (including Solaris 7 64-bit) have a default
"soft" limit of 64 and a default "hard" limit of 1024.
Processes may need to open many files or sockets as file
descriptors. Standard I/O (stdio) library functions have
a defined limit of 256 file descriptors as the fopen() call,
datatype char, will fail if it can not get a file descriptor between
0 and 255.
The open() system call is of datatype "int", removing this limitation.
However, if open() has opened 0-255 file descriptors without closing
any, fopen() will not be able to open any file descriptors as all the
low-numbered ones have been used up. Applications that need to use
many file descriptors to open a large number of sockets, or
other raw files, should be forced to use descriptors
numbered above 256. This allows system functions such as
name services, to work as they depend upon stdio routines.
(See p 368 "Performance and Tuning - Java and the Internet").
There are limitations on the number of file descriptors
available to the current shell and its descendents. (See the ulimit
man page). The maximum number of file descriptors that can
be safely used for the shell and Solaris processes is 1024.
This limitation has been lifted for Solaris 7 64-bit which
can be 64k (65536) as explained before.
Therefore the recommended maximum values to be added to /etc/system
are:
set rlim_fd_cur=1024
set rlim_fd_max=1024
The in the shell :
Use the limit command with csh:
% limit descriptors 1024
Use the ulimit command with Bourne or ksh:
$ ulimit -n 1024
However, some third-party applications need the max raised.
A possible recommendation would be to increase rlim_fd_max,
but not the default (rlim_fd_cur). Then rlim_fd_cur can be
raised on a per-process basis if needed, but the higher setting
for rlim_fd_max doesn't affect all processes.
Let me know how it goes
-Manish
SUN-DTS

Increasing max number of socket readers on client

Similar Messages

Maybe you are looking for