[ https://issues.apache.org/jira/browse/QPID-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672395#action_12672395 ]
Rajith Attapattu commented on QPID-1658: ---------------------------------------- Douglas, Are you using the c++ broker or the java broker? Depending on which broker the JMS clients takes a different code path. For the java broker the 0-8/0-9 code path is activated and uses MINA as the transport. For the c++ broker the 0-10 code path is activated and uses a plain java.io based transport. If it's the java broker you could then try to set -Dprotectio=true when starting the JMS client to ensure that the underlying MINA buffers don't grow unbounded. > JMS client OutOfMemoryError when sending 4k messages in rapid succession > ------------------------------------------------------------------------ > > Key: QPID-1658 > URL: https://issues.apache.org/jira/browse/QPID-1658 > Project: Qpid > Issue Type: Bug > Components: Java Client > Affects Versions: M4 > Environment: Ubuntu 8.04 Hardy > Reporter: Douglas Pew > Attachments: Consumer.java, Producer.java > > > The JMS bindings will throw an OutOfMemoryError when sending 4k or larger > messages in rapid succession. The message producer's heap will continue to > fill up until exhausted. > To repeat this error edit the class > org.apache.qpid.example.jmsexample.direct.Producer to produce 100000 messages > and 4k message sizes. I will submit source code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org