Bug 4895110 - broker w/ -shared sometimes stops sending msgs to a consumer

I am not confident this issue was (is) resolved. I am running 3.5 SP2 now, and i have a comsumer process that during a busy period, stops getting msg's out of queue.

i know there are many many msg's waiting, and if i stop IMQ (broker) and restart, then restart my consumer, it picks them up fine....but until i do, the consumer is stalled from getting any messages.

over nite, i have another process that loads many msg's into this queue....and it seems during this process, that the other consumer process stops working.

as i mentioned, the only way i can get it going again is to stop/restart IMQ

is it possible this bug is not completely resolved, or is there something i need to do in my enviornment or code to compensate?

Thanks in advance for any help.

Randy

[838 byte] By [randyhann] at [2007-11-25 18:07:15]
# 1

we do not know of any issues with the shared thread pool

which were not fixed with SP2. Its possible that you are

running into a new issue.

A couple of initial questions ...

Do you see the issue when running with the dedicated

thread pool ?

How are you acknowledging messages ? (dupsOK,

client ack, etc)

Did you make any changes to consumer flow control

for the consumer ?

Does stopping/starting the consumer have the same

behavior as stopping the broker ?

What platform are you running on ?

Do other consumers work fine when the consumer stops

(e.g. can you attach a new consumer or use imqcmd) ?

Linda_Schneider at 2007-7-3 17:47:09 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...
# 2

i dont have all your answers yet, but can answer a few

running on Windows Server 2000....1.4.2_04 JDK

i have not changed any of the defaults for flow control

stoping/starting the consumer will NOT "kick start" it...only stopping/starting the IMQ broker, then starting the consumer does the trick

i have two other consumer programs running monitor two other queues inside same broker, and they are still servicing fine....it is one of them, that feeds this third queue (that goes dead) actually

i have not tried to add a second consumer to this queue when this first one seems to go dormant; but i can try it the next time is freezes (likely tonite)

thanks for you help

Randy

randyhann at 2007-7-3 17:47:09 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...