| Author |
Message
|
| gpklos |
 Posted: Mon Oct 27, 2003 10:53 am Post subject: Initiation Queue Depth Greater than one. |
 |
|
Centurion
Joined: 24 May 2002
Posts: 108
|
We have an application which runs on a Compaq Tru64 box running MQ 5.1. The application is JAVA based. What seems to happen is on occasion the INITIATION Queue has more than one message on it at a time. The queue that is being triggered is also open for INPUT. So I don't know why the queue manager would bother putting a message on the initiation queue when the queue is already being serviced. Even if the application was in a hung state or something similar, the queue is still showing that it is open for input. This only happens with the JAVA application. Has anyone seen anything similar to this or know what is causing it or how to fix it?
Thanks,
Gary |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Oct 27, 2003 11:24 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| You can trigger many queues by pointing to one INITQ. The INITQ you are concerned with, is explicitly used by just one queue? |
|
| Back to top |
|
|
| gpklos |
| Posted: Mon Oct 27, 2003 11:45 am Post subject: |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
| I forgot to mention that. That initiation queue is monitoring only one queue. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 27, 2003 12:38 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What are the triggering properties of the queue in question?
What kind of trigger monitor are you running?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gpklos |
| Posted: Tue Oct 28, 2003 4:00 am Post subject: |
|
|
Centurion
Joined: 24 May 2002
Posts: 108
|
I'm using the basic trigger monitor that comes with MQ for TRU64, RUNMQTRM. It works fine for everything we have ever needed it for aside from this.
The trigger properties are set to trigger on FIRST, with a trigger depth of one, and no trigger message priority. The INITIATION Queue has a default input option of exclusive. There is no clustering involved.
Thanks |
|
| Back to top |
|
|
|
|
