Hi Tim,
Did you got a chance to look at this?
Thanks,
Abhi
--
View this message in context:
http://activemq.2283324.n4.nabble.com/KahabDB-compatibility-issue-between-ActiveMQ-5-10-and-ActiveMQ-5-11-tp4692008p4696555.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I already gave prefetch size 1 a try - then only one message at a time is
delivered, the next message gets not delivered until the current is
acknowledged. So this is the worst case with one consumer - all other
messages wait for the long lasting message before getting processed.
--
View this m
I'm using MQTT WebSocket,sometimes the client can not connect to the activeMQ.
However on the localhost/admin/connections.jsp the connection is created
Connector ws
Name Remote Address Active Slow
example-605041351aMQTTSocket_1426037866truefalse
And I can not close the connection ,even
Splitting your bean into 4 shouldn't be necessary; give it a shot with a
prefetch size of 1.
On May 14, 2015 2:37 PM, "Elmo" wrote:
> Hello Tim,
>
> thanks a lot for your reply.
>
> Yes, a different prefetch size changed the number of waiting messages: the
> smaller the size, the smaller the numb
Hello Tim,
thanks a lot for your reply.
Yes, a different prefetch size changed the number of waiting messages: the
smaller the size, the smaller the number of waiters. E.g. prefetch size 20
made 19 messages waiting, 2 made 1 waiting. A prefetch size 0 had the effect
that no Message was delivered
Where in your configuration have you tried to implement your third
requirement?
And more importantly, what makes you think it's the right requirement? If
a producer sends a single message that is invalid or that hits a bug in
your client code, all message processing on that destination will stop
Did changing jms.prefetchPolicy.queuePrefetch to other values change the
number of messages stuck behind the long-running message, just not bring it
to zero? Or did it have no effect (i.e. still 62 messages stuck)?
Prefetch is the key here; any messages dispatched to the consumer that gets
the lo
I am using AMQ and have problem with DLQ because I don't like a redelivery
policy with DLQ .
My requirements are :
1) no loosing messages and hold the correct order
2) minimize messages in memory and hold how many possible message in
persistent storage
3) redelivery policy : each message must be
Hello,
I've got a MessageDrivenBean, running in Glassfish 3.1.2, listening to an
ActiveMQ 5.9.0 Queue. When a Message is processed and needing a long time,
other messages wait for processing.
Test scenario: Sending a big message (needing approx. 30 minutes to process)
and 250 small messages while
hi, we are using activemq 5.11.1 and mqtt protocol.
but we found that in some special topic, for example BW9vxkjPZY6kFwBB
and using clientId defined the same as the topic, the client will receive
the same message for twice.
but if I change another clientId, the message will be receive only once
10 matches
Mail list logo
