You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/03/20 06:52:43 UTC

[jira] Assigned: (CAMEL-1467) OutOfMemory Exception in XMPP Component

     [ https://issues.apache.org/activemq/browse/CAMEL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-1467:
----------------------------------

    Assignee: Claus Ibsen

> OutOfMemory Exception in XMPP Component
> ---------------------------------------
>
>                 Key: CAMEL-1467
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1467
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-xmpp
>         Environment: Mac OS 10.4.11, Java 1.5, Smack 3.0.4/3.1.0
>            Reporter: Orton Huang
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>   Original Estimate: 5 minutes
>  Remaining Estimate: 5 minutes
>
> on publishing messages lots of messages using XMPP component (layered on top of Smack 3.0.4/3.1.0 client), Out of Memory Exception occurs. 
> With standard JVM settings, client runs out of memory at around 6600 messages sent. With -Xmx1024M set, client runs out at ~110K messages sent.
> Appears that on a
> chat.sendMessage(message);
> The server sends the message back and the messages needs to be processed on the client side or the client will continue filling its local queue until it runs out of memory
> FIX:
> For XmppPrivateChatProducer and XmppGroupChatProducer, need to insert chat.nextMessage() after chat.sendMessage()
>  public void process(Exchange exchange) {
>    ...
>         try {
>             chat.sendMessage(message);
>             chat.nextMessage();
>         } catch (XMPPException e) {
>             throw new RuntimeXmppException(e);
>         }
>     }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.