hi all:
need your help.
ActiveMq version is 5.12.1, using mqtt protocol:
I want keep alive adjust to 6 minutes, so I define, but what I setting,
the keep alive remain 30 seconds:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/how-to-setting-k
I've developed a small routing application like camel.
In one test scenario, I have a producer sending messages to Queue1. Then a
consumer receives messages from Queue1 and directly pass them to Queue2.
Then a consumer receives messages from Queue2 and pass them to Queue3, and
so on. In the end,
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
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
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
... 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