istener
> for each worker thread? And if a listener thread is busy, with the request
> be delivered to one of the idle listener threads, so that multiple messages
> can be worked on in parallel in the server.
Yes, thats exactly what I try to do. I'll try with listeners.
>
>
CTED]> wrote:
>
> I am under the impression this is correct behaviour. See for example:
> http://java.sun.com/products/jms/tutorial/ page 63
>
>
> Sebastjan Trepca wrote:
> >
> > Hi,
> >
> > I'm using ActiveMQ(both versions are affected) with ST
Hi,
I'm using ActiveMQ(both versions are affected) with STOMP protocol and
noticed a problem with it. At least I hope it's a problem.
When you ACK a message through stomp, all messages until the right one
gets ACKed too.
If we check the code:
protected void onStompAck(StompFrame command) th
Hi all,
I'm having problems with acknowledge order in ActiveMQ 4.1.1 using
STOMP protocol. I'm using a queue with async mode on.
I'm also using these headers:
SUBSCRIBE
activemq.dispatchAsync:'true'
activemq.noLocal:'true',
activemq.retroactive:'true',
activemq.prefetchSize:1000,
activemq.maximu
Hi all,
I'm a newbie in ActiveMQ world and as I noticed in examples messages
get delivered to all consumers by default? I want to deliver only to
consumer that first receives the message and consumes it.
So the work flow would go like this:
1. get message
2. mark it as read(unreadable by other c
