IBM E02HRLL-G Administration Guide - Page 186

Fixing WebSphere MQ messages, MQJMS2007 error

Page 186 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268

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