Environment
Novell Identity Manager Driver - Websphere
Situation
The JMS driver syncs information
on the Subscriber Channel but not on the Publisher
channel
Below is an example of a
trace.
JMS
3.5 PT:JMSPublicationShim.pollMonitoredDestinations()
JMS 3.5 PT:JMSChannel.connect()
JMS 3.5 PT:javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
JMS 3.5 PT:java.lang.NullPointerException
JMS 3.5 PT:Unable to connect or lost connection to broker'SYSTEM.BROKER'.
JMS 3.5 PT:Stopping connectioncom.ibm.mq.jms.MQQueueConnection@33fc1d.
JMS 3.5 PT:Stopped.
JMS 3.5 PT:Unregistering connection listener from connectioncom.ibm.mq.jms.MQQueueConnection@33fc1d.
JMS 3.5 PT:JMSChannel.connect()
JMS 3.5 PT:javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
JMS 3.5 PT:java.lang.NullPointerException
JMS 3.5 PT:Unable to connect or lost connection to broker'SYSTEM.BROKER'.
JMS 3.5 PT:Stopping connectioncom.ibm.mq.jms.MQQueueConnection@33fc1d.
JMS 3.5 PT:Stopped.
JMS 3.5 PT:Unregistering connection listener from connectioncom.ibm.mq.jms.MQQueueConnection@33fc1d.
Resolution
Many things can cause this
problem because it is rather generic. One item to check
are the flags used in the message sending client. Try a minimal JMS
sample app (built from source from the IBM website). Often, a
message will be delivered successfully. If that is the case then
remove the settings from the client application that is causing the
message to fail on retrieval.