PM83349: NullPointerException in SocketTimerThread due to improper initialization

Fixes are available

APAR status

Closed as program error.

Error description

The Object Request Broker's (ORB) SocketTimerThread will report
a NullPointerException in the SystemErr.log as follows:

Exception in thread "Thread-29" java.lang.NullPointerException
at
com.ibm.rmi.iiop.SocketTimerThread.run(SocketTimerThread.java:55
)

This prevents cleanup of ORB threads hung in a socketWrite as
governed by the ORB property com.ibm.CORBA.SocketWriteTimeout

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: The Object Request Broker               *
*                      SocketTimerThread fails to run due to   *
*                      a NullPointerException.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Object Request Broker (ORB)'s SocketTimerThread fails to
run properly due to a NullPointerException (NPE).  This in
turn may result in threads hung in a socketWrite() not being
cleaned up by the SocketTimerThread.  The SocketTimerThread
creation and frequency with which it runs is governed by the
ORB property com.ibm.CORBA.SocketWriteTimeout (default 0).
The NPE occurs because the SocketTimerThread's reference to
the ORB ConnectionTable is null.
Conditions for which the NPE is of no consequence:
-- SocketWriteTimeout is set to 0.  The NPE will in fact never
happen since the SocketTimerThread will not be created.
-- If no ORB threads ever become hung in socketWrite().
-- Even if threads become seemingly hung or delayed in
socketWrite(), they may in fact eventually finish out on
their own.
Conditions where NPE will occur and consequences:
-- The NPE will only occur if the SocketWriteTimeout is set to
a value greater than 0, which causes the SocketTimerThread
to be created.
-- If threads become hung in socketWrite(), they will be
reported in the SystemOut.log.
Examples of hung ORB threads:
EXAMPLE #1 (hung in socketWrite and this thread blocks others
waiting in SequentialByteBuffer.flushTo() )
-------------------------------------------------------------
[2/13/13 18:21:07:536 EST] 000010d6 ThreadMonitor W
WSVR0605W:
Thread "ORB.thread.pool : 499" (00000f2d) has been active for
699633 milliseconds and may be hung.  There is/are 118
thread(s)
in total in the server that may be hung.
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite
(SocketOutputStream.java:103)
at java.net.SocketOutputStream.write
(SocketOutputStream.java:147)
at com.ibm.rmi.util.buffer.SequentialByteBuffer.flushTo
(SequentialByteBuffer.java:452)
at com.ibm.rmi.util.buffer.SequentialByteBuffer.flushTo
(SequentialByteBuffer.java:477)
at com.ibm.rmi.iiop.IIOPOutputStream.writeTo
(IIOPOutputStream.java:547)
at com.ibm.rmi.iiop.Connection.write(Connection.java:2214)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2256)
...
EXAMPLE #2 (waiting behind thread which is in socketWrite)
----------------------------------------------------------
[2/13/13 18:21:07:535 EST] 000010d6 ThreadMonitor W
WSVR0605W:
Thread "ORB.thread.pool : 199" (00000ca6) has been active for
673804 milliseconds and may be hung.  There is/are 117
thread(s)
in total in the server that may be hung.
at com.ibm.rmi.util.buffer.SequentialByteBuffer.flushTo
(SequentialByteBuffer.java:466)
at com.ibm.rmi.iiop.IIOPOutputStream.writeTo
(IIOPOutputStream.java:547)
at com.ibm.rmi.iiop.Connection.write(Connection.java:2214)
at com.ibm.rmi.iiop.Connection.send(Connection.java:2256)
...

Problem conclusion

****************************************************************
* NOTE:  APAR IX90112 MUST be installed in addition to PM83349 *
*        in order for the NPE to be corrected.  Installing     *
*        PM83349 or IX90112 by themselves will not correct the *
*        problem.  Installing one of these APARs without the   *
*        other will not break current functionality or cause   *
*        the NPE.                                              *
****************************************************************

The Base ORB's SocketWriteTimerThread code has been provided a
method within the ORB Extension code whereby it can obtain a
valid reference to the ConnectionTable.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.47, 7.0.0.29, 8.0.0.7, and the fix pack
following 8.5.0.2. Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

If ORB threads are hung in socketWrite(), a recycle of the
Java Virtual Machine (JVM) may be necessary.

Comments

APAR Information

APAR number
PM83349
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-21
Closed date
2013-03-14
Last modified date
2013-03-14

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 November 2021

Tips

PM83349: NullPointerException in SocketTimerThread due to improper initialization

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?