In addition to what Siva just said:
JMS persistent messages can be configured to be in any database (e.g:
Oracle or the built-in HADB if you are using Sun Java System App
Server Enterprise Edition). I believe the JMS provider in GlassFish
also supports file system as message store, but you have to make sure
that the filesystem is highly available.
Timers metadata can be kept in any XA-capable data source. So any
reliable database would work. Follow the replication/reliability
guidelines of the vendor.
Sreeram
On Dec 22, 2007, at 6:34 AM, Markus KARG wrote:
> Our Java EE application is using Persistent Timers (see EJB spec)
> and relies very heavily on JMS.
> We want to prevent that long-term timers and non-yet-received
> messages in JMS topics and queues are lost in case of a server crash.
> What is the "official" way how to backup and restore that data in
> Glassfish?
> Is there a tutorial or reference manual on the web for that topic?
>
> We formerly used JOnAS, which stored both, timers and jms topics
> and queues as simple files, so backup and restore was quite simple.
> We did not yet find information on the storage mechanism that
> Glassfish uses.
>
> Thanks a lot
> Markus
>
> --
> http://www.xing.com/go/invita/58469
>