clustering partitions on JBoss3.0.4

[susan.deaves]

I am trying to set up partitions inorder to isolate installations for development teams.
I can succesfully create a new partition but I receive errors as JBoss seems to be trying to create and configure the deafult partition.
I am using the following text in the cluster-service.xml:-
<?xml version="1.0" encoding="UTF-8"?>

<!-- ===================================================================== -->
<!-- -->
<!-- Sample Clustering Service Configuration -->
<!-- -->
<!-- ===================================================================== -->






<!-- ==================================================================== -->
<!-- Cluster Partition: defines cluster -->
<!-- ==================================================================== -->






SuePartition


<!-- ==================================================================== -->
<!-- HA Session State Service for SFSB -->
<!-- ==================================================================== -->





jboss:service=SuePartition
/HAPartition/SueService
SuePartition


<!-- ==================================================================== -->
<!-- HA JNDI -->
<!-- ==================================================================== -->





jboss:service=SuePartition
SuePartition"
11001








I get the followling errors:-
12:12:49,285 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.4_tomcat-
4.1.12/server/default/deploy/http-invoker.sar/invoker.war/
12:12:49,285 INFO [EmbeddedCatalinaService41] Started
12:12:49,295 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.4_tomcat-
4.1.12/server/default/deploy/tomcat41-service.xml
12:12:49,295 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.0.4_tomcat-4.1.12/server/default/deploy/user-service.xml
12:12:49,345 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.4_tomcat-
4.1.12/server/default/deploy/user-service.xml
12:12:49,345 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.0.4_tomcat-4.1.12/server/default/deploy/ingres-service.xml
12:12:49,406 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=DefaultD
S does not implement any Service methods
12:12:49,406 INFO [JBossManagedConnectionPool] Creating
12:12:49,406 INFO [JBossManagedConnectionPool] Created
12:12:49,406 INFO [JBossManagedConnectionPool] Starting
12:12:49,416 INFO [JBossManagedConnectionPool] Started
12:12:49,416 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.4_tomcat-
4.1.12/server/default/deploy/ingres-service.xml
12:12:49,416 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.0.4_tomcat-4.1.12/server/default/deploy/cluster-service.xml
12:12:49,436 INFO [MainDeployer] Package: file:/C:/jboss-3.0.4_tomcat-4.1.12/se
rver/default/lib/jbossha.jar is already deployed
12:12:49,886 INFO [ClusterPartition] Creating
12:12:50,307 INFO [ClusterPartition] Set the JavaGroups logging to log4j with c
ategory:org.apache.log4j.Logger@1d7b222, priority: DEBUG, JavaGroupsLevel: 1
12:12:50,407 INFO [SuePartition] Initializing
12:12:50,477 INFO [ClusterPartition] Created
12:12:50,477 INFO [HASessionStateService] Creating
12:12:50,497 ERROR [HASessionStateService] Initialization failed
javax.naming.NameNotFoundException: DefaultPartition not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
at org.jnp.server.NamingServer.lookup(NamingServer.java:282)
at org.jnp.server.NamingServer.lookup(NamingServer.java:256)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:464)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:443)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.ha.hasessionstate.server.HASessionStateImpl.init(HASessionS
tateImpl.java:123)
at org.jboss.ha.hasessionstate.server.HASessionStateService.createServic
e(HASessionStateService.java:92)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:
136)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy5.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:315)

at org.jboss.system.ServiceController.create(ServiceController.java:243)

at org.jboss.system.ServiceController.create(ServiceController.java:335)

at org.jboss.system.ServiceController.create(ServiceController.java:243)

at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.create(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:217)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:760)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:620)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:585)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
nDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy4.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:435)
at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDe
ploymentScanner.java:656)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:261)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1
65)

Any help appreciated.my plan was to configure each development installation for a different cluster so they would not communicate with each other but at the same time being correctly configured for clustering whci be implemented at a later date..

[jbossnz]

Seems like the original errors come from the DeploymentScanner. Any chance that your ear file in the deploy or all directory has ejbs that still use the DefaultPartition ?

Note: if you havn't specified <partition-name>SuePartition</partition-name> in the jboss.xml for your enterprise beans it will default to <partition-name>DefaultPartition</partition-name>

See page 34 and 35 of the clustering docs (April 2003 version-the latest)

[jackpot]

I am also looking forward to cluster configuration. Appreciate if you can help me with the necessary steps involved in configuring a cluster for JBoss-3.2.1

Thank You
Jackpot

[darranl]

The easiest way to isolate the different clusters is to change the mcast_addr value instead of the name of the cluster.

[susan.deaves]

This sounds like the easiest way to do this..however can you me some info I would go about this please..

[darranl]

If you look in the {jboss.folder}/server/all/deploy folder you should find a file called cluster-service.xml

In the cluster partition configuration section of this file there should be a line

<UDP mcast_addr="228.1.2.3" mcast_port="45566"

This is the multicast address shared by the nodes in the cluster, changing this address basically puts the machine into a different cluster.

[susan.deaves]

Unfortunately my supplied cluster-servive.xml does not have any configuration liune sinit. I have found 2 different examples on the web and I have tried both of these:-

attribute name="PartitionConfig">
UDPmcast_addr="1.1.1.1" mcast_port="88888"




and


UDP(mcast_addr=1.1.1.1;mcast_port=88888)


both of these hang when the channel is created..the files seems to be deployed , initialised and started OK.

Any thoughts..could this be an issues with the network ??

[jackpot]

Hello Susan,

I read your postings. I also want to setup clustering. I am following your steps as a guide.

Does your mails have the entire configuration? If you not, can you please explain the steps for a simple cluster configuration?

Thankyou,
Jack

[jackpot]

Hi Susan,

Can you forward your cluster-service.xml and farm-service.xml?

That would have been a great help.

Thankyou,
Jack

[slaboure]

First, start using a recent version, such as 3.0.8. I will not debug earlier version.

Cheers,


sacha

[susan.deaves]

Thanks for your reply..however i am working with a project where for reasons I have no influence or control over this is the version I have been mandated to use. if it were up to me I would certainly be using the later versions...

[susan.deaves]

Jack in order to run clustering I used the cluster-service.xml straight as it was and clustering works out of the box. There is no farm-service.xml with this version of jboss so can not help you here. My problems
are occurring because i want to disable clustering for this version in the development environment and have so far not succeeded.

[theeligible]

Hi Susan,
Changing the partition name in cluster-service.xml WONT change the partition name. If you wish to run the application in a non-clustered env, run it in default configuration. Make sure u make changes to your META-inf/jboss.xml entries.
What u were trying to achieve(By changing the mcast addr), can be done. But the addres which you supplied was incorrect. Mcast address are with in range
224.0.0.0 through 239.255.255.255 .
To make things easier for you, dont try to do these changes unless they are very necessary.


regards,
theeligible

[susan.deaves]

Thanks for your reply. I believe I have solved my problem now by editing the mulicatcast port to be different on each machine- with a valid multicast address, and with ttl=0.
What I was trying to achieve was setting up identical environments on each member of the development team's PC - each connecting to a local database and without the jboss server believing that they are all part of the same cluster. They are all on the same network, all on the same subnet and are working with the same sets of code, . As the code they are working is the same- partition name in jboss.xml files will all be identical.
Once developemnt is deployed in a production environment this will not be an issue as clustering appears to work out of the box!
I am not sure that I have set this up the best way but it apprears to work.

[slaboure]

yes, changing the multicast address but keeping the same partition name is the easiest (and best IMHO) way to avoid conflicts between dev and prod environments.

cheers,


sacha