JMS Queue Persistence in GlassFish Server

Thanks To my Collegue Bentley Paul for investigating and providing this useful information.

I am just copy/pasting his analysis as it might be useful for other developers.

(A really useful page http://docs.oracle.com/cd/E19879-01/820-4332/6nfq988or/index.html)

Looking arround the documentation and forums there is some evidence of a persistence file in a fs370 folder. The UNIX find command tells us that this file is located in /app/caps/jcaps62/appserver/domains/domain1/imq/instances/imqbroker/fs370/message/QExampleQueue/vrfile

Some facts about this file: When you send a message to the Q it does not change its size but you can find the message in there. If you disable the Q and send a message, the message is consumed when the MDB is enabled again (as you would expect)

If the MDB is disabled, some messsages are sent, restart the domain, then enable the MDB the messages arrive when the MDB is enabled implying that the Q is truely persistent.

If you delete the Q and try the same the queue is recreated and behaves in the same persistent way. It appears that this is the default behaviour. The Q is automatically created when the first message is sent. That is good. It does not seem to be possible to change this behaviour.

Some useful commands:

Stop domain1 ./stop_appserver_domain1

Start domain1 ./start_appserver_domain1

Purge Q imqcmd purge dst -n ExampleQueue -t q

Delete Q asadmin delete-jmsdest --desttype queue ExampleQueue

Query Q imqcmd query dst -t q -n ExampleQueue -u admin -b localhost:7676 (portnumbers may be in logs/jvm.log, 7676 is the dfault)

Note also that the Glashfish admin console offers the following settings

(Resources -> JMS Resources -> Connection Factories -> ExampleQueue -> Transaction Support)

Not sure what this means. It is not set to any value (is blank). Here is a link to what Oracle documents http://docs.oracle.com/cd/E19316-01/820-4335/gicpj/index.html