| Author |
Message
|
| chenna.hari |
 Posted: Mon Oct 29, 2012 5:05 pm Post subject: Unable to read the large message |
 |
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
A large message around 55 MB file is present in the MQ. Broker is not able to process this message. for some reason its unable to backout also. below is the error from mqsi.log
error WebSphere Broker v6107[970776]: [20304]BIP2613E: Unable to backout a message; MQPUT to queue 'DLQ' failed: MQCC=2; MQRC=2031;
I am trying to save the message from the queue using rfhutil, i am not able to save the completely.
Any help to identify what is the issue and resolution? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Oct 29, 2012 6:09 pm Post subject: Re: Unable to read the large message |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chenna.hari wrote: |
| Any help to identify what is the issue and resolution? |
You could try looking up the 2031 reason code. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chenna.hari |
| Posted: Mon Oct 29, 2012 6:13 pm Post subject: |
|
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
yes it says MQRC_MSG_TOO_BIG_FOR_Q_MGR.
but qmgr maxmsglength is already 100 MB.
But what is the reason Broker unable to process the message. The above error comes only when Broker unable to process and trying to put the message in backout queue or DLQ queue. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Oct 29, 2012 10:39 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| chenna.hari wrote: |
| yes it says MQRC_MSG_TOO_BIG_FOR_Q_MGR. |
Keep reading ... |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Tue Oct 30, 2012 1:10 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| chenna.hari wrote: |
| but qmgr maxmsglength is already 100 MB. |
"cannot exceed the lesser of the queue-manager MaxMsgLength attribute and queue MaxMsgLength attribute."
Likely you also need a bit of MQ (primary and secondary) log space 
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Mon Nov 05, 2012 9:15 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
First thing to do: Make sure your Q maxmsg length is greater than 55.
Second thing to do: Define a backout Q for that queue and ensure that the maxmsglength is greater than 55 MB for backout Q as well. This is ensure that the msg does not hit DLQ immediately.
Third thing to do: increase log size as suggested by mqsiuser. Increase number of secondary log files and the size of the log files.
Incase problem still exists, do get back  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Nov 05, 2012 10:30 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mayheminMQ wrote: |
Third thing to do: increase log size as suggested by mqsiuser. Increase number of secondary log files and the size of the log files.
|
Increasing the number of log files is possible with a QMGR restart but AFAIK (MQ 7.1 and 7.5 might have changed this) changing the size of the log files is not possible without dropping the QMGR and creating it again.
This is where a set of decent scripts that create and provision the QMGR and more that create and provision the broker are a godsend.
Naturally you will have those scripts checked into your source control system as well.(won't you?)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
