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,
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.
