RE: [JBoss-user] HA JNDI trouble
OK, lets forget about the protocol settings first: - why don't you have multicasting? Is that because your 2 nodes are distant/remote or not? - what kind of clients do you have? HTTP or RMI? what usage scenario are you trying to do > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stefan Groschupf > Sent: mardi, 2. septembre 2003 16:41 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] HA JNDI trouble > > > Hi Sacha, > > I would say it is an easy task. > I wish to cluster 2 nodes in the internet that have _no_ multicasting > support. > As described in the cluster docu. i want to setup the servers for the > cluster manually. > Where/How i have to do that? > > Thanks a lot. > Stefan > > > > Sacha Labourey wrote: > > >What are you trying to achieve Stefan? You seem to do very > complexe stuff > >for a quite basic scenario. > > > >First rule: never ever change conf/jndi.properties in any of > the JBoss > >instance configuration: clustering or not, this rule > remains: don't change > >this file. > > > >Cheers, > > > > > > Sacha > > > > > > > >>-Original Message----- > >>From: [EMAIL PROTECTED] > >>[mailto:[EMAIL PROTECTED] On Behalf Of > >>Stefan Groschupf > >>Sent: mardi, 2. septembre 2003 11:38 > >>To: [EMAIL PROTECTED] > >>Subject: Re: [JBoss-user] HA JNDI trouble > >> > >> > >>Hi Guys, > >> > >>i figure out that my HA JNDI was not started since there was an > >>incompatibility between gnu.regex package and the same but > >>older package > >>in an external component i have to use. > >> > >>However not its start and i get via binding manger an test > >>setup running > >>on my home w2k system. Last night i had tried to setup to > >>servers in the > >>net. They do not discover each other. Of curse the > >>multicasting is not > >>available. So i setup on my slave engine the jndi properies: > >> > >>java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory > >>java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces > >># Do NOT uncomment this line as it causes in VM calls to go over > >># RMI! > >>java.naming.provider.url=myserver.biz:1100 > >> > >>my master has the last line not! > >> > >>The master starting well, since he is indenpendent. > >>The slave start with this exception: > >> > >>11:35:26,942 ERROR [JRMPInvoker] Starting failed > >>javax.naming.CommunicationException. Root exception is > >>java.rmi.RemoteException: Service unavailable. > >>at > >>org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HAR > >>MIClient.java:158) > >>at > >>org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClie > >>nt.java:196) > >>at $Proxy11.lookup(Unknown Source) > >>at > >>org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528) > >>at > >>org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) > >>at > javax.naming.InitialContext.lookup(InitialContext.java:347) > >>at > >>org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoke > >>r.java:409) > >>at > >>org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMP > >>Invoker.java:307) > >>at > >>org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JR > >>MPInvoker.java:107) > >>at > >>org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > >>.java:192) > >>at > >>org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker > >>.java:560) > >>at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >>at > >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > >>orImpl.java:39) > >>at > >>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > >>odAccessorImpl.java:25) > >>at java.lang.reflect.Method.invoke(Method.java:324) > >>at > >>org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > >>tedMBeanDispatcher.java:284) > >>at > >>org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > &
Re: [JBoss-user] HA JNDI trouble
Hi Sacha, I would say it is an easy task. I wish to cluster 2 nodes in the internet that have _no_ multicasting support. As described in the cluster docu. i want to setup the servers for the cluster manually. Where/How i have to do that? Thanks a lot. Stefan Sacha Labourey wrote: What are you trying to achieve Stefan? You seem to do very complexe stuff for a quite basic scenario. First rule: never ever change conf/jndi.properties in any of the JBoss instance configuration: clustering or not, this rule remains: don't change this file. Cheers, Sacha -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Groschupf Sent: mardi, 2. septembre 2003 11:38 To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] HA JNDI trouble Hi Guys, i figure out that my HA JNDI was not started since there was an incompatibility between gnu.regex package and the same but older package in an external component i have to use. However not its start and i get via binding manger an test setup running on my home w2k system. Last night i had tried to setup to servers in the net. They do not discover each other. Of curse the multicasting is not available. So i setup on my slave engine the jndi properies: java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces # Do NOT uncomment this line as it causes in VM calls to go over # RMI! java.naming.provider.url=myserver.biz:1100 my master has the last line not! The master starting well, since he is indenpendent. The slave start with this exception: 11:35:26,942 ERROR [JRMPInvoker] Starting failed javax.naming.CommunicationException. Root exception is java.rmi.RemoteException: Service unavailable. at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HAR MIClient.java:158) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClie nt.java:196) at $Proxy11.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoke r.java:409) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMP Invoker.java:307) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JR MPInvoker.java:107) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport .java:192) at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker .java:560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec tedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.system.ServiceController$ServiceProxy.invoke(Service Controller.java:976) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:394) at org.jboss.system.ServiceController.start(ServiceController.java:411) at org.jboss.system.ServiceController.start(ServiceController.java:411) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec tedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec tedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.i
RE: [JBoss-user] HA JNDI trouble
What are you trying to achieve Stefan? You seem to do very complexe stuff for a quite basic scenario. First rule: never ever change conf/jndi.properties in any of the JBoss instance configuration: clustering or not, this rule remains: don't change this file. Cheers, Sacha > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Stefan Groschupf > Sent: mardi, 2. septembre 2003 11:38 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] HA JNDI trouble > > > Hi Guys, > > i figure out that my HA JNDI was not started since there was an > incompatibility between gnu.regex package and the same but > older package > in an external component i have to use. > > However not its start and i get via binding manger an test > setup running > on my home w2k system. Last night i had tried to setup to > servers in the > net. They do not discover each other. Of curse the > multicasting is not > available. So i setup on my slave engine the jndi properies: > > java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory > java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces > # Do NOT uncomment this line as it causes in VM calls to go over > # RMI! > java.naming.provider.url=myserver.biz:1100 > > my master has the last line not! > > The master starting well, since he is indenpendent. > The slave start with this exception: > > 11:35:26,942 ERROR [JRMPInvoker] Starting failed > javax.naming.CommunicationException. Root exception is > java.rmi.RemoteException: Service unavailable. > at > org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HAR > MIClient.java:158) > at > org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClie > nt.java:196) > at $Proxy11.lookup(Unknown Source) > at > org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528) > at > org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) > at javax.naming.InitialContext.lookup(InitialContext.java:347) > at > org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoke > r.java:409) > at > org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMP > Invoker.java:307) > at > org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JR > MPInvoker.java:107) > at > org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport > .java:192) > at > org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker > .java:560) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > orImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > tedMBeanDispatcher.java:284) > at > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > at > org.jboss.system.ServiceController$ServiceProxy.invoke(Service > Controller.java:976) > at $Proxy0.start(Unknown Source) > at > org.jboss.system.ServiceController.start(ServiceController.java:394) > at > org.jboss.system.ServiceController.start(ServiceController.java:411) > at > org.jboss.system.ServiceController.start(ServiceController.java:411) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Reflec > tedMBeanDispatcher.java:284) > at > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > at > org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > at $Proxy4.start(Unknown Source) > at > org.jboss.deployment.SARDeployer.start(SARDeployer.java:226) > at > org.jboss.deployment.MainDeployer.start(MainDeployer.java:824) > at > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632) > at > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) > at > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > orImpl.java:39) > at > su
Re: [JBoss-user] HA JNDI trouble
java.naming.provider.url=myserver.biz:1100 just guessing: should the url start with a perfix like "jnp://myserver.biz:1100" ?? bax my master has the last line not! The master starting well, since he is indenpendent. The slave start with this exception: 11:35:26,942 ERROR [JRMPInvoker] Starting failed javax.naming.CommunicationException. Root exception is java.rmi.RemoteException: Service unavailable. at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:158) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:196) at $Proxy11.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoker.java:409) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:307) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:107) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:394) at org.jboss.system.ServiceController.start(ServiceController.java:411) at org.jboss.system.ServiceController.start(ServiceController.java:411) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291) at org.jboss.Main.boot(Main.java:150) at org.jboss.Main$1.run(Main.java:388) at java.lang.Thread.run(Thread.java:536) 11:35:26,981 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp javax.naming.CommunicationException. Root exception is java.rmi.RemoteException: Service unavailable. at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:158) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:196) I had tried as well IP adresses but no different. I would very happy if someone can give an hint! Thanks a lot! Stefan. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] HA JNDI trouble
Hi Guys, i figure out that my HA JNDI was not started since there was an incompatibility between gnu.regex package and the same but older package in an external component i have to use. However not its start and i get via binding manger an test setup running on my home w2k system. Last night i had tried to setup to servers in the net. They do not discover each other. Of curse the multicasting is not available. So i setup on my slave engine the jndi properies: java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces # Do NOT uncomment this line as it causes in VM calls to go over # RMI! java.naming.provider.url=myserver.biz:1100 my master has the last line not! The master starting well, since he is indenpendent. The slave start with this exception: 11:35:26,942 ERROR [JRMPInvoker] Starting failed javax.naming.CommunicationException. Root exception is java.rmi.RemoteException: Service unavailable. at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:158) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:196) at $Proxy11.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.invocation.jrmp.server.JRMPInvoker.rebind(JRMPInvoker.java:409) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:307) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:107) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:394) at org.jboss.system.ServiceController.start(ServiceController.java:411) at org.jboss.system.ServiceController.start(ServiceController.java:411) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291) at org.jboss.Main.boot(Main.java:150) at org.jboss.Main$1.run(Main.java:388) at java.lang.Thread.run(Thread.java:536) 11:35:26,981 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp javax.naming.CommunicationException. Root exception is java.rmi.RemoteException: Service unavailable. at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:158) at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:196) I had tried as well IP adresses but no different. I would very happy if someone can give an hint
RE: [JBoss-user] HA JNDI trouble
You are right Andrew. Most of the time (not to say always), you change the REMOTE CLIENTS to use HA-JNDI but you NEVER change the server settings in itself. Cheers, Sacha > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Andrew May > Sent: mardi, 2 septembre 2003 10:04 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] HA JNDI trouble > > > I've only played around with clusters, so I could be wrong, > but I think you need to access > HA-JNDI directly on the port it's bound to. If the object > cannot be found in HA-JNDI it > will look in the local JNDI. > > From the clustering docs: > > "When a remote client does a lookup through HA-JNDI, HA-JNDI > will delegate to the local > JNDI Context when it cannot find the object within the global > cluster-wide Context. So, a > EJB home lookup through HA-JNDI, will always be delegated to > the local JNDI instance." > > You should be able to tell whether HA-JNDI is correctly > deployed from either the > server.log or by looking in the JNDI console. > > When you say that you're using the same JNDI for all > instances do you mean that you're > setting the JNDI and/or HA-JNDI ports to be the same for > seperate instances of JBoss? I'm > not aware that you can do this - each JNDI and HA-JNDI should > run on a seperate port. When > you perform a remote lookup you can list multiple server > instances like this: > > java.naming.provier.url=localhost:1100,localhost:1200,localhost:1300 > > Hope that helps. > > -Andrew > > Stefan Groschupf wrote: > > > Hi Bax, > > > > nice to hear you! ;) I use such an pattern and it is generated by > > Xdoclet. I use the BeanUtil classes. > > They make an normal remote lookup. As i understand the > documentation i > > does not need an other lookup. Since the request will be > forwarded to > > the HA JNDI. Isn't it? > > > > Stefan > > > > Holger Baxmann wrote: > > > >> your setup reminds me on the Service Activator Pattern > >> > http://java.sun.com/blueprints/corej2eepatterns/Patterns/Servi > ceActivator.html > >> in conjunction with Session Facade and Service Locator for > decoupling > >> the lookup and the do-something stuff. > >> > >> It could be more easy to solve the clustering jndi problem if you > >> have > >> a facade between for 'hiding' the cluster to the 'client' > --- but i > >> could be totaly wrong here ... > >> > >> regards > >> > >> bax > >> > >> > >> On Mon, 01 Sep 2003 10:12:23 +0200, Stefan Groschupf > >> <[EMAIL PROTECTED]> wrote: > >> > >>> Dear all, > >>> I have massive trouble to get an simple cluster to run. > It sounds in > >>> all publications so easy, but something went wrong here. > >>> I can run multiple instances on my machine via binding > service. The > >>> nodes are discovered and the farming deployment running well. > >>> As you may be remember i have a set of node with my > project A: It is > >>> manually deployed on all nodes. I have my main > application that has > >>> an mdb that run my "job" queue. > >>> > >>> My problem is that it looks like i have no HA JNDI. To > get something > >>> running i setup my instances on my machine to use all the > same jndi > >>> of localhost. ;/ > >>> > >>> But when i setup my nodes in the network to use on jndi on my main > >>> machine it does of curse say that my project is already > deployed. ;( > >>> When i does not setup an jndi host as described in the clustering > >>> documentation i get an Object no bound exception. > >>> > >>> My MDB: > >>> TRExtractorRemote extractor = TRExtractorUtil.getHome().create(); > >>> ProcessedDocument document = > >>> extractor.process(oneValue.getValueExternal()); > >>> (The Remote Object is generated by xdoclet) > >>> Since my nodes are in a win network and the farming works > i think the > >>> multi casting working. > >>> > >>> Really guys i had try everything i had found in the net or in the > >>> documentation and had tried it now 2 days and 2 nights, > since i only > >>> can play with the nodes over night. Someone has any idea where my > >>> proble
Re: [JBoss-user] HA JNDI trouble
I've only played around with clusters, so I could be wrong, but I think you need to access HA-JNDI directly on the port it's bound to. If the object cannot be found in HA-JNDI it will look in the local JNDI. From the clustering docs: "When a remote client does a lookup through HA-JNDI, HA-JNDI will delegate to the local JNDI Context when it cannot find the object within the global cluster-wide Context. So, a EJB home lookup through HA-JNDI, will always be delegated to the local JNDI instance." You should be able to tell whether HA-JNDI is correctly deployed from either the server.log or by looking in the JNDI console. When you say that you're using the same JNDI for all instances do you mean that you're setting the JNDI and/or HA-JNDI ports to be the same for seperate instances of JBoss? I'm not aware that you can do this - each JNDI and HA-JNDI should run on a seperate port. When you perform a remote lookup you can list multiple server instances like this: java.naming.provier.url=localhost:1100,localhost:1200,localhost:1300 Hope that helps. -Andrew Stefan Groschupf wrote: Hi Bax, nice to hear you! ;) I use such an pattern and it is generated by Xdoclet. I use the BeanUtil classes. They make an normal remote lookup. As i understand the documentation i does not need an other lookup. Since the request will be forwarded to the HA JNDI. Isn't it? Stefan Holger Baxmann wrote: your setup reminds me on the Service Activator Pattern http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceActivator.html in conjunction with Session Facade and Service Locator for decoupling the lookup and the do-something stuff. It could be more easy to solve the clustering jndi problem if you have a facade between for 'hiding' the cluster to the 'client' --- but i could be totaly wrong here ... regards bax On Mon, 01 Sep 2003 10:12:23 +0200, Stefan Groschupf <[EMAIL PROTECTED]> wrote: Dear all, I have massive trouble to get an simple cluster to run. It sounds in all publications so easy, but something went wrong here. I can run multiple instances on my machine via binding service. The nodes are discovered and the farming deployment running well. As you may be remember i have a set of node with my project A: It is manually deployed on all nodes. I have my main application that has an mdb that run my "job" queue. My problem is that it looks like i have no HA JNDI. To get something running i setup my instances on my machine to use all the same jndi of localhost. ;/ But when i setup my nodes in the network to use on jndi on my main machine it does of curse say that my project is already deployed. ;( When i does not setup an jndi host as described in the clustering documentation i get an Object no bound exception. My MDB: TRExtractorRemote extractor = TRExtractorUtil.getHome().create(); ProcessedDocument document = extractor.process(oneValue.getValueExternal()); (The Remote Object is generated by xdoclet) Since my nodes are in a win network and the farming works i think the multi casting working. Really guys i had try everything i had found in the net or in the documentation and had tried it now 2 days and 2 nights, since i only can play with the nodes over night. Someone has any idea where my problem could be located? I use jboss-3.2.2RC3_jetty-4.2.11. Thanks for giving me light! Stefan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] HA JNDI trouble
Hi Bax, nice to hear you! ;) I use such an pattern and it is generated by Xdoclet. I use the BeanUtil classes. They make an normal remote lookup. As i understand the documentation i does not need an other lookup. Since the request will be forwarded to the HA JNDI. Isn't it? Stefan Holger Baxmann wrote: your setup reminds me on the Service Activator Pattern http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceActivator.html in conjunction with Session Facade and Service Locator for decoupling the lookup and the do-something stuff. It could be more easy to solve the clustering jndi problem if you have a facade between for 'hiding' the cluster to the 'client' --- but i could be totaly wrong here ... regards bax On Mon, 01 Sep 2003 10:12:23 +0200, Stefan Groschupf <[EMAIL PROTECTED]> wrote: Dear all, I have massive trouble to get an simple cluster to run. It sounds in all publications so easy, but something went wrong here. I can run multiple instances on my machine via binding service. The nodes are discovered and the farming deployment running well. As you may be remember i have a set of node with my project A: It is manually deployed on all nodes. I have my main application that has an mdb that run my "job" queue. My problem is that it looks like i have no HA JNDI. To get something running i setup my instances on my machine to use all the same jndi of localhost. ;/ But when i setup my nodes in the network to use on jndi on my main machine it does of curse say that my project is already deployed. ;( When i does not setup an jndi host as described in the clustering documentation i get an Object no bound exception. My MDB: TRExtractorRemote extractor = TRExtractorUtil.getHome().create(); ProcessedDocument document = extractor.process(oneValue.getValueExternal()); (The Remote Object is generated by xdoclet) Since my nodes are in a win network and the farming works i think the multi casting working. Really guys i had try everything i had found in the net or in the documentation and had tried it now 2 days and 2 nights, since i only can play with the nodes over night. Someone has any idea where my problem could be located? I use jboss-3.2.2RC3_jetty-4.2.11. Thanks for giving me light! Stefan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] HA JNDI trouble
your setup reminds me on the Service Activator Pattern http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceActivator.html in conjunction with Session Facade and Service Locator for decoupling the lookup and the do-something stuff. It could be more easy to solve the clustering jndi problem if you have a facade between for 'hiding' the cluster to the 'client' --- but i could be totaly wrong here ... regards bax On Mon, 01 Sep 2003 10:12:23 +0200, Stefan Groschupf <[EMAIL PROTECTED]> wrote: Dear all, I have massive trouble to get an simple cluster to run. It sounds in all publications so easy, but something went wrong here. I can run multiple instances on my machine via binding service. The nodes are discovered and the farming deployment running well. As you may be remember i have a set of node with my project A: It is manually deployed on all nodes. I have my main application that has an mdb that run my "job" queue. My problem is that it looks like i have no HA JNDI. To get something running i setup my instances on my machine to use all the same jndi of localhost. ;/ But when i setup my nodes in the network to use on jndi on my main machine it does of curse say that my project is already deployed. ;( When i does not setup an jndi host as described in the clustering documentation i get an Object no bound exception. My MDB: TRExtractorRemote extractor = TRExtractorUtil.getHome().create(); ProcessedDocument document = extractor.process(oneValue.getValueExternal()); (The Remote Object is generated by xdoclet) Since my nodes are in a win network and the farming works i think the multi casting working. Really guys i had try everything i had found in the net or in the documentation and had tried it now 2 days and 2 nights, since i only can play with the nodes over night. Someone has any idea where my problem could be located? I use jboss-3.2.2RC3_jetty-4.2.11. Thanks for giving me light! Stefan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
