I have tried to emulate this problem in 3.0.6 newest release from the sourceforge site there and it is doing the same thing. I have tried to release my queue resources in the ejbRemove method.
What is the lifecycle of the messageBean and when do they actually get removed? I thought someone would know a bit more about this and would have helped, I wouldn't have thought this was something no-one has ever encountered before, surely not? I can see the sessioncontext then the ejbCreate being called via a log4j event but I never see them getting dropped. Is there a way to force them to drop or make their lifecycle shorter? Michael Bennett ------------------------------------------------------- This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user