[ https://issues.apache.org/activemq/browse/AMQ-914?page=comments#action_36915 ] Daniel Aioanei commented on AMQ-914: ------------------------------------
Just got the same problem in the same configuration without running anything under a profiler. INFO Service - Sync error occurred: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space INFO Service - Sync error occurred: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space INFO Service - Sync error occurred: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space INFO Service - Sync error occurred: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space INFO Service - Sync error occurred: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space I guess I could specify some larger -xmx value, but because the back end is postgres I don't think the number of messages in the queue should have anything to do with the amount of memory the ActiveMQ server needs. > 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 > Attachments: activemq.xml > > > 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
