PM93004: SOME THREADS BOTTLENECK ON WMQJCARESOURCEADAPTER.

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as program error.

Error description

• Some bottleneck on WMQJCAResourceAdapter threads.
  Blocked on com/ibm/ws/websvcs/transport/jms/JMSSender. In this
  class, synchronized method getReplyQCF takes long time for a
  JNDI lookup and caused other threads waiting.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of é áJAX-
  *                  WS                                          *
  *                  web services.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Some threads bottleneck on              *
  *                      WMQJCAResourceAdapter.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Most threads are blocked on
  com/ibm/ws/websvcs/transport/jms/JMSSender. In this class,
  synchronized method getReplyQCF takes a long time for a JNDI
  lookup and causes other threads to wait.
  

Problem conclusion

• Modified the message driven bean to cache the lookup result
  with the default JNDI name, set to the appropriate QCF before
  calling the WSE, and clear in a finally block. Added a
  property to enable this cache. When you want to enable
  the cache, set the JVM property
  com.ibm.ws.websvcs.transport.jms.cacheReplyQCF
  to true, its default value is false.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.1.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP