| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| triggers |
« View previous topic :: View next topic » |
| Author |
Message
|
| njpmr |
 Posted: Mon Mar 12, 2007 6:11 pm Post subject: triggers |
 |
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
windows 2003 server. simple driver module, javaA, contains just a call to main of javaB. if javaB returns, javaA calls main javaC.
q records came from AS400, this 400 module is waiting while javaB processes Queue on windows server , AS400 then gets a message from javaB when its done. User intervention on AS400 then sends record back up to queue where javaC has been running polling the queue (same q) waiting for that record from AS400 so javaC can finish up. The problem is when as400 sends the record to the queue, javaA is starting all over again. TRigger is set for first 1.
This had been working, and in fact same modules are working on another production server. Server not working is MQ 5.3 csd 13 . Server working is MQ 5.3 csd 7. BUT , there is a set of queues on the 5.3 / 7 box that is not working. ANy ideas where to look. Thanks for even reading this far |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Mar 12, 2007 6:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Queues don't "work" or "not work" on their own.
Almost every single MQ problem is a problem with an application.
Start by troubleshooting your application logic.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| njpmr |
| Posted: Mon Mar 12, 2007 6:48 pm Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
The same exact code is working on one server. I guess I am asking could this have something to do with 5.3.13 vs 5.3.7.
Researching this it seems to be the scenario where trigger type first one is working like every because of the trigger interval, but this is the default 999999999 milliseconds. on both queues.
Need some ideas on where to look, running out |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Mar 12, 2007 8:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| njpmr wrote: |
The same exact code is working on one server. I guess I am asking could this have something to do with 5.3.13 vs 5.3.7.
Researching this it seems to be the scenario where trigger type first one is working like every because of the trigger interval, but this is the default 999999999 milliseconds. on both queues.
Need some ideas on where to look, running out |
This might be more along the logic of the reply to queue being the same as the intake queue.... Not a good design. Make the Replyto queue a separate queue and everything should be fine...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| njpmr |
| Posted: Tue Mar 13, 2007 2:49 am Post subject: |
|
|
Novice
Joined: 18 Jan 2007
Posts: 10
|
I had the same idea about the reply queue, that would probably be a simple remedy, and much better design. This was an old process previously set up on the job scheduler and I was just trying to retrofit the triggering. Just wondering what is causing this to behave like this as I am running the exact code on one server and there is no issue. We are setting up some new servers and during the testing this problem arose.
Obviously something is different but I can't pinpoint it. Are there some configuration settings that might impact this?
Thanks |
|
| 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
|
|
|
|
