PH41504: APPSERVERS GO INTO RETRY CYCLE WITH ERROR MESSAGE "EXCEPTION CAUGHT INCREASING RANGE OF UNIQUE KEY GENERATOR!"

APAR status

• Closed as program error.

Error description

• The flow of messages between Messaging Engines gets
  into a retry cycle that never resolves itself. The
  following error message is produced repeatedly:
  
  Caused by: javax.jms.JMSException: CWSIA0067E: An exception was
  received during the call to the method
  JmsMsgProducerImpl.sendMessage (#4):
  com.ibm.ws.sib.processor.exceptions.SIMPResourceException:
  com.ibm.websphere.sib.exception.SIResourceException: CWSIP0002E:
  An internal messaging error occurred in
  com.ibm.ws.sib.processor.impl.PubSubInputHandler,
  1:3109:1.331.1.4, com.ibm.ws.sib.msgstore.PersistenceException:
  Exception caught increasing range of unique key generator!.
  at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl.sendMe
  ssage(JmsMsgProducerImpl.java:1350)
  at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl.send(J
  msMsgProducerImpl.java:737)
  at com.ibm.lconn.events.internal.publish.impl.JMSPublish
  er.publishEvent(JMSPublisher.java:211)
  ... 89 more
  
  and the error stack below can be seen in the trace:
  
  java.lang.NullPointerException
  at com.ibm.ws.sib.processor.impl.BaseDestinationHandler.getRou
  tingDestinationAddr(BaseDestinationHandler.java:4872)
  at com.ibm.ws.sib.processor.impl.PtoPInputHandler.internalHand
  leMessage(PtoPInputHandler.java:486)
  at com.ibm.ws.sib.processor.impl.PtoPInputHandler.handleMessag
  e(PtoPInputHandler.java:264)
  at com.ibm.ws.sib.processor.impl.PtoPInputHandler.deliverOrder
  edMessages(PtoPInputHandler.java:2483)
  at com.ibm.ws.sib.processor.gd.GuaranteedTargetStream.processA
  ckExpected(GuaranteedTargetStream.java:1269)
  at com.ibm.ws.sib.processor.gd.TargetStreamManager.handleAckEx
  pectedMessage(TargetStreamManager.java:998)
  at com.ibm.ws.sib.processor.impl.AbstractInputHandler.handleCo
  ntrolMessage(AbstractInputHandler.java:757)
  at com.ibm.ws.sib.processor.io.RemoteMessageReceiver.processCo
  ntrolMessage(RemoteMessageReceiver.java:579)
  at com.ibm.ws.sib.processor.io.RemoteMessageReceiver.receiveMe
  ssage(RemoteMessageReceiver.java:362)
  at
  com.ibm.ws.sib.processor.io.MPIO.receiveMessage(MPIO.java:211)
  at com.ibm.ws.sib.comms.server.mesupport.METransportReceiveLis
  tener.rcvMessage(METransportReceiveListener.java:848)
  at com.ibm.ws.sib.comms.server.mesupport.METransportReceiveLis
  tener.dataReceived(METransportReceiveListener.java:347)
  at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ConversationRe
  ceiveListenerDataReceivedInvocation.invoke(ConversationReceiveL
  istenerDataReceivedInvocation.java:195)
  at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.ReceiveListene
  rDispatchQueue.run(ReceiveListenerDispatchQueue.java:542)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
  *                  using Publish                               *
  *                  Subscribe JMS messages within several       *
  *                  Messaging Engines in a                      *
  *                  bus.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: PubSub messages stop flowing between    *
  *                      Messaging Engines and messages build    *
  *                      up                                      *
  *                      at the sending end.                     *
  ****************************************************************
  * RECOMMENDATION:  If seen apply the fix.                      *
  ****************************************************************
  PubSub messages stop flowing between messaging engines. An FFDC
  with the stack element
  java.lang.NullPointerException
  at com.ibm.ws.sib.processor.impl.BaseDestinationHandler.getRou
  tingDestinationAddr(BaseDestinationHandler.java:4872)
  is produced.
  

Problem conclusion

• The fix for this APAR is targeted for inclusion in fix packs
  ptf8.5.5.21 and ptf9.0.5.11 For more information, see 'Recommend
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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