Hey,
I saw several posts on this issue, but still cannot understand exactly how to fix the problem we encounter.
We use the _HQ_SCHED_DELIVERY mechanism in our system in order to poll on some background operations and perform asyncrhnours jobs accordingly.
We encounter two types of problems:
1. From time to time, we see that some messages are stuck in queue (until we restart it)
2. (more frequenatly) we see that messages are proccessed after a long duration of time (much more then we requested in the _HQ_SCHED_DELIVERY configuration).
Although problems number 2 sounds like a backend-system problem (a.k.a we don't have enough resources to handle messages, so they wait in the queue) - we don't see any kind of stress in our system (we have listeners waiting in idle status).
If anyone has a clue on it - I will be happy to hear.
I want to fouces more on problem number 1, as it caused some of our operations to fail (to stuck, actually).
We used the JMX in order to get some data on the stuck mesasges.
We see some messages in "scheduled" status, for example:
{"timestamp":1369775436655,"userID":"ID:0abe608e-c7db-11e2-ac21-056db8376617","messageID":112886914,"expiration":0,"address":"jms.queue.AsyncStateMachineQueue","priority":4,
"opId":"4258581110782359378","_HQ_SCHED_DELIVERY":1369775446655,"durable":true,"type":2,"rvlMessageId":"c53d245b-6e91-4c45-88f5-c3ff1f372f33"}]
And some messages in "delivering" status, for example:
{"timestamp":1369764475319,"userID":"ID:85473c71-c7c1-11e2-ac21-056db8376617","messageID":110830833,"expiration":0,"address":"jms.queue.AsyncStateMachineQueue","priority":4,
"opId":"5252520669007945711","_HQ_SCHED_DELIVERY":1369764485319,"durable":true,"type":2,"rvlMessageId":"4c2814e6-6eff-4d17-a4a8-e80abc0470a3"},
Any ideans what should we look for?
Thanks
