This sounds like it could be https://issues.apache.org/jira/browse/AMQ-4595,
which was fixed in 5.9.0 (which uses the new HawtIO web console)...
On Wed, Oct 22, 2014 at 6:36 AM, sharma_arun_se
wrote:
> We are using 1.6.0_24 , 64 bit jdk
>
>
>
> --
> View this message in context:
> http://activem
We are using 1.6.0_24 , 64 bit jdk
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Error-Java-heap-space-viewing-queue-through-web-ui-having-400-messages-Adding-memory-paarmeters-do-n-tp4686431p4686625.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Which JDK are you using? I mean, its producer, platform
it runs on and if it's a 32 or 64 bits version.
--
Questo messaggio è di carattere riservato ed è indirizzato esclusivamente
al destinatario specificato. L'accesso, la divulgazione, la copia o la
diffusione sono vietate a chiunque altro ai
ActiveMQ service wrapper memory setting is:
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4096
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Error-Java-heap-space-viewing-queue-through-web-ui-having
We are using ActiveMQ version 5.8.0 on Java 1.6.
Currently when ActiveMQ queue contains lots of messages (says more than
400+), then clicking queue in ActiveMQ web UI use approx. 100% CPU/Memory
and ultimately dies with Java Heap space error.
Adding more memory parameters did not solve the probl
