| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Triggerinterval firing when queue is still open |
« View previous topic :: View next topic » |
| Author |
Message
|
| timcl |
 Posted: Mon Mar 03, 2003 5:50 pm Post subject: Triggerinterval firing when queue is still open |
 |
|
Novice
Joined: 16 May 2001
Posts: 23
Location: Australia
|
I am have a queue with trigger FIRST and an application
that is doing a GET with a WAITINTERVAL of 5 minutes.
The application is staying running for hours keeping the
queue open, but the TRIGGERINTERVAL is still generating
extra trigger messages.
My understanding from the Appl. Prog. Guide (Chapter 14)
in "Conditions for a trigger event" point 11 is that
for a trigger message to be generated by the TRIGGERINTERVAL
conditions 2-10 (excl. 3) must be satisfied and condition 4
is that the queue must have an OpenInputCount of 0.
So, if the application still has the queue open, why are
these extra trigger messages being generated ? |
|
| Back to top |
|
 |
| kolban |
| Posted: Mon Mar 03, 2003 9:20 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
| Hmmm ... this is my undertstanding too. I think we may need to see the queue definitions on the queue in question. Are you 100% certain that the queue is being kept open? Are you sure that the program is being triggered because of activity on the queue that you think is opened? What does your PROCESS definition look like for the app to be triggered? |
|
| Back to top |
|
|
| timcl |
| Posted: Tue Mar 04, 2003 3:44 pm Post subject: |
|
|
Novice
Joined: 16 May 2001
Posts: 23
Location: Australia
|
As far as being 100% sure it open all the time, I can only say that it is only triggered once at around 7am and the process remains running and every time I check the status of the q it has the process open against it.
Three things to note :-
1) The application is connecting as a client on the same machine
2) The triggering is all working fine except for the extra trigger msgs
3) Another queue with the same setup but lower volume is triggering, opening and closing but not generating extra trigger messages
Here are the queue and process definitions :-
DEFINE QLOCAL('P1.CMS.JETFORM.PRINT.CONTROL') +
DESCR('Control q for jetform printint') +
SHARE +
TRIGMPRI(0) +
TRIGDPTH(1) +
TRIGTYPE(FIRST) +
TRIGDATA(' ') +
BOQNAME(' ') +
PROCESS('P1.CMS.JETFORM.PRINT.CONTROL.PROC') +
DEFPRTY(0) +
MAXMSGL(4194304) +
BOTHRESH(0) +
MAXDEPTH(640000) +
TRIGGER +
DEFSOPT(SHARED) +
HARDENBO +
MSGDLVSQ(FIFO) +
PUT(ENABLED) +
GET(ENABLED) +
DEFPSIST(NO) +
USAGE(NORMAL) +
SCOPE(QMGR) +
RETINTVL(999999999) +
QDEPTHLO(20) +
QDEPTHHI(81) +
QSVCINT(999999999) +
QSVCIEV(NONE) +
QDPMAXEV(ENABLED) +
INITQ('SYSTEM.DEFAULT.INITIATION.QUEUE') +
QDPHIEV(DISABLED) +
QDPLOEV(DISABLED) +
CLUSTER(' ') +
CLUSNL(' ') +
DEFBIND(OPEN) +
STGCLASS(' ') +
REPLACE
DEFINE PROCESS('P1.CMS.JETFORM.PRINT.CONTROL.PROC') DESCR(' ') +
APPLTYPE(WINDOWSNT) +
APPLICID('c:\MQJetform\etc\jetformcontrol.bat') +
USERDATA('MEL2KP06(1444)') +
ENVRDATA(' ') +
REPLACE |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Mar 04, 2003 4:00 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
I will venture a guess here, but I might be way off. Both you and Neil are correct that triggering shouldn't occur when the queue is open. However, looking at your process definition I see: "'c:\MQJetform\etc\jetformcontrol.bat'" as the APPLICID. Now, at least on UNIX, if your APPLICID field is starting a script or program, and you don't have an '&' at the end of it to run the process in the background, then the trigger monitor will run the triggered application in the foreground. In other words, the trigger monitor will be tied up waiting for the application to end, and won't be able to service the initiation queue, which could allow trigger messages to pile up.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| timcl |
| Posted: Tue Mar 04, 2003 4:29 pm Post subject: |
|
|
Novice
Joined: 16 May 2001
Posts: 23
Location: Australia
|
Hi Brandon,
You're right, the trigger monitor will be tied up waiting for the application to end, but I didn't think there should be any more trigger messages being generated to build up on the queue. (Note: this it the only application running on this initq, other application runs on a separate initq).
Cheers,
Tim. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Mar 04, 2003 7:45 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3265
Location: London, ON Canada
|
Hi,
On Unix, use "&" (post-fix) but on Windows use a prefix of "START".
i.e.
| Code: |
| APPLICID('START c:\MQJetform\etc\jetformcontrol.bat') + |
This will cause jetformcontrol.bat to be executed in the background.
later
Roger...
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
