| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger Control drops off (MQ 5.3 CSD4 w2k Server) |
« View previous topic :: View next topic » |
| Author |
Message
|
| mthynell |
 Posted: Thu Apr 28, 2005 2:52 am Post subject: Trigger Control drops off (MQ 5.3 CSD4 w2k Server) |
 |
|
Newbie
Joined: 28 Apr 2005
Posts: 2
|
Hi,
my brobelm is that trigger control will change to 'OFF' even how many times I change is to 'ON*. I have done this from MQ Explorer and from command line like
ALTER QLOCAL(QUEUE.NAME) TRIGGER
Both will work for a while but then queue will change triggering off all by it self.
Trigger Type is 'depth' (200)
Any ideas how to solve this?
_________________
mt |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Apr 28, 2005 3:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's working the way it's supposed to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Apr 28, 2005 5:33 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
From the Application Programming Guide
| Quote: |
Triggering by depth
With triggering by depth, the queue manager disables triggering (using the TriggerControl attribute) after it creates a trigger message. Your application must re-enable triggering itself (by using the MQSET call) after this has happened.
The action of disabling triggering is not under syncpoint control, so triggering cannot be re-enabled simply by backing out a unit of work. If a program backs out a put request that caused a trigger event, or if the program abends, you must re-enable triggering by using the MQSET call or the ALTER QLOCAL command.
|
|
|
| Back to top |
|
|
| mthynell |
| Posted: Thu Apr 28, 2005 9:12 pm Post subject: |
|
|
Newbie
Joined: 28 Apr 2005
Posts: 2
|
| kevinf2349 wrote: |
From the Application Programming Guide
| Quote: |
Triggering by depth
With triggering by depth, the queue manager disables triggering (using the TriggerControl attribute) after it creates a trigger message. Your application must re-enable triggering itself (by using the MQSET call) after this has happened.
The action of disabling triggering is not under syncpoint control, so triggering cannot be re-enabled simply by backing out a unit of work. If a program backs out a put request that caused a trigger event, or if the program abends, you must re-enable triggering by using the MQSET call or the ALTER QLOCAL command.
|
|
OK. Thank you both. I have to chance my procedure or type of triggering.
_________________
mt |
|
| 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
|
|
|
|
