I have multiple instances of activemq 5.9 and 5.11.1 and have no problems
accessing the jolokia interface but on my one instance of 5.13.0 I get a 503
Service Unavailable. I can't find a difference in configuration. From what I
have seen Jolokia is supposed to be enabled by default.
--
View this
What is the 5.12 incompatibility with new openwire?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/No-cleanup-on-scheduler-logs-tp4704382p4704425.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I have several instances of 5.11.1 where cleanup is not occurring on
scheduler logs in the data/localhost/scheduler folder. The log files data
back to the instance creation. I have enabled the kahadb logging and it
never shows those files as a candidate for garbage collection.
log4j.appender.kahad
Thanks for the suggestions, we will try that right now I am travelling
and away from work.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-tp4701242p4701483.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
At this time I think they are synchronous. They are persistent messages so
this would be the default I think. At one time we specified asynchronous but
it looks like that has been removed.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-t
There is a specific queue that gets the scheduled messages and generally a
single consumer thread on that queue. That consumer is part of the same
application that is pulling from all the other queues.
We don't use selectors on any queue, of which there are 15, nor do we have
any destination based
I would modify my last statement to add that there is one consumer that still
processes data while everything else is paused. What is unique about that is
that all messages published to that queue are delayed (scheduled) messages
and I am guessing that they are handled differently internally in AMQ
Pretty much everything grinds to a halt... all the consumers stop processing.
Each 'application' has multiple consumer threads pulling from multiple
queues, they all pause. and if there are 2 application instances they
both pause. It's as if there is a single thread feeding all consumers and i
We have a finite set of message groups - 20 (0-19)
We are monitoring the consumers via JMX and at one time were having issues
with memory leaks and GC operation that have since been solved. Now
everything looks good on the consumer side.
There are variations in how long messages take to process -
I have not been seeing anything in the broker logs indicating that PFC is
occurring and I have also tried adding to disable it entirely without effect.
I'm not currently seeing any detail in the GC operation, only that there is
no obvious sign of memory issues when this happens. I'll see if we c
Yes, we have done that and there doesn't seem to be any sign of trouble.
Threads are ~ 100 and memory is well below maximum.
The way the system works we have producers publishing to a single queue, the
consuming application then processes those messages and publishes to a bunch
of secondary queues
The producer continues to send and message build in the queue. The consumers
resume on their own usually and empty the queue but a while later the same
thing happens again.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-tp4701242p4701244.h
I have an issue where my consumer stops receiving messages for 10 or 15
minutes, then resumes. This is load dependent - the faster the message rate
the more frequently it occurs. We have assumed that it is an issue at the
consumer level but have not been able to pin down the cause.
However, someti
13 matches
Mail list logo
