JMS dies after main thread exits

Hi, In Java when the main thread exits, all remaining working threads should continue. I have created Threads where messages are received and processed and committed. I expected my spawned threads to continue processing messages well after the main thread exits - they die mysteriously after the

Re: message selectors

infrastructure to incorporate) give to this situation? James.Strachan wrote: > > On 11/10/2007, Terry K <[EMAIL PROTECTED]> wrote: >> >> ... thanks for the suggestions - message groups do sound like a plausible >> solution. >> >> I am not interested in assigning a g

Re: transacted sessions in multi-threaded client

message and use it within a thread. Problem is, Apache Commons Pooling does not allow iteration of items in a pool - to find the session with all the messaages. What is the lowest prefetch limit that would ensure good throughput of messages without pulling too often from the broker terry k ttmdev

Re: message selectors

... thanks for the suggestions - message groups do sound like a plausible solution. I am not interested in assigning a group of messages to particular sessions indefinately as the groups will be small and many. Once the high priority message has been dequeued with all related messages (at that po