I’m looking for some best practices around MDB clustering and any support Glassfish add to that.
We have an MDB that must process messages in order.
Basically we’re looking for an active / failover situation where if MDB Foo fails for some reason on host A, the copy of MDB Foo on host B is automagically started. We have some OS level hooks available in the case of catastrophic failures (i.e. Disk blows up) but wondering if there is anything built in to the spec or Glassfish specifically that we’re missing.
Any pointers appreciated :-)
--
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454 Cell: 860.329.5842