[ https://issues.apache.org/activemq/browse/AMQ-914?page=all ]
Rob Davies resolved AMQ-914.
----------------------------
Fix Version/s: 4.2.0
Resolution: Fixed
Use optional Store cursor to page messages into the broker from the persistent
store
SVN revision 478967.
> OutOfMemoryError
> ----------------
>
> Key: AMQ-914
> URL: https://issues.apache.org/activemq/browse/AMQ-914
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Daniel Aioanei
> Assigned To: Rob Davies
> Fix For: 4.2.0
>
> Attachments: activemq.xml, jmxconsole.png
>
>
> I was doing some testing with a single MDP listening to a queue which had
> about 247300 messages, with a postgres backend. ActiveMQ server was started
> using the default activemq startup script (on Linux). In this configuration
> the cpu normally stays mostly idle and I described this behaviour in another
> bug report.
> Another issue came to surface when I tried to profile the client application
> with EclipseColorer to see why a single MDP can't hog my machine. But when I
> tried so, 4 OutOfMemoryError messages were logged by ActiveMQ server. Note
> that I was *not* profiling the server, but the client which is a totally
> different process.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
