PI63365: JMS THIN CLIENTS HANG AFTER ILLEGALARGUMENTEXCEPTION IS THROWN

8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• JMS client hangs when attempting to connect to Websphere
  Application Server v8.0 Service Integration Bus messaging
  engine.The following errors are logged in the client logs:
  
  CWSIT0007W: It is not possible to contact the bootstrap
  server at nodex:7278:BootstrapBasicMessaging because of
  exception:java.lang.IllegalArgumentException.
  
  at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactory
  Impl.contactBootstrapService(TrmSICoreConnectionFactory
  Impl.java:761)
  at com.ibm.ws.sib.trm.client.TrmSICoreConnectionFactory
  Impl.remoteBootstrap(TrmSICoreConnectionFactoryImpl.
  java:589)
  .....
  Caused by: java.lang.IllegalArgumentException
  
  at java.nio.DirectByteBuffer.put(Unknown Source)
  at com.ibm.ws.sib.jfapchannel.buffer.impl.ThinByteBuffer
  Impl.put(ThinByteBufferImpl.java:407)
  at com.ibm.ws.sib.jfapchannel.impl.Connection.startNew
  ConversationGeneric(Connection.java:489)
  
  at com.ibm.ws.sib.jfapchannel.impl.OutboundConnection.
  startNewConversation(OutboundConnection.java:225)
  at com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionData
  Group.startNewConversation(ConnectionDataGroup.java:865)
  at com.ibm.ws.sib.jfapchannel.impl.octracker.Connection
  DataGroup.doConnect(ConnectionDataGroup.java:733)
  at com.ibm.ws.sib.jfapchannel.impl.octracker.Connection
  DataGroup.connect(ConnectionDataGroup.java:648)
  
  
  Javacores collected from the client show JMS client threads
  further wait for first conversation to complete creating
  the hang situation.
  
  
  "Thread-XX" prio=6 tid=0x00000000088f0000 nid=0x2864 in
  Object.wait()[0x0000000009f2e000]
  
  java.lang.Thread.State: WAITING (on object monitor)
  
  at java.lang.Object.wait(Native Method)
  
  - waiting on <0x00000000da6403d8> (a java.lang.Object)
  
  at java.lang.Object.wait(Object.java:485)
  
  at com.ibm.ws.sib.jfapchannel.impl.OutboundConnection.
  startNewConversation(OutboundConnection.java:190)
  
  - locked <0x00000000da6403d8> (a java.lang.Object)
  
  at com.ibm.ws.sib.jfapchannel.impl.octracker.Connection
  DataGroup.startNewConversation(ConnectionDataGroup.
  java:865)
  - locked <0x00000000da640500> (a
  com.ibm.ws.sib.jfapchannel.impl.octracker.
  ConnectionDataGroup)
  at com.ibm.ws.sib.jfapchannel.impl.octracker.Connection
  DataGroup.doConnect(ConnectionDataGroup.java:733)
  
  - locked <0x00000000da640580> (a
  
  com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionData
  Group$1)
  at com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionData
  Group.connect(ConnectionDataGroup.java:648)
  

Local fix

• Restart JMS Thin client.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: JMS thin client hangs after             *
  *                      IllegalArgumentException is thrown on   *
  *                      the                                     *
  *                      client side.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  JMS thin client hangs when attempting to connect to WebSphere
  Application Server Service Integration Bus messaging engine. The
  exception IllegalArgumentException is observed in the client
  side
  logs.
  

Problem conclusion

• Under rare timing conditions, the JMS thin client hangs when
  attempting to connect to WebSphere Application Server Service
  Integration Bus messaging engine. This hang is caused by a
  duplicate bytebuffer allocation from the thin client buffer
  pool during the first connection attempt. The code is fixed to
  avoid the duplicate allocation of bytebuffer. This fix is
  applicable only to Thin JMS clients.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.13.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP