| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2056 Error Messages - Where do you see them? |
« View previous topic :: View next topic » |
| Author |
Message
|
| clbrasfield |
 Posted: Fri Feb 25, 2005 7:24 am Post subject: 2056 Error Messages - Where do you see them? |
 |
|
Newbie
Joined: 12 Nov 2003
Posts: 3
Location: Atlanta
|
We have had a problem recently where applications on Solaris have reported a 2056 when trying to put to a queue. I have read through many posts on this subject and have a general undertanding of the cause, but I have a question for those of you out there who have experienced this.
When this problem occurs, do you see any indication of the problem in the MQ error logs? I see no indication in my MQ error logs, and no FDC files were created. Maybe I'm off-base here, but I would expect this type of error to be reported in my logs somewhere, not just in the application.
This is on an outdated system soon to be decommissioned and we are running MQ 5.1 CSD4 on Solaris 2.5. |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Fri Feb 25, 2005 7:34 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| There s no reason to report it in the logs, or produce an FDC. The reason code is MQRC_Q_SPACE-NOT_AVAILABLE, which means that the queue file has expanded to its maximum possible size, 320Mb at 5.1. This is an application and configuration level error, not an MQ error, and so is not reported in the logs, just returned to the app. |
|
| Back to top |
|
|
| clbrasfield |
| Posted: Fri Feb 25, 2005 11:10 am Post subject: |
|
|
Newbie
Joined: 12 Nov 2003
Posts: 3
Location: Atlanta
|
Thank you for the reply. More info..
The queue that was getting put to was a remote queue. There was no indication of channel trouble to the remote system, so I'm sure that the problem was not with the local transmission queue. The remote system is running 5.3, so we're much less likely to hit the now 2 GB limit on the queue. Other applications running on the remote system were able to put to the same queue with no problem. The resolution, albeit an undesirable one, was to recycle MQ on the local node. For some reason, the recycle fixed the problem. Perhaps the timing was coincidental, and the problem went away on the remote server at the time of recycle, but I don't see that as likely. We are using persistent messaging.
Can anyone make sense of this or maybe point me to something I haven't considered? Has anyone else seen the 2056 return code being resolved by recycling MQ? |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Fri Feb 25, 2005 12:40 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Are you sure that the transmission queue was working? Did you send a test message across it?
It could be that you had a lot of uncommitted messages being placed on the transmission queue from an application that never committed them or issued a close for the remote queue. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 25, 2005 1:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Could it be that you had a non persistent message on the xmitq that exceeded the posted channel maxmsgsize? Upon recycling this non persistent message would disappear and the channel restart.
This way a full xmitq would start working again...
Enjoy  |
|
| 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
|
|
|
|
