Alexander,
Sleep deprevation (3 week old) is kickin' in. Tried it again back from the beginning with a conf/clone and started hacking. Per your instruction it did work this time; although it required removal from jboss.conf; no modification to jboss.jcml was made. It does appear that I cannot have the same jndi name bound on two different servers; what I really wanted. The second registration stomps the first. I assume I still get the JMX & RMI support just throught the first server.
Are there any good alternatives people are using for better fault tolerance?
John Moore
-----Original Message-----
From: John Moore [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 3:26 PM
To: 'jBoss'
Subject: RE: [jBoss-User] Containers on Multiple Machines
Thanks, but I seem to have a different baseline configuration. I don't have anyting in the jboss.jcml file ([jBoss]/conf/default/jboss.jcml) that references either the jmx or rmi. There is certainly no direct reference to "Adaptor:name=RMI" in the conf/default directory or in any .conf or .properties file under the [jBoss] installation directory. I do have a MLET entries in the [jBoss]/conf/default/jboss.conf. Commenting those out has not helped. Also, there are no deployed applications, this is the 2.0 Final downloaded this morning, and I am running Solaris 8/Sparc 1.3 JVM. The jndi.properties file to refer to the first hostname. No changes were made to the jnp.properties file.
The error I receive is:
# ./run.sh
:run.jar:../lib/jdbc2_0-stdext.jar:../lib/jboss-jaas.jar
Using configuration "default"
[Console logging] Initialized
[Classpath extension] Initializing
..... { whole lotta things starting up normally }
[SpyderMQ] Started
[JMX RMI Adaptor] Starting
[JMX RMI Adaptor] Stopped
[JMX RMI Adaptor] javax.naming.NameAlreadyBoundException
[JMX RMI Adaptor] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
[JMX RMI Adaptor] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
[JMX RMI Adaptor] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
[JMX RMI Adaptor] at org.jnp.server.NamingServer_Stub.bind(Unknown Source)
[JMX RMI Adaptor] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:260)
[JMX RMI Adaptor] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:232)
[JMX RMI Adaptor] at javax.naming.InitialContext.bind(InitialContext.java:358)
[JMX RMI Adaptor] at org.jboss.jmx.server.JMXAdaptorService.startService(JMXAdaptorService.java:78)
[JMX RMI Adaptor] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:92)
[JMX RMI Adaptor] at java.lang.reflect.Method.invoke(Native Method)
[JMX RMI Adaptor] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
[JMX RMI Adaptor] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
[JMX RMI Adaptor] at org.jboss.dependencies.DependencyManager.startMBean(DependencyManager.java:284)
[JMX RMI Adaptor] at org.jboss.dependencies.DependencyManager.startMBeans(DependencyManager.java:126)
[JMX RMI Adaptor] at org.jboss.Main.<init>(Main.java:162)
[JMX RMI Adaptor] at org.jboss.Main$1.run(Main.java:87)
[JMX RMI Adaptor] at java.security.AccessController.doPrivileged(Native Method)
[JMX RMI Adaptor] at org.jboss.Main.main(Main.java:83)
[Default] Error starting service 'Adaptor:name=RMI': javax.management.MBeanException: Exception thrown in operation start
[Default] Unable to start MBean 'Adaptor:name=RMI'
[JMX RMI Connector] Starting
[JMX RMI Connector] Started
[Default] 23 services and 4 other MBeans started.
[Default] Shutdown hook added
[Default] jBoss 2.0 FINAL Started
-----Original Message-----
From: Alexander Kogan [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 05, 2001 2:30 PM
To: jBoss
Subject: Re: [jBoss-User] Containers on Multiple Machines
John,
I was doing such thing with some success.
You were definitely in the right track
with removing duplicated services.
I finished up by removing only JMX adapters
(JMXAdaptorService, RMIConnectorService)
from the secondary server (in jboss.jcml) and
everything worked (ok, almost).
I was doing dynamic classes downloading
and it didn't work from the second server.
Regards,
Alex.
> John Moore wrote:
>
> Is it possible to have jBoss running on two different servers with a
> common jnp? I'm not sure if this qualifies as clustering; which is
> clearly stated as a non-supported function. I have tried to just get
> the 2nd container up and running and continually run into exceptions at
> the JMX RMI? I've tried to remove different services from the
> jboss.conf file (e.g. naming, sypderMQ, etc ) with no success. Is there
> a configuration that will allow this to happen. Also, if this is just
> generally a bad idea from a performance/design standpoint I'd be happy
> to know that too before I go too far the wrong direction.
>
> Thanks,
> John Moore
>
> John Moore [mailto:[EMAIL PROTECTED]]
> PDSI
> 625 The City Drive
> Suite 190
> Orange, CA 92868
> 800-850-7374
--
__________________________________________________
Alexander Kogan PTC www.ptc.com
[EMAIL PROTECTED] 140 Kendrick St. Needham MA 02494
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
