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.
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
Yes, I already posted broker log when I post this issue first time. See top
of this topic.
The log from wrapper/broker is:
2014-02-12 15:46:46,812 | WARN | /admin/queues.jsp |
org.eclipse.jetty.servlet.ServletHandler | qtp1530088410-59
javax.el.ELException: java.lang.reflect.UndeclaredThrowableE
We have default setting for persistent (ActiveMQ 5.8.x):
Also we did not specify broker option "deleteAllMessagesOnStartup". So it
must have its default value i.e. false
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Problem-with-JMX-m
Below are answers:
>>Is that the exception from the attempt to access the queue via JMX, or
from the web console?
Ans: Both. I am getting this error from both JMX and/or from the web
console.
>> If it's from the web console, are you hitting the main Queue page, or
>> trying to hit the browse pag
Agree with you. We have no messages in DLQ, when I restarted ActiveMQ
service.
But ActiveMQ web-console queue tab (http://localhost:8161/admin/queues.jsp)
must be visible to me which has other queue.
But currently, it is throwing error when I click queue tab in ActiveMQ
web-console.
"
Error!
Ex
