[
https://issues.apache.org/jira/browse/QPID-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672641#action_12672641
]
Douglas Pew commented on QPID-1658:
-----------------------------------
FYI: This test is using the M4 C++ broker.
I set the heap size to be very large on the client -mx512m, but that only
delays the issue a bit. The heap fills up quite linearly, and memory is not
being released.
The VisualVM profiler shows that the memory is being used by byte[] (54MB) -
3,338 instances. There are also 3,362 instances of MessageTransport. This
seems to indicate that the MessageTransport.body (of class ByteBuffer) is the
culprit.
> 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:[email protected]
