1 2 Previous Next 15 Replies Latest reply on Sep 28, 2003 10:02 PM by Manuel Elaraj

    clustering partitions on JBoss3.0.4

    susan.deaves Newbie

      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..

        1 2 Previous Next