|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Trigger monitor not triggering |
« View previous topic :: View next topic » |
Author |
Message
|
vennela |
Posted: Wed Jun 30, 2004 8:51 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
You should be able to view why the app did not get triggered in your nohup.out or wherever you redirected the output of nohup. |
|
Back to top |
|
 |
TimDroz |
Posted: Wed Jun 30, 2004 8:54 am Post subject: |
|
|
Novice
Joined: 04 Mar 2004 Posts: 20
|
Yes, the actual error we're seeing now is:
Code: |
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
/home/pdapps/puradm/bin/receive_mrr 'TMC 2MRR.QL MRR.PR
/home/pdapps/puradm/bin/receive_mrr
JBXSD170
'
====receive_mrr: start at Wed Jun 30 09:51:08 2004
receive_mr: error while connecting:
ORA-03113: end-of-file on communication channel
receive_mr: quitting.
End of application trigger.
__________________________________________________
Waiting for a trigger message
|
The application guys are looking into it... I don't think it has anything to do specifically with MQSeries... perhaps some kind of permissions or environment variables that need to be set properly. |
|
Back to top |
|
 |
kman |
Posted: Wed Jun 30, 2004 10:00 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003 Posts: 309 Location: Kuala Lumpur, Malaysia
|
Tim, it's good to know that you have narrowed down the problem area. Now that you have runmqtrm in foreground, you can get the screenshot of the activity.
The interesting part here is what is the error registered in that runmqtrm output. The application itself should give an mq return code, if necessary. However since you said you can run it standalone outside of runmqtrm, I would say this have something to do with access and authority, plus where the TRM was run. In fact it should no be application error at all.
I think if you run a search on this forum, you will find some answers. |
|
Back to top |
|
 |
hi_sharan |
Posted: Fri May 30, 2014 2:05 am Post subject: |
|
|
Newbie
Joined: 30 May 2014 Posts: 3
|
Actually same issue is going on for me also.
The message is stucking in the queue without triggering the application.
Additionally,I am getting the error in the log,like "NO destination queue exists".
I mentioned all the trigger settings in the queue.
Still,what is that "NO destination queue exists". error in the log.
I am not using the default initiation queue name.I created one initiation queue and I gave that name.
Kindly provide me the solution. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 30, 2014 5:03 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
hi_sharan wrote: |
Still,what is that "NO destination queue exists". error in the log.
I am not using the default initiation queue name.I created one initiation queue and I gave that name.
Kindly provide me the solution. |
Please post the entire error here, including the error message id. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
hughson |
Posted: Fri May 30, 2014 6:19 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
|
Back to top |
|
 |
tczielke |
Posted: Fri May 30, 2014 8:44 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010 Posts: 941 Location: Illinois, USA
|
TimDroz wrote: |
Well, after starting up runmqtrm at the command line without nohup, leaving the process in the foreground and not redirecting any output, it appears that the trigger is firing, but the application itself is encountering an error of some kind. This is odd in and of itself, because I can run the receive_mrr process manually from the command line as the mqm user and it processes fine (when the trigger fires it, I'm getting some kind of Oracle error). |
When you run the receive_mrr process manually from the command line as the mqm user and it processes fine, are you also giving it that painfully long command line argument (that starts with TMC) for the trigger information? Or did you run it with no command line arguments? |
|
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
|
|
|
|