Troubleshooting
Problem
Your WebSphere Application Server Message consumer is unable to get the message.
Symptom
The following JMSException occurs at the application side when a consumer tries to get a message:
javax.jms.JMSException: CWSIA0144E: An exception was received during the call to the method
createBrowserSession: com.ibm.websphere.sib.exception.SIResourceException: CWSIC8007E: An
exception was caught from the remote server with Probe Id <id>. Exception: CWSIP0002E: An
internal messaging error occurred in com.ibm.ws.sib.processor.impl.BrowserSessionImpl, com.ibm.ws.sib.msgstore.MessageStoreException: CWSIP0532E: A timeout occurred while remotely
browsing destination <destination name>.
com.ibm.ws.sib.api.jms.impl.JmsQueueBrowserImpl.instantiateBrowser(JmsQueueBrowserImpl.java
)
at com.ibm.ws.sib.api.jms.impl.JmsQueueBrowserImpl.<init>(JmsQueueBrowserImpl.java)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createBrowser(JmsSessionImpl.java)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createBrowser(JmsSessionImpl.java)
The server throws the following error:
CWSIC1010E: An internal error occurred. A protocol error has occurred. Unexpected data was received from the server (<hostname>:<port> - BootstrapBasicMessaging).
Cause
For example, there are two messaging engines (ME) in the same cluster, ME1 and ME2. The message producer is connected to ME1, the message consumer is connected to ME2, and the queue point (destination) is on ME2.
If ME2 is not running, the consumer application will not receive any messages. The reason the application will not receive messages is because ME2 hosts the queue where the messages are stored.
Resolving The Problem
Make sure the messaging engine which hosts the queue is started.
Historical Number
PMR 63469;999;616
Product Synonym
WebSphere Application Server WAS SIB SIBUS SI BUS
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21624088