| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| QALIAS and mqrc 2053 |
« View previous topic :: View next topic » |
| Author |
Message
|
| gui2180 |
 Posted: Fri Dec 17, 2010 5:04 am Post subject: QALIAS and mqrc 2053 |
 |
|
Newbie
Joined: 17 Dec 2010
Posts: 2
|
Hi,
first of all, thanks for the great help in the past.
I have a alias queue defined with a target type TOPIC.
Everthing works fine. The point is, when a (local)queue is full, the application will receive a 2053 ( MQRC_Q_FULL ) and can do what ever they want. When they put to a alias queue, they get no error, and the message goes to the deadletter queue.
Is there a way, to tell the application, that the queue is full? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Dec 17, 2010 8:39 am Post subject: Re: QALIAS and mqrc 2053 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| gui2180 wrote: |
Hi,
first of all, thanks for the great help in the past.
I have a alias queue defined with a target type TOPIC.
Everthing works fine. The point is, when a (local)queue is full, the application will receive a 2053 ( MQRC_Q_FULL ) and can do what ever they want. When they put to a alias queue, they get no error, and the message goes to the deadletter queue.
Is there a way, to tell the application, that the queue is full? |
Think a little bit more down to earth...
What are you really asking about:
- The publication stream queue is full
- The subscriber queue is full
Remember that the pub/sub domain completely disconnects the subscriber from the publisher. If you want to verify that the publish was successful you can ask for corresponding psc reply on the publish call.
The same way the subscriber can ask for the corresponding psc reply on the subscription call to determine whether he/she/it was successfully subscribed.
The rest is all disconnected and the publication that cannot be delivered because the destination queue is full goes to the DLQ if it exists or ... (look up the manual what happens if there is no defined DLQ)...
But then I would have expected that your monitoring would alert you to those conditions early enough!
This behavior is as designed... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gui2180 |
| Posted: Fri Dec 17, 2010 3:09 pm Post subject: |
|
|
Newbie
Joined: 17 Dec 2010
Posts: 2
|
Sorry, i forget to tell, that i wanted this constellation for messages to duplicate. The application does not know anything about pub/sub. The application just put one message to the alias queue and the message ist duplicated to local queue Q1, Q2, Q3 up to Q99.
For the moment we use Message Broker for this, but with pub/sub in MQ v7 it will also work, as far as i tested it.
The application would not like to change the code.
I have to accept, that i can't get a queue full from an alias queue.
So i have to choose between using broker with queue full error or pub/sub without queue full error. When i reduce the queuedepthhigh event, i have enought time to fix it before the queue becomes full.
Thanks, for bringing me down to earth ...  |
|
| 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
|
|
|
|
