PM44272: SERVICE INTEGRATION BUS APPLICATION HANGS ATTEMPTING TO CONNECT FOLLOWING A HANDSHAKE FAILURE

Fixes are available

APAR status

Closed as program error.

Error description

A Service Integration Bus application hangs when attempting to
connect to a Messaging Engine (ME).

After the hang, the following messages will appear in the
SystemOut.log:

WTRN0006W: Transaction nnnnnnnnnn has timed out after 180
seconds.
WTRN0124I: When the timeout occurred the thread with which the
transaction is, or was most recently, associated was
Thread[<Thread ID>]. The stack trace
of this thread when the timeout occurred was:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
com.ibm.ws.sib.jfapchannel.impl.OutboundConnection.startNew
Conversation(OutboundConnection.java:188)
com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionDataGroup.
connect(ConnectionDataGroup.java:548)
com.ibm.ws.sib.jfapchannel.impl.octracker.OutboundConnection
Tracker.connect(OutboundConnectionTracker.java:518)
com.ibm.ws.sib.jfapchannel.impl.ClientConnectionManagerImpl.
connect(ClientConnectionManagerImpl.java:129)
com.ibm.ws.sib.comms.client.ClientSideConnection.connect
(ClientSideConnection.java:231)
com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactoryImpl.
contactBootstrapService(TrmSICoreConnectionFactoryImpl.
...

This stack will be evident in javacores taken from the
application JVM.

There will be an FFDC at the client indicating a failure to
connect a few milliseconds before the hang ensued.  This FFDC
will indicate that a different thread to the hanging thread
failed to connect because of an Exception during handshaking.

It is likely, although not necessary, that an FFDC at the ME
JVM will look like the following:

java.lang.NullPointerException compData 95
Exception = java.lang.NullPointerException
Source = compData
probeid = 95
Stack Dump = java.lang.NullPointerException
at com.ibm.ws.sib.mfp.impl.SchemaManager.makeSchemaIdList(Schema
Manager.java:316)
at com.ibm.ws.sib.mfp.impl.SchemaManager.receiveHandshake(Schema
Manager.java:204)
at com.ibm.ws.sib.mfp.impl.CompHandshakeImpl.compHandshakeData
(CompHandshakeImpl.java:93)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for                                         *
*                  IBM WebSphere Application Server            *
****************************************************************
* PROBLEM DESCRIPTION: Application thread hangs attempting     *
*                      to connect to the Messaging Engine      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Connections to the Service Integration Bus are multiplexed,
meaning multiple application threads can use the same TCP
connection concurrently to communicate with the Messaging
Engine.  When this multiplexed connection is established a
handshake process is required, and this is performed by the
first connecting thread.  If the handshake fails for any
reason, other threads waiting to use the multiplexed
connection will attempt the handshake.
However, due to the processing following the first handshake
failure being performed at the same time a second handshake is
being attempted, the system will enter a hung state.

Problem conclusion

This APAR resolves the problem by preventing the second
attempt to perform a handshake on the same TCP connection.
Instead, threads waiting to use the TCP connection are told
the connection is broken.  These threads will get a connection
error and must attempt the connection again.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.43, 7.0.0.21 and 8.0.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

Comments

APAR Information

APAR number
PM44272
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-22
Closed date
2011-10-20
Last modified date
2011-10-20

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
PLAT MSG COM
Fixed component ID
620600101

Applicable component levels

R200 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM44272: SERVICE INTEGRATION BUS APPLICATION HANGS ATTEMPTING TO CONNECT FOLLOWING A HANDSHAKE FAILURE

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

R200 PSY

Document Information

Share your feedback

Need support?