| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Cannot get messages from the queue (AMQ4033) |
« View previous topic :: View next topic » |
| Author |
Message
|
| MichaelBulla |
 Posted: Mon Nov 20, 2006 8:22 am Post subject: Cannot get messages from the queue (AMQ4033) |
 |
|
Apprentice
Joined: 27 Sep 2006
Posts: 31
Location: Hamburg/Germany
|
Hi,
I've got a new MQ-Problem/Error in my collection.
I configured two queuemanagers, both connected by a Sender-Receiver-Channel and a transmissionqueue. I just post the changes to normal configuration by MQ-Explorer.
Configuration1
QMgrname: CSS
TransmitQname: BOC01
Usage: Transmission
TriggerControl: On
Triggertype: First
InitiationQ: SYSTEM.CHANNEL.INITQ
Senderchannelname: toBOC01
connection name: 10.1.101.205(1414)
TransmissionQ: BOC01
Receiverchannelname: toCSS
Configuration2
QMgrname: BOC01
TransmitQname: CSS
Usage: Transmission
TriggerControl: On
Triggertype: First
InitiationQ: SYSTEM.CHANNEL.INITQ
Senderchannelname: toCSS
connection name: 10.1.20.98(1414)
TransmissionQ: CSS
Receiverchannelname: toBOC01
For a while this works fine, but after some time one or the other queuemanager crashes. It becomes the status "Retrying" and locks both, the transmissionQ and the senderChannel. I cant stop or delete the channel, and if I try I cant even stop or delete the queuemanager until a reboot.
The transmissionQ doesnt react, too. I can put messages to it, but if I browse Messages, I get a "Cannot get messages from the queue (AMQ4033)"-error.
At this point, theres nothing left to do, than rebooting, deleting and creating a new queuemanager.
Any idea, whats wrong?
Bye Michael |
|
| Back to top |
|
 |
| CMF |
| Posted: Mon Nov 20, 2006 8:45 am Post subject: |
|
|
Novice
Joined: 18 Apr 2006
Posts: 10
Location: Nashville
|
Channel retrying:
Is your network stable?
Does the recieving side have plenty of disk space?
AMQ4033:
Gets inhibited for the queue. Cannot get messages from the queue.
You'll need to change the attributes of the queue if you want to browse/get messages from it. The transmit queue by default is get inhibited.
Stopping the queue manager:
What command are you using to stop it? If you are not specifying an immediate stop (-i), it can take a while for it to come down. Even when you do, it's still not instant. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Nov 20, 2006 5:39 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
The transmit queue by default is get inhibited.
|
No it isn't. The transmit queue will be placed into a get inhibited status if the channel is having a problem. (Which in this case it certainly seems to be). The MCA needs the queue to be get enabled in order to GET the message for transmission.
But over to the problem...
Stop the channel at both ends. (use Force if needed)
Investigate why the channels went into retrying (especially check for a full queue at the remote end).
Does the remote end have a system DLQ defined?
Correct the initial problem.
Restart the channels (you may need to reset both ends).
Always try to find your problem before dropping the queue manager. MQ is pretty good at telling you what is going on if you investigate the logs from both ends.
Finally...please read the Intercommunications guide. I realise that you are 'new to MQ' and it is a pretty big manual but trust me, you will benefit from reading it emensely. |
|
| Back to top |
|
|
| MichaelBulla |
| Posted: Tue Nov 21, 2006 5:03 am Post subject: |
|
|
Apprentice
Joined: 27 Sep 2006
Posts: 31
Location: Hamburg/Germany
|
| kevinf2349 wrote: |
| Quote: |
The transmit queue by default is get inhibited.
|
No it isn't. The transmit queue will be placed into a get inhibited status if the channel is having a problem. (Which in this case it certainly seems to be). The MCA needs the queue to be get enabled in order to GET the message for transmission. |
Yeah, thats it. Thanks.
If there occurs a network problem, do I always have to start the communication manually? Do I have to set the queue to get enable on my own?
| kevinf2349 wrote: |
| Finally...please read the Intercommunications guide. I realise that you are 'new to MQ' and it is a pretty big manual but trust me, you will benefit from reading it emensely. |
I started reading it until I thought to know enough about intercommunication to realize my application. But maybe I should take another look on it.
Bye Michael |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 21, 2006 5:54 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| If there occurs a network problem, do I always have to start the communication manually? Do I have to set the queue to get enable on my own? |
You only have to start the communications manually if the channel is no longer in retry mode. The start channel get enables the xmitq.
Enjoy 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
