While investigating
http://java.net/jira/browse/GLASSFISH-17041
I notice that
serverConfigLookup.getWebContainerAvailabilityEnabledFromConfig() = true
out of the box. In other words, we are using HA by default. I don't
think this is the desirable behavior.
While investigating, I find the following:
1. In domain.xml, we have
<availability-service>
<web-container-availability></web-container-availability>
<ejb-container-availability
sfsb-store-pool-name="jdbc/hastore"></ejb-container-availability>
<jms-availability></jms-availability>
</availability-service>
2. In admin/config-api:
For AvailabilityService, WebContainerAvailability,
EjbContainerAvailability, getAvailabilityEnabled()
has a "true" as default.
Note that JmsAvailability.getAvailabilityEnabled() has a "false" as
default.
There are several possibilities to resolve this issue:
a) remove the <availability-service> in the domain.xml
I do not know whether there is any side effect in admin / admin
console side
b) add availability-enabled="false" to availability-service,
web-container-availability, ejb-container-availability
At least, we have to add it to web-container-availability and
ejb-container-availability.
c) change the default value of getAvailabilityServiceEnabled() in
AvailabilityService, WebContainerAvailability, EjbContainerAvailability
of config-api.
Any comment?