The symptoms you report are exactly the problem that was fixed in 3.2.3 1) Start a client VM - and connect using a ClientID 2) Send messages to a temporary queue/topic but don't receive them 3) Don't close the connection properly, leaving the server to try to tidy up for you (it does not - it doesn't delete the messages in the temporary queue) 4) Repeat from (1)
The other part to reproduce the problem is that the message cache must have softened the undeleted temporary messages into the db. i.e. at some point JBossMQ thought you were running low on memory. If this is not your problem (try it on 3.2.3), then please include an analysis similar to what I have done above. The persistence manager cannot recover from the problem. Everytime you start a client (new VM) with the same client id, it will try to use the same key for the temporary destinations, but there are still records lying around from the previous client to confuse it. TOPIC.GPRS.KermitMessageClient.-2147483616 Means: [DestinationType.ClientID.SubscriptionName.ClientVMsConnectionNumber] View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831924#3831924 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831924 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
