| Author |
Message
|
| mqexplorer |
 Posted: Tue Oct 30, 2007 10:04 am Post subject: Unable to write to clustered queue |
 |
|
Novice
Joined: 02 Aug 2007
Posts: 17
|
Hi,
we are unable to write a big (>5 meg) message to a clustered queue. We can write the same message to the same queue when we remove it from the cluster. I have checked the Max Message Length parameter on the cluster sender/receiver channels, system cluster queues etc. Anything else that I might be missing? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 30, 2007 10:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What's the MQRC when it fails?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Oct 30, 2007 10:07 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
It would help if we knew what error code you got.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Oct 30, 2007 10:14 am Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| PeterPotkay wrote: |
| It would help if we knew what error code you got. |
2007-10-25 10:35:55,131 DEBUG
[com.accenture.adsj.soa.mrf.transport.jms.JmsReceiverMDB]
javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Oct 30, 2007 10:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
We need the linked exception that will show the actual MQSeries return code. The JMS reason code is useless here, as you have found out.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqexplorer |
| Posted: Tue Oct 30, 2007 2:53 pm Post subject: |
|
|
Novice
Joined: 02 Aug 2007
Posts: 17
|
15:38:03,267 ERROR [JmsReceiverMDB] ### Linked Exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2010
-bash-3.00$ mqrc 2010
2010 0x000007da MQRC_DATA_LENGTH_ERROR
-bash-3.00$ |
|
| Back to top |
|
|
| rmah |
| Posted: Tue Oct 30, 2007 2:55 pm Post subject: |
|
|
Centurion
Joined: 04 May 2007
Posts: 142
|
| mqexplorer wrote: |
15:38:03,267 ERROR [JmsReceiverMDB] ### Linked Exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2010
-bash-3.00$ mqrc 2010
2010 0x000007da MQRC_DATA_LENGTH_ERROR
-bash-3.00$ |
So it looks like some channel or transmission queue is not setup to handle large messages > 4MB
_________________
MQ 6.0.2.3
Broker 6.0.0.7
for Linux |
|
| Back to top |
|
|
| csd066 |
| Posted: Thu Nov 15, 2007 11:01 am Post subject: |
|
|
Newbie
Joined: 17 Nov 2004
Posts: 3
Location: GTA, Ontario
|
(You also need enough log space.)
Sorry, I take this reply back. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Nov 16, 2007 2:21 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The max length on one of the objects used is less than the size of the msg.
The objects are:
Client channel (if app is a client) CLNTCONN & SVRCONN
cluster xmitq
CLUSSDR channel - defined EVERY TIME from the corresponding CLUSRCVR
qmgr
Check all these objects
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Nov 16, 2007 6:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
and I would be so bold as to add the DLQ of each cluster member, and the log space of each cluster member to Nigel's list...
If I may suggest, use message grouping as huge message may put a serious performance strain on the network and impact your response time.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 16, 2007 8:30 am Post subject: |
|
|
Guest
|
| Quote: |
| If I may suggest, use message grouping as huge message may put a serious performance strain on the network and impact your response time. |
Then, again, we should not be writing applications around existing hardware/network issues, as these will change over time. |
|
| Back to top |
|
|
|
|
