How to check data persistence in JBoss-7.1.1-Final ?

[kparasam]

Hi, I've a JBoss-7.1.1-Final domain cluster setup running. I've configured a datasource(MySql) using some online help and I see them as bound in the logs. If I understand right, the persistence is meant to insert messages from jms queue to the database(which has been configured as datasource, say MySql). Or let's say I want this behavior. How exactly can I accomplish this ? Is there a way and what would be the possible steps. Any help would be appreciated. Thanks !

[jbertram]

JBoss AS 7 uses HornetQ as the JMS implementation.  HornetQ does not persist data to a database.  It uses a local journal.  There is no option to use a database.

[kparasam]

Ok. Thank you for the reply. So, a local journal would be a file system ? I see 'data' folders under servers, would it be saved there ? I'm asking because, if the server goes down and the messages are not yet consumed by receiver (in my case an MDB). Upon restart would the server keep the messages in queue to make it available for the receiver ? Apologies if this sounds very basic, I'm fairly new to JBoss.

[jbertram]

The journal is a set of files on the file-system.  By default they are stored in the server's "data" directory.  Any persistent messages will be persisted to disk and therefore will survive a server restart, crash, etc. so they can be consumed when the server comes back online.

[kparasam]

Cool. Thanks Justin. Are you aware of any known issues with this implementation ? Any kind of failures that would cause the messages to be lost. Just being cautious. Thank you.

[jbertram]

I'm not aware of any problems.

[kparasam]

Ok. How long would the data be stored in the file system ? Any way that we can configure ?

[jbertram]

I'm not sure I understand your question.  The data will be stored on the file-system until you remove it (e.g. consume the message(s) with a client or delete the message(s) administratively).  You can leverage the JMS API to set a time-to-live for the messages if necessary.  See http://docs.oracle.com/javaee/6/api/javax/jms/MessageProducer.html#setTimeToLive(long) for more information on that.

[kparasam]

Ok. Thank you. As long it is stored until the message is consumed by a client, it should be fine. Thanks again.