PQ96752; 4.0.6: 1024 Connection limit using
JNIReader threads
Downloadable files
Abstract
1024 Connection limit using JNIReader threads
Download Description
PQ96752 resolves the following problem:
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 manyJNIReaders 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 available via iFix PQ96752
(PQ96752_Fix.jar.).
JORB00105: None of the native code reader threads has room in its queue
for a new Socket to watch, a COMM_FAILURE was thrown
Prerequisites
NONE
Installation instructions
Please review the readme.txt for detailed installation
instructions.