[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1685) jboss messaging / memory leak on session.rollback() operation

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1685?page=com.atlassian.ji... ] Martin Gysel updated JBMESSAGING-1685: -------------------------------------- hi howard, thanks for your feedback. i changed the queue defs as follows: <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=testQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> <depends>jboss.messaging:service=PostOffice</depends> <attribute name="MaxDeliveryAttempts">10</attribute> <attribute name="FullSize">200</attribute> <attribute name="PageSize">100</attribute> <attribute name="DownCacheSize">100</attribute> <attribute name="SecurityConfig"> <security> <role name="guest" read="true" write="true"/> <role name="publisher" read="true" write="true" create="false"/> <role name="noacc" read="false" write="false" create="false"/> </security> </attribute> </mbean> the test case with 100K messages should now occupy a max of about 20MB (200 x 100K). before running the test again i changed the test program to adapt as realistic as possible to our current application logic. so the loop now takes place in the main() method and in the receiving of the messages (MaxDeliveryAttempts set to 10). there is no commit() operation anymore ( see the attached file QueueExampleLong3). many more 'rounds' can be run with this logic and the above configuration. after about 4060 rounds the OOM in the java heap space occurs again. when running with 500K messages the OOM occurs after 817 rounds (factor 5 matches for sizes and number of rounds). these tests were done with a DLQ specified. i assume that a similar or alike behaviour can be expected with a DLQ as well. attached you'll also find another screen shot und server log. the screen shot of the jconsole memory view shows the continous growth of memory over time. thank you very much for your help. kind regards martin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira