This content has been marked as final. Show 1 reply
Yes, GlassFish 2.1.1 assumed the use of HADB when using an enhanced (HA) cluster in LOCAL mode. That's because HADB was actually bundled with it.
The workaround is to use REMOTE mode, which allows you to configure your MQ cluster in any way you want. However it does require you to start and stop the brokers yourself rather than leave this to GlassFish.
This restriction will be resolved in GlassFish 3.1, which will allow you to configure a LOCAL broker to use any suitable JDBC database.