[
https://issues.apache.org/activemq/browse/CAMEL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50804#action_50804
]
Orton Huang commented on CAMEL-1467:
------------------------------------
Hi Claus,
Just downloaded the Camel 1.6.1 version... Do you think you can make the same
XMPP fixes in 1.6.1 that you made in 2.0?
FIX:
For XmppPrivateChatProducer and XmppGroupChatProducer, need to insert
chat.nextMessage() after chat.sendMessage()
public void process(Exchange exchange) {
...
try {
chat.sendMessage(message);
chat.nextMessage(); // <----- this line needed!
} catch (XMPPException e) {
throw new RuntimeXmppException(e);
}
}
Thanks!!
Orton
On 3/20/09 12:52 PM, "Claus Ibsen (JIRA)" <[email protected]> wrote:
[
https://issues.apache.org/activemq/browse/CAMEL-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=50715#action_50715
]
Claus Ibsen commented on CAMEL-1467:
------------------------------------
Orton
There are *no* nextMessage() on the chat object in XmppPrivateChatProducer.
Only the other one got the method.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
> 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, 1.6.1
>
> 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.
