PQ99410: 1024 CONNECTION LIMIT WITH JNI READER THREADS

 A fix is available

PQ99410; 5.1.1: 1024 CONNECTION LIMIT WITH JNI READER THREADS



APAR status
Closed as program error.

Error description
Customer gets the following error if JNI readers try to use more
than 1024 connections:
[11/4/04 1:41:36:148 CST] 25a29d5f ORBRas        X com.ibm.
CORBA.iiop.JNIReaderManager addConnection() P=651306:O=1
:LT=1:port=7778 JORB00105: None of the native code reader
threads has room in its queue for a new Socket to watch, a
COMM_FAILURE was thrown
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users utilizing *
*                 JNIReader threads with their ORB.            *
****************************************************************
* PROBLEM DESCRIPTION: After 1024 active connections, the      *
*                      Application Server ORB will start       *
*                      rejecting connections when using        *
*                      JNIReader threads with the ORB.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using JNIReader threads with the ORB, Application Server
will report the following error after 1024 active connections:
JORB00105: None of the native code reader threads has room in
its queue for a new Socket to watch, a COMM_FAILURE was thrown.
Application Server will stop accepting connections at this point
until connections are released.  This happens no matter how many
JNIReaders the administrator specified to use.
Problem conclusion
When attempting to assign a new connection to a JNIReader queue,
the code that maintains the JNIReader queues was mistakenly
comparing the number of active connections across ALL threads
to the maximum queue size instead of comparing the current size
of each specific queue.
The fix for this APAR is currently targetted for inclusion
in 5.02.10 and 5.1.1.4. Please refer to the recommended
updates page for delivery dates:

http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&
uid=swg27004980
.
PQ99410_Fix.jar will also be released as a 5.1 iFix.
Temporary fix Comments
APAR information
APAR number PQ99410
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-01-12
Closed date 2005-01-12
Last modified date 2005-01-24

APAR is sysrouted FROM one or more of the following:
PQ96752

APAR is sysrouted TO one or more of the following:

Modules/Macros
ORB          

Publications Referenced

Fix information
Fixed component name WAS BASE 5.0
Fixed component ID 5630A3600

Applicable component levels
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10S PSY    UP
R10W PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ99410
IBM Group: Software Group
Modified date: Jan 24, 2005