nested exception is: com.ibm.websphere.csi.CSITransactionRolledbackException:
at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:742)
at com.ibm.ejs.csi.TranStrategy.postInvoke(TranStrategy.java:181)
at com.ibm.ejs.csi.NotSupported.postInvoke(NotSupported.java:99)
at com.ibm.ejs.csi.TransactionControlImpl.postInvoke(TransactionControlImpl.java:581)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3876)
at com.ibm.bcg.server.common.EJSLocalStatelessTransController_5c554616.onReceive
(Unknown Source)
at com.ibm.bcg.server.common.BaseMDB.onMessage(BaseMDB.java:194)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod
(MessageEndpointHandler.java:992)
at com.ibm.ejs.container.MessageEndpointHandler.invoke
(MessageEndpointHandler.java:725)
at $Proxy0.onMessage(Unknown Source)
at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint
(JmsJcaEndpointInvokerImpl.java:201)
at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch
(SibRaDispatcher.java:708)
at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run
(SibRaSingleProcessListener.java:584)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:497)
Although you receive this exception, all of the follow objectives are met:
v
Graceful recovery
v
No document loss
v
No duplicate document processing
v
No performance degradation (after restart)
v
No hung documents
Fixing WebSphere MQ messages
See the following sections to fix specific MQ messages:
v
“MQJMS2007 error”
v
“MQJMS2013 error” on page 181
MQJMS2007 error
About this task
If you are using JMS as a Gateway with Websphere MQ as the messaging service,
you can receive the following message when putting a particular message in a
queue.
MQJMS2007: failed to send message to MQ queue
The result is that the Connector fails to write a message to output queue. The
cause of this error might be that the Maximum message length attribute for a
queue, queue manager or channel is not set to a value that is equal to or higher
than the largest message size.
To change the message length attribute for the queue, queue manager and channel:
1.
Go to the Websphere MQ explorer Queue manager properties.
2.
Click on the extended tab and set the maximum message length attribute to a
value greater than the size of the message.
3.
Go to the Channel properties.
4.
Click on the extended tab and set the maximum message length attribute to a
value greater than the size of the message.
5.
Go to the Queue properties for the queue that was specified while creating the
gateway.
180
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
Summary of Contents for E02HRLL-G - WebSphere Partner Gateway...
Page 20: ...14 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 66: ...60 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 80: ...74 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 86: ...80 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 90: ...84 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 134: ...128 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 154: ...148 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 194: ...188 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 228: ...222 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 258: ...252 IBM WebSphere Partner Gateway Enterprise and Advanced Editions Administration Guide...
Page 267: ......
Page 268: ...Printed in USA...