| Author |
Message
|
| praveenmq |
 Posted: Sun Dec 21, 2014 2:19 am Post subject: Service as Trigger monitor is not working |
 |
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Hello All ,
I have just defined a Trigger monitor as a service in MQ V7.5 in windows environment.
I can see that the services started and the trigger.initq has a ipprocs connected, But unfortunately the messages are not being triggered.
I just opened a CMD prompt and ran the normal runmqtrm command and it is working fine.
No logs nothing since the ipprocs is connected when the service is started i dont have a clue how to check this service?
Any suggestions please?
Thanks
_________________
Jack |
|
| Back to top |
|
 |
| exerk |
| Posted: Sun Dec 21, 2014 3:10 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Post the definition of your service object and triggering parameters of your queue object here, and have you checked logs to see whether the "...messages are not being triggered..." errors appear in them? Event Viewer, StdErr that you may have defined in your service, or even anything on the Dead-Letter queue may be of help.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 21, 2014 4:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Also check the dead-letter queue to see if any trigger event messages are in it.
_________________
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 |
|
|
| praveenmq |
| Posted: Sun Dec 21, 2014 5:07 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Regarding stdout and std error nothing written in the log files its still 0KB. Files has the necessary permissions to be written but nothing is written
DLQ has zero messages.
Has i already told the ipprocs is 1 and it is connected but not triggerring the messages
_________________
Jack |
|
| Back to top |
|
|
| praveenmq |
| Posted: Sun Dec 21, 2014 5:15 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Please find the definitions below
display service('Command') 3 : display service('Command') AMQ8629 : isplay service information details.SERVICE(Command)SERVTYPE(COMMAND)STARTCMD(D:\IB\WebSphereMQ\bin\runmqtrm.exe)STARTARG(-m KAP1WM01 -q TRIGGER.INITQ)STOPCMD(D:\IBM\WebSphereMQ\bin\amqsstop)STOPARG(-m KAP1WM01 -p +MQ_SERVER_PID+)STDOUT(D:\IBM\WebSphereMQ\errors\tm1.txt)STDERR(D:\IBM\WebSphereMQ\errors\tm2.txt)DESCR()ALTTIME(02.02.07)ALTDATE(2014-12-21)CONTROL(QMGR)Display process(BILL_PAYMENT_APPLICATION)4. display process(BILL_PAYMENT_APPLICATION)AMQ8407 : Display Process details.
PROCESS(BILL_PAYMENT_APPLICATION)APPLTYPE(WINDOWSNT)APPLICID(c:\billpaymentprod\exe\billpayment.exe)ENVRDATA()USERDATA()DESCR( The bill payment e-service application)ALTDATE(2014-11-23)ALTTIME(23.04.41)
_________________
Jack |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 21, 2014 9:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Display attributes of the application QLocal.
_________________
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 |
|
|
| bruce2359 |
| Posted: Sun Dec 21, 2014 9:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Display attributes of the application QLocal.
Display the attributes of the initiation QLocal.
For purposes of readability, please separate each DISPLAY command and results by a blank line.
_________________
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 |
|
|
| praveenmq |
| Posted: Sun Dec 21, 2014 10:10 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Qlocal attibutes
dis ql(BILL_PAYMENT_REQ)
1: dis ql(BILL_PAYMENT_REQ)
AMQ8409: Display Queue details.
QUEUE(BILL_PAYMENT_REQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2014-12-11)
ALTIME(01.55.57) BOQNAME()
BOTHRESH(0) CLUSNL()
CLUSTER() CLCHNAME()
CLWLPRTY(0) CLWLRANK(0)
CLWLSEQ(QMGR) CRDATE(2014-11-23)
CRTIME(23.04.39) CURDEPTH(0)
CUSTOM() DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFPRESP(SYNC) DEFREADA(NO)
DEFSOFT(SHARED) DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Local Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ(TRIGGER.INITQ)
IPPORCS(0) MAXDEPTH(10000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) MONQ(QMGR)
NPMCLASS(NORMAL) OPPROCS(2)
PROCESS(BILL_PAYMENT_APPLICATION) PUT(ENABLED)
PROPCTL(COMPAT) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEU(NONE) QSVCINT(999999999)
RETINTVL(99999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA() TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(EVERY)
USAGE(NORMAL)[/img]
_________________
Jack |
|
| Back to top |
|
|
| praveenmq |
| Posted: Sun Dec 21, 2014 10:28 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
INITIATION QUEUE Attributes
dis ql(TRIGGER.INITQ)
2: dis ql(TRIGGER.INITQ)
AMQ8409 : Display Queue details.
QUEUE(TRIGGER.INITQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2014-11-23)
ALTTIME(23.04.40) BOQNAME()
BOTHRESH(0) CLUSNL()
CLUSTER() CLCHNAME()
CLWLPRTY(0) CLWLRANK(0)
CLWLSEQ(QMGR) CRDATE(2014-11-23)
CRTIME(23.04.40) CURDEPTH(0)
CUSTOM() DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFPRESP(SYNC) DEFREADA(NO)
DEFSOFT(SHARED) DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Local Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ()
IPPROCS(4) MAXDEPTH(5000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) NOTRIGGER
NPMCLASS(NORMAL) OPPROCS(0)
PROCESS() PUT(ENABLED)
PROPCTL(COMPAT) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(99999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA() TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(NORMAL)
_________________
Jack |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sun Dec 21, 2014 2:03 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
You may refer this link .
Hope this will be helpful.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| tczielke |
| Posted: Sun Dec 21, 2014 2:04 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
You pasted the STARTCMD on your trigger monitor service as:
STARTCMD(D:\IB\WebSphereMQ\bin\runmqtrm.exe)
It looks like the IBM in the directory path is incorrectly typed. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 21, 2014 3:06 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| praveenmq wrote: |
Qlocal attibutes
dis ql(BILL_PAYMENT_REQ)
1: dis ql(BILL_PAYMENT_REQ)
AMQ8409: Display Queue details.
QUEUE(BILL_PAYMENT_REQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2014-12-11)
ALTIME(01.55.57) BOQNAME()
BOTHRESH(0) CLUSNL()
CLUSTER() CLCHNAME()
CLWLPRTY(0) CLWLRANK(0)
CLWLSEQ(QMGR) CRDATE(2014-11-23)
CRTIME(23.04.39) CURDEPTH(0)
CUSTOM() DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFPRESP(SYNC) DEFREADA(NO)
DEFSOFT(SHARED) DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Local Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ(TRIGGER.INITQ)
IPPORCS(0) MAXDEPTH(10000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) MONQ(QMGR)
NPMCLASS(NORMAL) OPPROCS(2)
PROCESS(BILL_PAYMENT_APPLICATION) PUT(ENABLED)
PROPCTL(COMPAT) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEU(NONE) QSVCINT(999999999)
RETINTVL(99999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA() TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(EVERY)
USAGE(NORMAL)[/img] |
I see TRIGTYPE(EVERY), but neither TRIGGER nor NOTRIGGER. Did you edit this?
_________________
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 |
|
|
| bruce2359 |
| Posted: Sun Dec 21, 2014 3:23 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| tczielke wrote: |
You pasted the STARTCMD on your trigger monitor service as:
STARTCMD(D:\IB\WebSphereMQ\bin\runmqtrm.exe)
It looks like the IBM in the directory path is incorrectly typed. |
Good eye. The usual install path on Windows was/is C:\Program Files\IBM\WebSphere MQ\ ...
If the service application could not be found (because the service def specified an incorrect filesystem path), I'd expect the qmgr to write this to AMQERR01.LOG. I'm surprised that you found nothing in the error logs for this qmgr. Did you look in AMQERR01.LOG in ...\IBM\WebSphere MQ\qmgrs\<your qmgr name>\errors\ ?
_________________
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 |
|
|
| praveenmq |
| Posted: Sun Dec 21, 2014 10:03 pm Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
While copy/paste i think the M is missed.
MQ is not installed in the default path. Its installed in D: drive so the start command path is correct.
_________________
Jack |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Dec 22, 2014 6:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It seems odd that there would be something wrong with the definition of the queue if manually running the trigger monitor against the same initq works.
It likewise seems odd if a process started by the queue manager is unable to connect to the queue manager, or otherwise has a failure.
It's more possible that the trigger monitor, when run by the queue manager as the queue manager user (MUSR_MQADMIN ,probably) would be unable to access the program it's trying to trigger (c:\billpaymentprod\exe\billpayment.exe from the process definition), and that when the trigger monitor is run by an interactive user, it does have access.
As a side note, praveenmq, you could also look at using supportPac MA7K as a trigger monitor. It can run as a local bindings application as well as a client application. |
|
| Back to top |
|
|
|
|
