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 2010/07/08 07:15:52 UTC

[jira] Commented: (CAMEL-2922) XMPPConsumer does not remove the message which causes OOME with XMPP

    [ https://issues.apache.org/activemq/browse/CAMEL-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60495#action_60495 ] 

Claus Ibsen commented on CAMEL-2922:
------------------------------------

See CAMEL-1476

{quote}
The patch for this bug was removed in revision 779121. The result is that the XMPPConsumer does not remove the message from the MultiUserChat and the possibility for an OutOfMemoryException still exists.
The OOM occurs because the org.jivesoftware.smackx.muc.RoomListenerMultiplexor is a packet listener that contains a collector that stores all of the messages received up to a hard coded limit of 65k messages. These messages are not removed unless muc.pollMessage() or muc.nextMessage() is called. I'm not sure the reason behind storing these messages in a collector.

I have tested this in 2.1.0 and 2.3.0 and reviewed the code in 2.4-SNAPSHOT. I can supply a test case if needed.
{quote}

> XMPPConsumer does not remove the message which causes OOME with XMPP
> --------------------------------------------------------------------
>
>                 Key: CAMEL-2922
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2922
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-xmpp
>    Affects Versions: 2.1.0, 2.2.0, 2.3.0
>            Reporter: Claus Ibsen
>             Fix For: 2.5.0
>
>


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