Found the problem and Solution
The number of outstanding messages received by a consumer and not committed
is dependent on the amount of memory allowed by MemUsageLimit.
Once I upped things began to hum again.
shridharv wrote:
>
> Our consumer stops receiving further messages aroun
Hi,
Our consumer stops receiving further messages around 1000 messages.
A commit has not been done at this point, as the consumer is waiting to get
a whole batch of messages before processing them and then doing a
Session.Commit. We need the ability to keep the Commit pending until we get
even u
Hi,
Was this issue figured out ?
We have the same problem, wherein a consumer stops receiving further
messages, as it has not committed after receiving around 1000 messages. We
cannot commit until we get a set of messages and hence the consume is
waiting indefinitely.
Any suggestions welcome.
Am
I need to configure Jetty's threadpool and connector parameters like
minresourcecount, within ActiveMQ.
Started with a problem with Jetty's default thread usage being higher than
needed.
Tried different things, did not work..
A sample would help
thanks
--
View this message in context:
http:/
I need help in setting selectors in the http interface and selecting messages
in the webconsole queues page.
shridhar
--
View this message in context:
http://www.nabble.com/Selector-in-webconsole-rest-http-interface-tp20512388p20512388.html
Sent from the ActiveMQ - User mailing list archive at N
--
View this message in context:
http://www.nabble.com/Selector-in-webconsole-rest-http-interface-tp20512383p20512383.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
has been
addressed by a consumerid parameter (not tested by me yet)..
shridhar
-
shridharv wrote:
>
> Writing a simple http client without a http library;
> 1. formatted the http header with ?destination=Qname&type=queue
> 2. payload is in the content with the content-length s
Writing a simple http client without a http library;
1. formatted the http header with ?destination=Qname&type=queue
2. payload is in the content with the content-length set correctly
3. message gets added to queue Qname
4. The mesage in the queue does not have any payload data
5. we need to do it