Bugs item #478527, was opened at 2001-11-05 21:05 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=478527&group_id=22866
Category: JBossMQ Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Brian Weaver (weave) Assigned to: Nobody/Anonymous (nobody) Summary: MQ Messages not released Initial Comment: JBossMQ does not appear to be releasing all references to messages that are being delivered. I'm using the source from the HEAD of the CVS repository and I'm using OptimizeIt to trace the memory usage for JBossMQ during runtime. The application in question has several services and is composed of one queue and two topics. There is one application that starts several threads to read messages placed onto the queue. When messages are read from the queue they are processes/modified and then re-broadcast using one of the topics. The second topic is used strictly for control messages. Using OptimizeIt to profile the JBossMQ code I can watch the memory profile as messages are being exchanged. As more messages are sent the average total memory used tends to grow. Looking at the total number of actual instances objects in the system I've seen that the number of SpyTextMessage objects grows and never shrinks over the program lifetime. Additionally, if all connected clients disconnect the number of messages remains constant. This ultimatly has the effect of causing the server to run out of memory and this may be the exact problem as bug #474206. I tuned the configuration files to force events to be written to disk in the "tmp" directory by setting the HighMemoryMark to 16M an the Maximum memory to 64. As the product ran the number of messages in the "tmp" directory continue to increase. Additionally, ALL the messages that were passed in the server were in the "tmp" directory. One Final Note: The Queue session is persistant, but the Topic sessions are not. ---------------------------------------------------------------------- >Comment By: Hiram Chirino (chirino) Date: 2002-05-02 21:33 Message: Logged In: YES user_id=175851 This has been fix now in 3.0 RC 2... Selectors were causing leaks (messages that did not match hung arround forever). ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=478527&group_id=22866 _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
