I also forgot to answer on this thread... this was not the problem related to the lack of the memory, it's related to hanging connections, i've set up the broker with the large amount of memory (>2GB) in both broker configuration and via jconsole and problem was defintely in the connections which were not cleaned up - for unknown reason to me. it was easy to block queue with large number of un-properly closed sessions and relatively hard with properly closed connections in a shutdown hook.
thanks, igor On 6/30/06, skarthik <[EMAIL PROTECTED]> wrote:
Hi Hiram, I was wondering what is the relationship between the Broker memory limit set in the broker XML and the JVM heap size specified in when launching the broker. For example should the heap size be some extra percentage of the configured broker memory? I guess the broker memory can nenver be greater than the -Xmx value. thanks, karthik -- View this message in context: http://www.nabble.com/problems-with-ActiveMQ-with-large-number-of-producers-consumers-tf1823629.html#a5126960 Sent from the ActiveMQ - User forum at Nabble.com.
