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/
