10 Replies Latest reply on Feb 11, 2009 3:20 PM by Brian Stansberry

    clustering/JMS problem among machines not using same partiti

    Josephine Schwabel Newbie

      Hello, all. We are using jboss-4.2.3.GA on some machines with CentOS 4.4 and some with CentOS 5. For development purposes we do not like to cluster so we all change our mcast_port in cluster-service.xml to something unique. That was fine for a time. Then we realized that even though JBoss was not clustering, JMS was. I read http://jboss.org/community/docs/DOC-12460 and consequently started using unique partition names and jboss.partition.udpGroup addresses. This LOOKS like it is working, but does not.

      Here is the start of my JBoss log on a machine called "cars" at 150.102.65.10:

      ================================================================================
      JBoss Bootstrap Environment
      
      JBOSS_HOME: /usr/jboss-4.2.3.GA
      
      JAVA:
      
      JAVA_OPTS: -server -Xmx512m -XX:PermSize=96m -XX:MaxPermSize=128m -Dprogram.name=jboss
      
      CLASSPATH: /usr/jboss-4.2.3.GA/bin/run.jar:/usr/java/jdk1.5.0_02/lib/tools.jar
      
      CMD_START: /usr/java/jdk1.5.0_02/bin/java -server -Xmx512m -XX:PermSize=96m -XX:MaxPermSize=128m -Dprogram.name=jboss -classpath /usr/jboss-4.2.3.GA/bin/run.jar:/usr/java/jdk1.5.0_02/lib/tools.jar org.jboss.Main -c appServer -b cars -Djava.security.manager=java.lang.SecurityManager -Djava.security.policy=/usr/jboss-4.2.3.GA/server/appServer/conf/server.policy -Djava.rmi.server.codebase="file:/usr/jboss-4.2.3.GA/server/appServer/lib/KDCSservices.jar file:/usr/jboss-4.2.3.GA/server/appServer/lib/kdcsclient.jar" -Djava.rmi.server.hostname=cars -Dkdcs.hostname=cars -Djboss.partition.name=workstation_32_development_Rochester
       -Djboss.partition.udpGroup=228.1.2.10 -Djboss.platform.mbeanserver -Djava.endorsed.dirs=/usr/jboss-4.2.3.GA/lib/endorsed
      ================================================================================
      
      10:11:13,954 INFO [JChannel] JGroups version: 2.4.1 SP-4
      10:11:14,661 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 150.102.65.10:52299
      -------------------------------------------------------
      10:11:16,684 INFO [TreeCache] viewAccepted(): [150.102.65.10:52299|0] [150.102.65.10:52299]
      10:11:16,709 INFO [TreeCache] TreeCache local address is 150.102.65.10:52299
      10:11:16,709 INFO [TreeCache] State could not be retrieved (we are the first member in group)
      10:11:16,709 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
      10:11:20,919 INFO [NativeServerConfig] JBoss Web Services - Native
      10:11:20,919 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
      10:11:22,094 INFO [SnmpAgentService] SNMP agent going active
      10:11:22,610 INFO [JChannel] JGroups version: 2.4.1 SP-4
      10:11:22,759 INFO [workstation_32_development_Rochester] Initializing
      10:11:22,809 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 150.102.65.10:52303
      -------------------------------------------------------
      10:11:24,817 INFO [workstation_32_development_Rochester] Number of cluster members: 1
      10:11:24,818 INFO [workstation_32_development_Rochester] Other members: 0
      10:11:24,818 INFO [workstation_32_development_Rochester] Fetching state (will wait for 30000 milliseconds):
      10:11:24,818 INFO [workstation_32_development_Rochester] State could not be retrieved (we are the first member in group)
      10:11:24,862 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=cars/150.102.65.10
      10:11:24,868 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on cars/150.102.65.10:1102, group=228.1.2.10, HA-JNDI address=150.102.65.10:1100
      10:11:26,171 INFO [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
      10:11:26,336 INFO [JChannel] JGroups version: 2.4.1 SP-4
      10:11:26,481 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 150.102.65.10:52309
      -------------------------------------------------------
      10:11:28,485 INFO [TreeCache] viewAccepted(): [150.102.65.10:52309|0] [150.102.65.10:52309]
      10:11:28,486 INFO [TreeCache] TreeCache local address is 150.102.65.10:52309
      10:11:28,640 INFO [JChannel] JGroups version: 2.4.1 SP-4
      10:11:28,790 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is 150.102.65.10:52312
      -------------------------------------------------------
      10:11:30,794 INFO [TreeCache] viewAccepted(): [150.102.65.10:52312|0] [150.102.65.10:52312]
      10:11:30,796 INFO [TreeCache] TreeCache local address is 150.102.65.10:52312
      


      Looks great, right? cars is the only machine in the cluster with the partition name workstation_32_development_Rochester. Before when we all were using DefaultPartition, and only had unique mcast_ports, many other ip addresses showed up in the list following "[TreeCache] viewAccepted():"

      Then, for unknown reasons it tries to access another machine called "wizard":

      10:12:52,894 INFO [QuartzJob] startSingleton(): Start QuartzJob Singleton
      10:12:57,500 ERROR [QuartzJob] *********************Exception Thrown*********************
      10:12:57,501 ERROR [QuartzJob] createJobAndTrigger(): null
      10:12:57,501 ERROR [QuartzJob] *********************End of Exception*********************
      10:12:57,501 ERROR [STDERR] javax.naming.CommunicationException [Root exception is java.rmi.RemoteException: Service unavailable.; nested exception is:
       java.rmi.ConnectIOException: Exception creating connection to: wizard; nested exception is:
       java.net.NoRouteToHostException: No route to host]
      10:12:57,502 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
      10:12:57,502 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
      10:12:57,502 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
      10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.jobInvoiceHandlerJob(QuartzJob.java:797)
      10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.createJobAndTrigger(QuartzJob.java:849)
      10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.startSingleton(QuartzJob.java:390)
      10:12:57,502 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      10:12:57,502 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      10:12:57,503 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      10:12:57,503 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
      10:12:57,503 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      10:12:57,503 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      10:12:57,503 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      10:12:57,503 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      10:12:57,503 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.java:207)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:144)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.singleton.HASingletonSupport.startNewMaster(HASingletonSupport.java:272)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:254)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:196)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:247)
      10:12:57,503 ERROR [STDERR] at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:846)
      10:12:57,504 ERROR [STDERR] at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.add(DistributedReplicantManagerImpl.java:409)
      10:12:57,504 ERROR [STDERR] at org.jboss.ha.jmx.HAServiceMBeanSupport.registerDRMListener(HAServiceMBeanSupport.java:255)
      10:12:57,504 ERROR [STDERR] at org.jboss.ha.jmx.HAServiceMBeanSupport.startService(HAServiceMBeanSupport.java:177)
      10:12:57,504 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
      10:12:57,504 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
      10:12:57,504 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
      10:12:57,504 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      10:12:57,504 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
      10:12:57,504 ERROR [STDERR] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
      10:12:57,504 ERROR [STDERR] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
      10:12:57,504 ERROR [STDERR] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
      10:12:57,504 ERROR [STDERR] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
      


      wizard used to be in cars' /etc/hosts/ file, but I commented it out, so it makes sense that it cannot create a connection.

      What I do not understand is, why is it trying to connect to wizard?????

      I have searched and searched again and there is no reference to wizard in any config files nor is cars still trying to use DefaultPartition!

      Any help would be GREATLY appreciated!!!

      Thanks,
      Josephine

        • 1. Re: clustering/JMS problem among machines not using same par
          Josephine Schwabel Newbie

          A few other things to note....

          We are using Quartz v1.4.0.

          We are using Apache v2.0.6x.

          Everything looks great at the JMX console for cars, but if I try to login to the actual application, I get another Connection Exception to wizard!

          • 2. Re: clustering/JMS problem among machines not using same par
            Josephine Schwabel Newbie

            I upgraded to Quartz 1.6.4 and that didn't help.
            I checked JBOSS_HOME/server/appserver/deploy/jms/hajndi-ds.xml and the following are set as expected:

            jnp.partitionName=${jboss.partition.name:DefaultPartition}
            jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}

            • 3. Re: clustering/JMS problem among machines not using same par
              Josephine Schwabel Newbie

              A former co-worker suggested that I try adding -b 0.0.0.0 to the start and that worked!!!
              I honestly don't understand why because without -b 0.0.0.0, it says in the jboss log:

              13:30:21,078 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=cars/150.102.65.10
              13:30:21,085 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on cars/150.102.65.10:1102, group=228.1.2.10, HA-JNDI address=150.102.65.10:1100
              


              which has nothing to do with wizard!!

              With -b 0.0.0.0, it says in the jboss log:
              13:36:34,526 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=/0.0.0.0
              13:36:34,533 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on 0.0.0.0/0.0.0.0:1102, group=228.1.2.10, HA-JNDI address=150.102.65.10:1100
              


              and it no longer tries to connect with wizard.

              • 4. Re: clustering/JMS problem among machines not using same par
                Brian Stansberry Master

                What is going on in here?

                10:12:57,502 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
                10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.jobInvoiceHandlerJob(QuartzJob.java:797)
                10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.createJobAndTrigger(QuartzJob.java:849)
                10:12:57,502 ERROR [STDERR] at kdcs.timers.QuartzJob.startSingleton(QuartzJob.java:390)
                


                That is, what environment properties are being passed to new InitialContext(Hashtable props) before the lookup call is made?

                You commented that the following are set in hajndi-ds.xml:

                jnp.partitionName=${jboss.partition.name:DefaultPartition}
                jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}

                but your stack trace doesn't involve the JMSProviderLoader. Make sure the equivalent entries are in the environment properties you pass to new InitialContext. I suspect an HA-JNDI auto discovery call is getting a response from a "wizard" server which AIUI is not meant to be involved. If the "wizard" server has a different partition name and you include jnp.partitionName=${jboss.partition.name:DefaultPartition} you won't get an auto discovery response from "wizard" and won't try to connect to it.

                • 5. Re: clustering/JMS problem among machines not using same par
                  Josephine Schwabel Newbie

                  Brian - thank you for your response!

                  I'm not actually sending anything to InitialContext()....Here's the call:

                  InitialContext ic = new InitialContext();
                  Scheduler sched = (Scheduler) ic.lookup("Quartz");
                  ic.close();
                  


                  The middle line is the one that throws the CommunicationException.

                  You are correct, wizard should NOT be involved.

                  wizard does indeed have a different partition name AND JBoss is not running even running on wizard. I don't see how/why cars could possibly get an auto discovery response from wizard.

                  Regards,
                  Josephine

                  • 6. Re: clustering/JMS problem among machines not using same par
                    Josephine Schwabel Newbie

                    Here's our jndi.properties file:

                    java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
                    java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
                    


                    • 7. Re: clustering/JMS problem among machines not using same par
                      Brian Stansberry Master

                      Perhaps the whole "wizard" thing is a red-herring due to a reverse DNS problem? The word "wizard" appears here in the message of a java.rmi.ConnectIOException; perhaps that's getting created with a call to InetAddress.getHostName() which does a reverse lookup and says "wizard" when it should say "cars"?

                      The other strange is why it's trying to make a remote connection to do the JNDI lookup at all. With no properties passed to new InitialContext() and the jndi.properties you listed, a NamingContext running inside the AS should be making a direct call against the local NamingServer.

                      • 8. Re: clustering/JMS problem among machines not using same par
                        Josephine Schwabel Newbie

                        Brian - the reverse DNS problem sounds like a great idea. I checked and the DNS servers I'm using are QUITE messed up, BUT none of them point cars to wizard or wizard to cars and cars' /etc/hosts file is "clean" (ie, no wizard). I am at my wit's end!

                        • 9. Re: clustering/JMS problem among machines not using same par
                          Josephine Schwabel Newbie

                          Here's a new piece of info....I tried using "-b hostname" on another set of servers and they do not try to connect to my archenemy wizard, BUT none of the remote lookups work. They all fail with the following exception:

                          2009-02-10 16:51:53,612 ERROR [STDERR] javax.naming.CommunicationException [Root exception is java.rmi.RemoteException: Service unavailable.; nested exception is:
                           java.rmi.NoSuchObjectException: no such object in table]
                          2009-02-10 16:51:53,612 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:351)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at kdcs.common.jndi.EJBHomeFactory.lookup(EJBHomeFactory.java:114)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at kdcs.common.CommonMethods.getHome(CommonMethods.java:1585)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at http.wrapper.CPSListener.getHome(CPSListener.java:160)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at http.wrapper.CPSListener.init(CPSListener.java:195)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at javax.servlet.GenericServlet.init(GenericServlet.java:212)
                          2009-02-10 16:51:53,612 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4071)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4375)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                          2009-02-10 16:51:53,613 ERROR [STDERR] at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.web.WebModule.startModule(WebModule.java:83)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.web.WebModule.startService(WebModule.java:61)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
                          2009-02-10 16:51:53,614 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
                          
                          ....
                          
                          2009-02-10 16:51:53,619 ERROR [STDERR] Caused by: java.rmi.RemoteException: Service unavailable.; nested exception is:
                           java.rmi.NoSuchObjectException: no such object in table
                          2009-02-10 16:51:53,619 ERROR [STDERR] at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:261)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:321)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at $Proxy847.lookup(Unknown Source)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:675)
                          2009-02-10 16:51:53,619 ERROR [STDERR] ... 144 more
                          2009-02-10 16:51:53,619 ERROR [STDERR] Caused by: java.rmi.NoSuchObjectException: no such object in table
                          2009-02-10 16:51:53,619 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
                          2009-02-10 16:51:53,619 ERROR [STDERR] at org.jboss.ha.framework.server.HARMIServerImpl_Stub.invoke(Unknown Source)
                          2009-02-10 16:51:53,620 ERROR [STDERR] at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:219)
                          2009-02-10 16:51:53,620 ERROR [STDERR] ... 147 more
                          


                          However, if I use "-b 0.0.0.0" upon start I do not get the RemoteExceptions and the servers seem to cluster only with the other servers with their partion name, upd group, and mcast port.
                          So, I guess I'm done, but I would still really like to know what is up with cars/wizard and why all the RemoteExceptions?

                          • 10. Re: clustering/JMS problem among machines not using same par
                            Brian Stansberry Master

                            There is something wrong with how JNDI is working in that application. That stack trace shows that the call is using an HA-JNDI proxy to make a remote call to an HA-JNDI server. That shouldn't be needed for code running inside the AS; the org.jnp.interfaces.NamingContext.lookup() method should be a direct call on the naming server running inside the AS -- no remote call.

                            Please confirm:

                            1) You don't have a jndi.properties file anywhere in anything you deployed inside the AS. The only one that should be there is the one in the AS's conf/ dir.

                            2) You are using the standard JBoss AS JNDI service; i.e. you haven't replaced it with something.

                            3) The config of your NamingBeanImpl inside conf/jboss-service.xml looks like this:

                             <mbean code="org.jnp.server.NamingBeanImpl"
                             name="jboss:service=NamingBeanImpl"
                             xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml">
                             </mbean>