In most cases, I would expect a 1GB message to cause out-of-memory
conditions.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Exception-in-thread-ActiveMQ-Broker-localhost-Scheduler-java-lang-OutOfMemoryError-Java-heap-space-tp4680994p4681001.html
Sent from the ActiveMQ
Was a heap dump taken in order to find where the memory was being used?
If not, reproducing the problem and grabbing a heap dump after the
out-of-memory is reported (or using the create-heap-dump-on-oom JVM option)
will make it feasible to track this down.
Based on the description of the problem,
Hi All,
I am having "java.lang.OutOfMemoryError: Java heap space" error while
starting an activemq broker. I am using: apache-activemq-5.9.0
The broker was configured for persistent storage using oracle
database. The broker could start normally, then i manually created an
queue and
any chance you took a heap dump?
-
http://www.christianposta.com/blog
--
View this message in context:
http://activemq.2283324.n4.nabble.com/java-lang-OutOfMemoryError-Java-heap-space-tp4655291p4655364.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
hi, all~
i met "java.lang.OutOfMemoryError: Java heap space" error while
starting an activemq broker. I am using: apache-activemq-5.6.0-win
The broker was configured for persistent storage using oracle
database. The broker could start normally, then i mannally created an
queue and
