| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Put message to local q when qmgr starts |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Thu May 08, 2008 1:18 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| wbimb wrote: |
| Thanks. I modified amqsput as mentioned by you and it worked |
But the question of "Why" remains contact admin.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Thu May 08, 2008 4:51 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Vitor wrote: |
| wbimb wrote: |
| Thanks. I modified amqsput as mentioned by you and it worked |
But the question of "Why" remains contact admin.... |
.....and probably will remain so. My initial thoughts are that they must just be testing a local queue in order to prepare for dropping a message onto a remote queue later. That way they could flag another server when this one becomes 'active'. ...other than that....  |
|
| Back to top |
|
|
| wbimb |
| Posted: Thu May 08, 2008 8:37 pm Post subject: |
|
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
This scenario is because
The moment a message lands on a local queue which will trigger an application to start which will start the message traffic
There are production servers which goes for maintenance and once the maintenance is done and the servers are back again, the administrator needs to explictly tell the application team to start with the message traffic, so instead of that we thought why not trigger the application as soon as the qmgr comes up.
Does this answer your question
Thanks again for solving my query |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 09, 2008 12:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
[quote="wbimb"]Does this answer your question[/query]
It does, though I still struggle to see the point rather. If the application needs to start when the queue manager does then why not simply start it as a service, dependant on the queue manager in the same way your amsget thing is now defined? If it's a triggered application that starts when a message arrives for it to process, why not let it start once the application team have been notified as you describe?
Still, your system, your requirements, your design. 
| wbimb wrote: |
| Thanks again for solving my query |
Thank you for answering ours.
 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wbimb |
| Posted: Fri May 09, 2008 1:51 am Post subject: |
|
|
Centurion
Joined: 17 Aug 2006
Posts: 144
|
We even tried doing that
we created a service that started the application, but somewhere the application is giving error in the first attempt to connect to the qmgr, but if we try and attempt it second time it works...which i feel need changes in the code, so till that changes are done we are trying a different approach |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
