Hi,
I've been testing the XMPP Camel component and ran into an OutOfMemoryError
after I send about 6600 packets. I have a simple client that just sends
messages one after another and the messages are roughly 4KB in size.
My client code is pretty simple:
-
public void sendMessages(i
Whats the URI you're using, do you have any camel routes and how much
ram has your JVM?
2009/3/12 orton :
>
> Hi,
>
> I've been testing the XMPP Camel component and ran into an OutOfMemoryError
> after I send about 6600 packets. I have a simple client that just sends
> messages one after another a
Whats the URI you're using, do you have any camel routes and how much
ram has your JVM?
Hi James,
uri: xmpp://or...@172.18.1.191/?room=t...@conference.nc01&password=orton
I don't have any camel routes set up (just doing a straight up send to the
Openfire Server)
I'm running the java class fro
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 10
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 :
>
> Ran some more tests with more memory for the publisher and subscriber, and it
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 cli
Heard from a co-worker:
When you send a message to the XMPP server (in this case, OpenFire) it sends
a copy back to you and that message has to be dispatched or the queue on the
client side will grow and eventually blow up. So it seems that its necessary
to call muc.nextMessage().
I did a quick
On Thu, Mar 19, 2009 at 4:20 PM, orton wrote:
>
> Heard from a co-worker:
>
> When you send a message to the XMPP server (in this case, OpenFire) it sends
> a copy back to you and that message has to be dispatched or the queue on the
> client side will grow and eventually blow up. So it seems that
Hi Claus/XMPP Component Developers,
Soo... the XMPP consumer runs out of memory also, unfortunately. Was doing a
stand alone consumer test and just found this out. I'm not sure what the
best way to handle it is, but I did try this and it works:
In the xmpp component, XmppConsumer.java, you have
Hi Orton
Thanks for reporting again.
I have fixed it on trunk and 1.x
On Thu, Mar 26, 2009 at 7:14 PM, orton wrote:
>
> Hi Claus/XMPP Component Developers,
>
> Soo... the XMPP consumer runs out of memory also, unfortunately. Was doing a
> stand alone consumer test and just found this out. I'm
10 matches
Mail list logo
