|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Determining Queue connected with Channel |
« View previous topic :: View next topic » |
Author |
Message
|
kordi |
Posted: Mon May 28, 2012 1:37 pm Post subject: Determining Queue connected with Channel |
|
|
Centurion
Joined: 28 May 2012 Posts: 146 Location: PL
|
Hello,
Yesterday I had an issue: I couldn't estabilish a connection between server and receiver channel. Error logs was informing that receiver channel ended abnormally, WebSphere MQ Explorer showed status of this channel as "PAUSED", server channel where runnig, so I was really confused.
My vendor dicovered that queue connected with this channel reached maximum number of documents, so new document couldn't arrived, the receiver channel was in PAUSED state then. I try to read properties of queue and receiver channel and I didn't fine any informations that they are connected in any way.
Is it possible to determine which queue is a receiver/destination for which channel?
Regards |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon May 28, 2012 2:30 pm Post subject: Re: Determining Queue connected with Channel |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
kordi wrote: |
Hello,
Yesterday I had an issue: I couldn't estabilish a connection between server and receiver channel. Error logs was informing that receiver channel ended abnormally, WebSphere MQ Explorer showed status of this channel as "PAUSED", server channel where runnig, so I was really confused.
My vendor dicovered that queue connected with this channel reached maximum number of documents, so new document couldn't arrived, the receiver channel was in PAUSED state then. I try to read properties of queue and receiver channel and I didn't fine any informations that they are connected in any way.
Is it possible to determine which queue is a receiver/destination for which channel?
Regards |
does not really matter. Any queue full is bad news. If you have a DLQ the channel is dramatically slower while attempting the retries before putting the message to the DLQ. If you have no DLQ the channel is stopped after the last retry... Eventually the DLQ may fill up too...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Mr Butcher |
Posted: Mon May 28, 2012 11:06 pm Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
is it possible to determine by a look at your post box who will be able to send you letters? _________________ Regards, Butcher |
|
Back to top |
|
 |
kordi |
Posted: Mon May 28, 2012 11:08 pm Post subject: |
|
|
Centurion
Joined: 28 May 2012 Posts: 146 Location: PL
|
True, but you didn't answer the question
What I figured out is that i need to determine transmission queue, then find this transsmision queue on a list and look at properties of remote queue connectet with this transmission queue. |
|
Back to top |
|
 |
Mr Butcher |
Posted: Tue May 29, 2012 1:17 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
yes, sure. if you can get your hands on all remote connected ends, you will see all remotequeues that point to that local queue.
however, keep in mind, there is also mq clustering (if this applies to your case), so new queuemanagers may show up as new senders to that queue.
And that applications may use the remote queuemanager name on the mqopen, which (assuming a proper routing by qmgr name) makes remote queue definitions obsolete. _________________ Regards, Butcher |
|
Back to top |
|
 |
mqjeff |
Posted: Tue May 29, 2012 1:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
IF you have a stopped receiver channel, then the issue is not on the remote ends.
You can determine that the receiver channel is stopped. You should be able to get information from the logs about WHY it stopped - i.e. a queue was full. Ideally this will include the name of the queue in question.
You can otherwise, and SHOULD otherwise, be monitoring for a FULL QUEUE in the first place. So that you don't deal with "my receiver is stopped" you deal with "My queue is full. Oh, and apparently that stopped the receiver". |
|
Back to top |
|
 |
kordi |
Posted: Tue May 29, 2012 3:08 am Post subject: |
|
|
Centurion
Joined: 28 May 2012 Posts: 146 Location: PL
|
OK, thanks! I'll remebeer this in the future |
|
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
|
|
|
|