On 5/21/07, camper <[EMAIL PROTECTED]> wrote:
in activemq.xml i have usageManager set to 4096 MB, this is the output when
it dies
Note that setting does not affect the JVM heap size; try changing that.
--
James
---
http://macstrac.blogspot.com/
in activemq.xml i have usageManager set to 4096 MB, this is the output when
it dies
Exception in thread "ActiveMQ Transport: tcp:///192.168.2.184:52359"
java.lang.OutOfMemoryError: Java heap space
Exception in thread "ActiveMQ Transport: tcp:///192.168.2.182:35570"
java.lang.OutOfMemoryError: Jav
On 5/21/07, camper <[EMAIL PROTECTED]> wrote:
You were right, when i disabled advisory support those topics stopped showing
up. I am getting Out of Memory errors and I thought that that might be a
problem, messages being queued but not consumed. I am using a Snapshot
version of 4.2, are you aw
You were right, when i disabled advisory support those topics stopped showing
up. I am getting Out of Memory errors and I thought that that might be a
problem, messages being queued but not consumed. I am using a Snapshot
version of 4.2, are you aware of any known issues that would cause an java
Hi,
I believe what you're seeing are advisory topics which are automatically
created by default by activemq to send advisory messages to monitor the
behavior of the system (ie. starting of connections, creation of
destinations, etc).
http://activemq.apache.org/advisory-message.html
Btw, you