Hi James,

I haven't had a chance to use JProbe yet, but will attempt that later today

A few things I noticed were:

The Smack 3.0.4 client has a history of memory issues and there were several
threads on the Ignite forums regarding the memory issues. I did some testing
on my own on the Smack client and if I simply do continuous
muc.sendMessages, then I run into Out of Memory exceptions. Someone
suggested doing a muc.nextMessage() (which is basically a pull on the muc
room) after the sendMessage and that actually prevents the OOM error (it
also reduces the efficiency by quite a bit). I'll try with the Smack 3.1.0
libraries but I believe the issue still persists in the latest version.

Though not a permanent fix, it might be useful until Ignite fixes all the
OOM issues with the Smack clients.

Here are some references to the OOM errors at Ignite:
http://www.igniterealtime.org/community/message/189102





James.Strachan wrote:
> 
> Running your app using a profiler (either the one in the JDK or JProbe
> or something) would provide useful diagnostics as to what's hogging
> all the RAM - is it the Smack client or something in Camel.
> 
> 2009/3/17 orton <[email protected]>:
>>
>> Ran some more tests with more memory for the publisher and subscriber,
>> and it
>> still runs out of memory. If I give the the sending and receiving JVM
>> each
>>
>> -Xms256M -Xmx512M -Xmn40M
>>
>> It runs out of memory at around 54000 4KB messages sent and received.
>>
>> Doubling the memory causes it to die around 102000 4KB messages sent and
>> received
>>
>> Any help would be greatly appreciated! Thanks...
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Camel-XMPP-1.6-2.0---OutOfMemoryError%3A-Java-heap-space-tp22485629p22562234.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source Integration
> http://fusesource.com/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Camel-XMPP-1.6-2.0---OutOfMemoryError%3A-Java-heap-space-tp22485629p22601217.html
Sent from the Camel Development mailing list archive at Nabble.com.

Reply via email to