hi, I have done a bit testing and I am able to reproduce my problem all the time. Here is what I observed:
All consumers and producers are listening and posting on the same queue. First 1 consumer, 1 producer -> no memory problems Second 1 consumer, 2 producers -> no memory problems Third 2 consumers, 1 producer -> memory problem, the memory raises till it hits 100 and then the clients die Fourth 2 consumers, 2 producers -> memory problem, the memory raises till it hits 100 and then the clients die Even when I kill the clients, before memory reaches 100, it doesn't frees the memory and it stays at the fixed size. I am also using a AMQ post 10.05.2006 -----Ursprüngliche Nachricht----- Von: Attila_Szegedi [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 31. Mai 2006 13:22 An: [email protected] Betreff: Re: Broker Hung With Following VM Dump Now, I noticed that the Broker object in JMX does report MemoryPercentageUsed=100, but I can't fathom why. Also, I now split the processors for queues A and B into separate set of sessions, but still can't get it to work - I believe the MemoryPercentageUsed=100 is to blame. I'll try restarting the broker with higher memory, but this is rather problematic regardless -- View this message in context: http://www.nabble.com/Broker+Hung+With+Following+VM+Dump-t1627677.html#a4642632 Sent from the ActiveMQ - User forum at Nabble.com. This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message.
