| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WAS MQ/JMS app sometimes throws 2010 sending message |
« View previous topic :: View next topic » |
| Author |
Message
|
| webspherical |
 Posted: Wed Sep 14, 2005 9:42 am Post subject: WAS MQ/JMS app sometimes throws 2010 sending message |
 |
|
Acolyte
Joined: 15 Aug 2005
Posts: 50
|
on WAS 5.1/WMQ5.3.10
I have a session bean that simply places a JMS bytes message on a remote queue (target client=MQ) that is sent to iSeries.
everything runs perfect 99% of the time but I see this error intemittently testing:
| Quote: |
[9/14/05 13:12:28:149 EDT] 60dce1e3 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$qcf1$JMSManagedConnection@1549836385. The exception which was received is javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[9/14/05 13:12:28:157 EDT] 60dce1e3 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/SLSB/qcf1. The exception which was received is javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[9/14/05 13:12:28:160 EDT] 60dce1e3 SystemOut O JMS Exception thrown in method sendMessage(): javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[9/14/05 13:12:28:160 EDT] 60dce1e3 SystemOut O JMS linked exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2010
[9/14/05 13:12:28:160 EDT] 60dce1e3 SystemOut O Finally closing connection
[9/14/05 13:12:28:160 EDT] 60dce1e3 SystemOut O mdh.create() :javax.ejb.CreateException: MQJMS2007: failed to send message to MQ queue
|
when checking the messages manual it says:
| Quote: |
MQRC_DATA_LENGTH_ERROR
The DataLength parameter is not valid. Either the parameter pointer is not valid, or it points
to read-only storage. (It is not always possible to detect parameter pointers that are not valid;
if not detected, unpredictable results occur.)
This reason can also be returned to an MQ client program on the MQGET, MQPUT, or
MQPUT1 call, if the BufferLength parameter exceeds the maximum message size that was
negotiated for the client channel.
Corrective action: Correct the parameter.
If the error occurs for a WebSphere MQ client program, also check that the maximum message
size for the channel is big enough to accommodate the message being sent; if it is not big
enough, increase the maximum message size for the channel.
Completion and reason codes
90 WebSphere MQ Messages
|||
|
but what parameter is it talking about?
I checked and the queues/ channels are all set to 4194304 so they are large enough.
I basically just create a bytes message, and do a writebytes to it and send it off....
anyone seen this?
thanks!
Last edited by webspherical on Mon Sep 26, 2005 9:23 am; edited 1 time in total |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Sep 14, 2005 9:53 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are you connecting to your qmgr via a MQ client connection? If so, you need to check the clntconn definition on the WAS side AND the svrconn definition on the qmgr size for maxmsgl.
_________________
-wayne |
|
| Back to top |
|
|
| webspherical |
| Posted: Wed Sep 14, 2005 11:03 am Post subject: |
|
|
Acolyte
Joined: 15 Aug 2005
Posts: 50
|
yes i am connecting through client bindings and svrconn channel. svrconn chl is also set to 4MB.
Last edited by webspherical on Mon Sep 26, 2005 9:22 am; edited 1 time in total |
|
| Back to top |
|
|
| webspherical |
| Posted: Mon Sep 26, 2005 9:21 am Post subject: |
|
|
Acolyte
Joined: 15 Aug 2005
Posts: 50
|
| Should I dump the size of the message before trying to send just to verify? IS this the only time we would see a 2010? if the message is over 4MB? |
|
| Back to top |
|
|
| hopsala |
| Posted: Mon Sep 26, 2005 7:01 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| webspherical wrote: |
| Should I dump the size of the message before trying to send just to verify? |
Well, why ask us, just try it 
Procceed with usual debugging methods - start printing out variables, understand the pattern and what's special about the specific msg this happens in.
| webspherical wrote: |
| IS this the only time we would see a 2010? if the message is over 4MB? |
As your quote states, this can either happen if your msg is over 4MB, *or* when you give it a pointer instead or a variable (or anything similar); if you still can't find it, paste the relevant code section here, including the part that sets the message itself and sends it. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
