Paul Ferraro wrote:
> TBH, I'm not a 100% sure what the code above does... is it adding a
> lifecycle listener dynamically if mod_cluster is started after JBossWeb
> ? Actually, I guess this will always be the case as you have a
> dependency from mod-cluster to JBossWeb.
In summary, if the jbossweb server exists that means the WebServer
service was already started. If this is the case, then dynamically add
the mod_cluster lifecycle listener, and trigger the init and start
events manually (since those events were missed).
OK, got it
> So when this is done, what will the configuration steps be (on
> JBoss AS side) ?
> 1. Add a jvmRoute to server.xml [optional, as jvmRoute is generated
> if absent]
The default JvmRouteFactory allows system property override as well,
I assume you're referring to the *factory*, so would the property be
something like -Djboss.mod_cluster.jvmRoute.factory=CLASSNAME ?
> 2. mod-cluster.sar:
> 1. Set the proxy list (jboss.mod_cluster.proxyList) [optional
> if IP multicasting works, as advertise is enabled by default]
Advertise is not enabled by default - in order to minimize jboss's
default port footprint. Advertise can be enabled via a system property.
So, in summary, the servers just need to be started with either:
OK. In order to create virtual images for GoGrid, EC2 and Rackspace, I
want to avoid using system properties as much as possible. So jvmRoutes
need to be either hard coded, or my startup script (/etc/init.d/jboss)
will have to provide unique values for them, e.g. via uuidgen.
> 2. Set the domain [optional if we use a system prop, or the
> default domain]
> 3. Use HAModClusterService instead of ModClusterService: for
> the mod-cluster.sar located in 'all', can we make this the
> default ?
I alluded to this earlier when I mentioned splitting the
ModClusterListener bean into a separate conf file and creating 2
versions of it. One using HAModClusterService for use in the all
profile, the other using ModClusterService for use in the default
Lead JGroups / Clustering Team