2:46 p.m.
OK, I read through the archives of this list and came up with a solution
for mod-jk, but apparently nobody has so far used domains/sticky
sessions with *mod-cluster* !
I found 2 different ways of doing this:
#1 server.xml:
---------------------
<Listener className="org.jboss.modcluster.ModClusterListener"
advertize="true" domain="${jboss.Domain:DefaultDomain}"
/>
#2 and in mod-cluster-jboss-beans.xml:
---------------------------------------------------------
<bean name="HAModClusterService" ...>
<property
name="domain">${jboss.Domain:DefaultDomain}</property>
</bean>
and then started several instances:
./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
and
./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
-Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
D2 with node3).
#1 above seems to work half way, #2 doesn't.
Questions
========
* What is the recommended way of setting of domains ?
o I assume #1, but that's not documented anywhere, I just
found out accidentally through a port via google
* Sometimes, a webapp on node2 fails over to node3 rather than node1
Can someone look into this ? This information should be available via a
web page, similar to the one for mod-jk !
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
3:12 p.m.
On 07/21/2009 02:46 PM, Bela Ban wrote:
OK, I read through the archives of this list and came up with a
solution
for mod-jk, but apparently nobody has so far used domains/sticky
sessions with *mod-cluster* !
I found 2 different ways of doing this:
#1 server.xml:
---------------------
<Listener className="org.jboss.modcluster.ModClusterListener"
advertize="true" domain="${jboss.Domain:DefaultDomain}" />
#2 and in mod-cluster-jboss-beans.xml:
---------------------------------------------------------
<bean name="HAModClusterService" ...>
<property name="domain">${jboss.Domain:DefaultDomain}</property>
</bean>
and then started several instances:
./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
and
./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
-Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
D2 with node3).
#1 above seems to work half way, #2 doesn't.
Questions
========
* What is the recommended way of setting of domains ?
#2 with AS (5.x and up)/
#1 for Tomcat/JbossWEB and 4.2.x/ 4.3.x.
o I assume #1, but that's not documented anywhere, I just
found out accidentally through a port via google
* Sometimes, a webapp on node2 fails over to node3 rather than node1
Looks like a bug... Would need a way to reproduce it, are you sure it is
not MODCLUSTER-81?
Can someone look into this ? This information should be available via a
web page, similar to the one for mod-jk !
Where is the mod_jk one?
Cheers
Jean-Frederic
3:17 p.m.
jean-frederic clere wrote:
On 07/21/2009 02:46 PM, Bela Ban wrote:
> OK, I read through the archives of this list and came up with a solution
> for mod-jk, but apparently nobody has so far used domains/sticky
> sessions with *mod-cluster* !
>
> I found 2 different ways of doing this:
>
> #1 server.xml:
> ---------------------
>
> <Listener className="org.jboss.modcluster.ModClusterListener"
> advertize="true" domain="${jboss.Domain:DefaultDomain}" />
>
> #2 and in mod-cluster-jboss-beans.xml:
> ---------------------------------------------------------
>
> <bean name="HAModClusterService" ...>
> <property
name="domain">${jboss.Domain:DefaultDomain}</property>
> </bean>
>
> and then started several instances:
>
> ./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
> -Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
> ./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
> -Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
>
> and
>
> ./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
> -Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
>
>
> So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
> D2 with node3).
>
> #1 above seems to work half way, #2 doesn't.
>
> Questions
> ========
>
> * What is the recommended way of setting of domains ?
#2 with AS (5.x and up)/
#1 for Tomcat/JbossWEB and 4.2.x/ 4.3.x.
Hmm, #2 did *not* work with AS 5.1/mod-cluster, but #1 did ! So it's
just the other way round ! (?)
Looks like a bug... Would need a way to reproduce it, are you sure it
is not MODCLUSTER-81?
Yes, I didn't play around with disabling webapps/nodes.
Where is the mod_jk one?
http://lists.jboss.org/pipermail/mod_cluster-dev/2009-January/000043.html
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
3:26 p.m.
Is the mod_cluster-dev list still not working for you?
On Tue, 2009-07-21 at 14:46 +0200, Bela Ban wrote:
OK, I read through the archives of this list and came up with a
solution
for mod-jk, but apparently nobody has so far used domains/sticky
sessions with *mod-cluster* !
I found 2 different ways of doing this:
#1 server.xml:
---------------------
<Listener className="org.jboss.modcluster.ModClusterListener"
advertize="true" domain="${jboss.Domain:DefaultDomain}"
/>
#2 and in mod-cluster-jboss-beans.xml:
---------------------------------------------------------
<bean name="HAModClusterService" ...>
<property
name="domain">${jboss.Domain:DefaultDomain}</property>
</bean>
Configuration properties for the HA service are defined in a separate
config bean, as documented here:
http://www.jboss.org/mod_cluster/java/config.html#ha
This should read:
<bean name="HAModClusterService" mode="On Demand"
class="org.jboss.modcluster.ha.HAModClusterService">
<constructor>
<parameter><inject bean="HAPartition"/></parameter>
<parameter><inject
bean="HAModClusterConfig"/></parameter>
<parameter><inject
bean="DynamicLoadBalanceFactorProvider"/></parameter>
<parameter><bean
class="org.jboss.ha.singleton.HASingletonElectionPolicySimple"/></parameter>
</constructor>
</bean>
<bean name="HAModClusterConfig" mode="On Demand"
class="org.jboss.modcluster.config.ha.HAModClusterConfig">
<!-- Configuration properties go here -->
<parameter
name="domain">${jboss.Domain:DefaultDomain}</parameter>
</bean>
and then started several instances:
./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
-Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
and
./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
-Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
D2 with node3).
#1 above seems to work half way, #2 doesn't.
Questions
========
* What is the recommended way of setting of domains ?
o I assume #1, but that's not documented anywhere, I just
found out accidentally through a port via google
The location of the domain property depends on how you've configured
mod_cluster.
Config #1 uses ModClusterListener, defined in server.xml, and is primary
used with JBoss Web standalone and Tomcat, where you don't have the
benefit of MC configuration.
http://www.jboss.org/mod_cluster/java/config.html#web
Config #2, uses HAModClusterService, configured via the microcontainer,
and is used for configuration in JBoss AS, where all proxy communication
goes through an HASingleton.
http://www.jboss.org/mod_cluster/java/config.html#ha
The third option, not yet mentioned, uses ModClusterService, configured
via the microcontainer, where each AS node communicates directly with
the proxy. Using this method, the "domain" property is defined within
the ModClusterService bean, like you tried to do initially.
http://www.jboss.org/mod_cluster/java/config.html#as
* Sometimes, a webapp on node2 fails over to node3 rather than
node1
Have you verified that node1 is enabled when this happens?
If so, can you file a JIRA?
Can someone look into this ? This information should be available via
a
web page, similar to the one for mod-jk !
Is this what you're looking for?
http://www.jboss.org/mod_cluster/java/properties.html
7:50 p.m.
I changed this, now I use bban@redhat.com...
jean-frederic clere wrote:
On 07/21/2009 03:26 PM, Paul Ferraro wrote:
> Is the mod_cluster-dev list still not working for you?
It should be work. Bela just never uses the right mail account I need
to accept the posts (I have done that today: needed a password :-/ ).
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
12:42 p.m.
Thanks for the explanation !
So I switched to placing the property inside of HAModClusterConfig, and
this seems to work. However, mod_cluster_manager does *not* show the
domain ! Does it only show the domain when it is configured in
ModClusterListener in server.xml ?
Another question: what's the advantage of defining a domain in
HAModClusterConfig over ModClusterListener ? I assume ModClusterListener
works in clustered AS mode, too ?
Paul Ferraro wrote:
Is the mod_cluster-dev list still not working for you?
On Tue, 2009-07-21 at 14:46 +0200, Bela Ban wrote:
> OK, I read through the archives of this list and came up with a solution
> for mod-jk, but apparently nobody has so far used domains/sticky
> sessions with *mod-cluster* !
>
> I found 2 different ways of doing this:
>
> #1 server.xml:
> ---------------------
>
> <Listener className="org.jboss.modcluster.ModClusterListener"
> advertize="true" domain="${jboss.Domain:DefaultDomain}" />
>
> #2 and in mod-cluster-jboss-beans.xml:
> ---------------------------------------------------------
>
> <bean name="HAModClusterService" ...>
> <property
name="domain">${jboss.Domain:DefaultDomain}</property>
> </bean>
Configuration properties for the HA service are defined in a separate
config bean, as documented here:
http://www.jboss.org/mod_cluster/java/config.html#ha
This should read:
<bean name="HAModClusterService" mode="On Demand"
class="org.jboss.modcluster.ha.HAModClusterService">
<constructor>
<parameter><inject bean="HAPartition"/></parameter>
<parameter><inject bean="HAModClusterConfig"/></parameter>
<parameter><inject
bean="DynamicLoadBalanceFactorProvider"/></parameter>
<parameter><bean
class="org.jboss.ha.singleton.HASingletonElectionPolicySimple"/></parameter>
</constructor>
</bean>
<bean name="HAModClusterConfig" mode="On Demand"
class="org.jboss.modcluster.config.ha.HAModClusterConfig">
<!-- Configuration properties go here -->
<parameter name="domain">${jboss.Domain:DefaultDomain}</parameter>
</bean>
> and then started several instances:
>
> ./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
> -Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
> ./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
> -Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
>
> and
>
> ./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
> -Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
>
>
> So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
> D2 with node3).
>
> #1 above seems to work half way, #2 doesn't.
>
> Questions
> ========
>
> * What is the recommended way of setting of domains ?
> o I assume #1, but that's not documented anywhere, I just
> found out accidentally through a port via google
The location of the domain property depends on how you've configured
mod_cluster.
Config #1 uses ModClusterListener, defined in server.xml, and is primary
used with JBoss Web standalone and Tomcat, where you don't have the
benefit of MC configuration.
http://www.jboss.org/mod_cluster/java/config.html#web
Config #2, uses HAModClusterService, configured via the microcontainer,
and is used for configuration in JBoss AS, where all proxy communication
goes through an HASingleton.
http://www.jboss.org/mod_cluster/java/config.html#ha
The third option, not yet mentioned, uses ModClusterService, configured
via the microcontainer, where each AS node communicates directly with
the proxy. Using this method, the "domain" property is defined within
the ModClusterService bean, like you tried to do initially.
http://www.jboss.org/mod_cluster/java/config.html#as
> * Sometimes, a webapp on node2 fails over to node3 rather than node1
Have you verified that node1 is enabled when this happens?
If so, can you file a JIRA?
> Can someone look into this ? This information should be available via a
> web page, similar to the one for mod-jk !
Is this what you're looking for?
http://www.jboss.org/mod_cluster/java/properties.html
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
3:44 p.m.
On Wed, 2009-07-22 at 12:42 +0200, Bela Ban wrote:
Thanks for the explanation !
So I switched to placing the property inside of HAModClusterConfig, and
this seems to work. However, mod_cluster_manager does *not* show the
domain ! Does it only show the domain when it is configured in
ModClusterListener in server.xml ?
I think I see where the confusion is...
The entry point for the configuration of mod_cluster is the lifecycle
listener in server.xml. There are two types of listeners you can use:
1. ModClusterListener - configures mod_cluster directly inside
server.xml via java bean properties. If you use ModClusterListener in
server.xml, everything in mod-cluster-jboss-beans.xml is ignored. This
also limits your load balancing options to a single metric.
2. MicrocontainerIntegrationLifecycleListener - delegates the
configuration of mod_cluster to a microcontainer bean. There are 2
values you can use for this bean (if you are to using the stock
-jboss-beans.xml config):
a. ModClusterService - configuration properties are java bean
properties of this object
b. HAModClusterService - configuration properties reside in
HAModClusterConfig delegate. The differing location is due to an
implementation detail to which, because of the dual responsibilities
(configuration and IOC) of the microcontainer, the user is unfortunately
exposed.
Another question: what's the advantage of defining a domain in
HAModClusterConfig over ModClusterListener ? I assume ModClusterListener
works in clustered AS mode, too ?
I think the above explanation already answers this question.
Paul Ferraro wrote:
> Is the mod_cluster-dev list still not working for you?
>
> On Tue, 2009-07-21 at 14:46 +0200, Bela Ban wrote:
>> OK, I read through the archives of this list and came up with a solution
>> for mod-jk, but apparently nobody has so far used domains/sticky
>> sessions with *mod-cluster* !
>>
>> I found 2 different ways of doing this:
>>
>> #1 server.xml:
>> ---------------------
>>
>> <Listener className="org.jboss.modcluster.ModClusterListener"
>> advertize="true" domain="${jboss.Domain:DefaultDomain}"
/>
>>
>> #2 and in mod-cluster-jboss-beans.xml:
>> ---------------------------------------------------------
>>
>> <bean name="HAModClusterService" ...>
>> <property
name="domain">${jboss.Domain:DefaultDomain}</property>
>> </bean>
>
> Configuration properties for the HA service are defined in a separate
> config bean, as documented here:
> http://www.jboss.org/mod_cluster/java/config.html#ha
>
> This should read:
>
> <bean name="HAModClusterService" mode="On Demand"
> class="org.jboss.modcluster.ha.HAModClusterService">
> <constructor>
> <parameter><inject bean="HAPartition"/></parameter>
> <parameter><inject
bean="HAModClusterConfig"/></parameter>
> <parameter><inject
bean="DynamicLoadBalanceFactorProvider"/></parameter>
> <parameter><bean
>
class="org.jboss.ha.singleton.HASingletonElectionPolicySimple"/></parameter>
> </constructor>
> </bean>
> <bean name="HAModClusterConfig" mode="On Demand"
> class="org.jboss.modcluster.config.ha.HAModClusterConfig">
> <!-- Configuration properties go here -->
> <parameter
name="domain">${jboss.Domain:DefaultDomain}</parameter>
> </bean>
>
>> and then started several instances:
>>
>> ./run.sh -b 192.168.1.5 -c all -g *D1* -u 230.1.1.1 -m 10500
>> -Djboss.jvmRoute=*node1* -Djboss.Domain=*D1*
>> ./run.sh -b 192.168.1.9 -c all -g *D1* -u 230.1.1.1 -m 10500
>> -Djboss.jvmRoute=*node2* -Djboss.Domain=*D1*
>>
>> and
>>
>> ./run.sh -b 192.168.1.10 -c all -g *D2* -u 230.2.2.2 -m 11500
>> -Djboss.jvmRoute=*node3* -Djboss.Domain=*D2*
>>
>>
>> So we have domains D1 (cluster D1 with node1 and node2) and D2 (cluster
>> D2 with node3).
>>
>> #1 above seems to work half way, #2 doesn't.
>>
>> Questions
>> ========
>>
>> * What is the recommended way of setting of domains ?
>> o I assume #1, but that's not documented anywhere, I just
>> found out accidentally through a port via google
>
> The location of the domain property depends on how you've configured
> mod_cluster.
>
> Config #1 uses ModClusterListener, defined in server.xml, and is primary
> used with JBoss Web standalone and Tomcat, where you don't have the
> benefit of MC configuration.
> http://www.jboss.org/mod_cluster/java/config.html#web
>
> Config #2, uses HAModClusterService, configured via the microcontainer,
> and is used for configuration in JBoss AS, where all proxy communication
> goes through an HASingleton.
> http://www.jboss.org/mod_cluster/java/config.html#ha
>
> The third option, not yet mentioned, uses ModClusterService, configured
> via the microcontainer, where each AS node communicates directly with
> the proxy. Using this method, the "domain" property is defined within
> the ModClusterService bean, like you tried to do initially.
> http://www.jboss.org/mod_cluster/java/config.html#as
>
>> * Sometimes, a webapp on node2 fails over to node3 rather than node1
>
> Have you verified that node1 is enabled when this happens?
> If so, can you file a JIRA?
>
>> Can someone look into this ? This information should be available via a
>> web page, similar to the one for mod-jk !
>
> Is this what you're looking for?
> http://www.jboss.org/mod_cluster/java/properties.html
>
4:59 p.m.
Paul Ferraro wrote:
On Wed, 2009-07-22 at 12:42 +0200, Bela Ban wrote:
> Thanks for the explanation !
>
> So I switched to placing the property inside of HAModClusterConfig, and
> this seems to work. However, mod_cluster_manager does *not* show the
> domain ! Does it only show the domain when it is configured in
> ModClusterListener in server.xml ?
I think I see where the confusion is...
The entry point for the configuration of mod_cluster is the lifecycle
listener in server.xml. There are two types of listeners you can use:
1. ModClusterListener - configures mod_cluster directly inside
server.xml via java bean properties. If you use ModClusterListener in
server.xml, everything in mod-cluster-jboss-beans.xml is ignored. This
also limits your load balancing options to a single metric.
Oops, the documentation led me to believe that I need to configure
*both* ! In http://jboss.org/mod_cluster/java/config.html, the
configuration of ModClusterListener is under "Common Configuration", so
I thought this needs to be added no matter what...
Voila, I removed ModClusterListener from server.xml, and I can now see
the domains in mod-cluster-manager, great !
thanks for you help !
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
2:29 p.m.
On 07/21/2009 02:46 PM, Bela Ban wrote:
* Sometimes, a webapp on node2 fails over to node3 rather than
node1
Can someone look into this ?
I have found when it happens... Once you remove a node (clean shutdown)
mod_cluster will remove the information about the node so it have no way
to find the domain, that is some work to fix it (need another shared
area with removed nodes, just JVMRoute | domain).
There is a JIRA for it: MODCLUSTER-82
Cheers
Jean-Frederic
2:37 p.m.
OK, great ! Will this be in mod-cluster before JBW ?
jean-frederic clere wrote:
On 07/21/2009 02:46 PM, Bela Ban wrote:
> * Sometimes, a webapp on node2 fails over to node3 rather than node1
>
> Can someone look into this ?
I have found when it happens... Once you remove a node (clean
shutdown) mod_cluster will remove the information about the node so it
have no way to find the domain, that is some work to fix it (need
another shared area with removed nodes, just JVMRoute | domain).
There is a JIRA for it: MODCLUSTER-82
Cheers
Jean-Frederic
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
5391
days inactive
5392
days old
mod_cluster-dev@lists.jboss.org
10 comments
3 participants
participants (3)
-
Bela Ban -
jean-frederic clere -
Paul Ferraro