[jboss-user] [JBoss Messaging] - Re: automatically truncate message table on server startup

[paul_da_programmer]

I'm only interested in the ATOMIC ('A' in ACID) aspect of a transaction. What I want to guarantee in using a JMS in a NONPERSISTENT mode is that if the JMS transaction ends abruptly, that all DB work will be back out ATOMICALLY (i.e. all or none)

That's why I asked if there is a configurable way for JBoss MQ to be configured to do both
1. use persistence, say an XA DB configuration
2. but not persist the messages across restarts - i.e. truncate the JMS message table at startup.

I know it's a bit of an oddball request, and I know I could just write some "ResetQueue" service that invokes removeAllMessages( ) for the JMS destination and have my MDBs depend on that service... I just was wondering if this was something that existed. It seems that you may want persistent messages for the lifecycle of the execution of your application, while not wanting them to persist ACROSS restarts...

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047992#4047992

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047992