I enabled debug logs to see what was happening when AMQ could not send ACK
within 30 secs. I started the AMQ broker on 28-Mar around 17:40 and to my
surprise, I find that the server startup is still going on even now at
29-Mar 09:30 (~16 hours!!). I see a lot of following messages in the logs :
To improve sending/receiving of ObjectMessages I used another serialization
framework (Kryo). I was a bit surprised, because the performance gain was
not as big es expected.
- When using Kryo with ActiveMQ it improved sending/receiving message with
about factor 2,5.
- In my stand alone Java
For the JMX: there is a newer setting in the activemq configuration file
that may override the command-line settings; here's a fairly stock example:
Check for these and any output during broker starting indicating the
management context failed to start -- if both
Hi Tim
thanks a lot for your reply.
What are your systemLimits, especially your storeUsage and memoryUsage?
Default configuration
Why is producerFlowControl="false"? The sole purpose of
We use standalone broker, because we write our applications in PHP. And we
don't use custom plugins.
I try configure jmx for jconsole, on localhost all works well, but i can't
connect to server over vpn.
I use this manual: http://activemq.apache.org/jmx.html
And here ACTIVEMQ_SUNJMX_START
Messages consumed fast, never seen more than 30 messages in queue. 90% of
time i see 0 messages in all queues and only consumed counter inreases.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-hangs-and-i-don-t-understand-why-tp4709963p4709978.html
Sent from
Catch this situation again. Even web-console hangs. But this time no info
even in log, only startup log info.
Maybe openjdk is not the best choice?
java -version
openjdk version "1.7.0_80"
OpenJDK Runtime Environment (build 1.7.0_80-b15)
OpenJDK 64-Bit Server VM (build 24.80-b11, mixed mode)
Or
Hi,
Is there any limit to the number of Topics that can be created on a single
broker? As per my understanding, there is no such limit and it depends on
the system in which the broker is running.
Problem observed which raised the above question :
I tried to simulate an issue which occurs in our
