This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

An MQ Trigger Problem Scenario

 
Srinivas Rao Marri
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have two queue managers(qm1, qm2), one among them(qm2) is remote.

I have trigger associated with my qm1 queue, which will put messages directly to the qm2 queue.

In this scenario, if qm2 gone down, and message came to qm1 queue. Trigger will fire and try connecting to qm2. It will fail. Then the message will backed out the same queue i.e qm1 queue.

Now qm2 is up. But the message wont be consumed from qm1 queue.
If a second message comes then only the previous message will also consumed as all together. If second message wont come for one week my first message will held up in the queue. Which is not a right behaviour.

In IBM MQ API is there any way to handle this situation?

Thanks
Srini
 
Chetan Parekh
Ranch Hand
Posts: 3640
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is not the right forum to post your problem.

Please choose apropriate forum from this list.
 
fred rosenberger
lowercase baba
Bartender
Posts: 12086
29
Chrome Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Chetan is right. This forum is for asking questions about this site, bringing issues to the moderators attention, and so on. Questions about technologies belong in the other forums. This one possible belongs in General Computing, or possibly IBM Websphere...
 
Guy Allard
Ranch Hand
Posts: 776
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you talked to your MQ system admins about ways to solve this?

Seems to me like you need to have your MQI consumer/getter on qm2 fired unconditionally during qm2 restart, to consume whatever is on it's input queue. In the case of a restart, your getter code may need to wait a little longer for messages. The channels have to get fully operational, and time is needed to get the message(s) off of qm1's transmit queue.

But you might need no code changes, just the admin setup to fire your qm2 consumer during system restart.

Guy
[ January 09, 2007: Message edited by: Guy Allard ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic