Alex, After running my new test overnight yesterday, the application did not go out of memory.
In my new test I removed the MDB from my previous test and replaced it with a thread whose run() method is same as onMessage() of MDB. The thread is passed the Message in the constructor. To commit transactions I used the UserTransaction (via a lookup) instead of the MDB Context. Apart from these, there were no other changes. I was not able to rule of leak, as the memory did go to the max, but I never got the "OutOfMemory" error. I will use a profiling tool to rule out leak. Based on these observations could this be a MDB + CMP issue? In my previous test, whenever I updated a CMP bean in a MDB, there was no leak and memory would never reach max. My application leaked (memory was at the max and got OutOfMemory error) only when I did an delete and insert of CMPs in a MDB. Kindly advise how I can resolve this issue. Thanks again, VM View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863954#3863954 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863954 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
