-
1. Re: Multiple JBoss Instances
frebe73 Jan 30, 2002 8:43 AM (in response to rsrivast)Have you changed port in standardjboss.xml from 4444 to something else? It solved some problems for me.
I have still one problem: Both instances are using %JOSS_DIST%/tmp/Default for deployed ear-files. Maybe you can help me. -
2. Re: Multiple JBoss Instances
frebe73 Jan 30, 2002 9:24 AM (in response to rsrivast)You should also change the name of the deployer in mbean
org.jboss.deployment.J2eeDeployer
/Fredrik -
3. Re: Multiple JBoss Instances
rsrivast Jan 30, 2002 1:26 PM (in response to rsrivast)ok, I finally reconfigured all the ports and started the server successfully. The second server throws these exceptions during startup. It is not able to start the JBossMQService. Also, CTRL-C stops ALL jboss instances. Not able to start multiple instances if jboss is a major show stopper!
[JBossMQService] Starting
[Default] tracePriority = TRACE
[Default] Port configured to: 2324
[Default] JBossMQ listening on PORT: 2324
[Default] Port configured to: 2324
[Default] Closing socket: Initialization
[Default] java.net.BindException: Address in use: JVM_Bind
[Default] at java.net.PlainSocketImpl.socketBindNative Method)
[Default]
[Default] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405)
[Default]
[Default] at java.net.ServerSocket.(ServerSocket.java:170)
[Default]
[Default] at java.net.ServerSocket.(ServerSocket.java:82)
[Default]
[Default] at org.jbossmq.distributed.server.DistributedJMSServerUIL.export
Object(DistributedJMSServerUIL.java:94)
[Default]
[Default] at org.jbossmq.distributed.server.DistributedJMSServerUIL.init(D
istributedJMSServerUIL.java:296)
[Default]
[Default] at org.jbossmq.server.InvocationLayerFactory.createObjects(Invoc
ationLayerFactory.java:65)
[Default]
[Default] at org.jbossmq.server.StartServer.run(StartServer.java:230)
[Default]
[Default] at org.jbossmq.server.StartServer.start(StartServer.java:72)
[Default]
[Default] at org.jbossmq.server.JBossMQService.startService(JBossMQService
.java:66)
[Default]
[Default] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.
java:107)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1628)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1523)
[Default]
[Default] at org.jboss.configuration.ConfigurationService$ServiceProxy.inv
oke(ConfigurationService.java:836)
[Default]
[Default] at $Proxy0.start(Unknown Source)
[Default]
[Default] at org.jboss.util.ServiceControl.start(ServiceControl.java:81)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1628)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1523)
[Default]
[Default] at org.jboss.Main.(Main.java:210)
[Default]
[Default] at org.jboss.Main$1.run(Main.java:116)
[Default]
[Default] at java.security.AccessController.doPrivileged(Native Method)
[Default]
[Default] at org.jboss.Main.main(Main.java:112)
[Default]
[Default] Cannot start the JMS server ! null
[Default] java.lang.NullPointerException
[Default] at org.jbossmq.distributed.server.DistributedJMSServerUIL.create
Client(DistributedJMSServerUIL.java:274)
[Default]
[Default] at org.jbossmq.server.InvocationLayerFactory.createObjects(Invoc
ationLayerFactory.java:66)
[Default]
[Default] at org.jbossmq.server.StartServer.run(StartServer.java:230)
[Default]
[Default] at org.jbossmq.server.StartServer.start(StartServer.java:72)
[Default]
[Default] at org.jbossmq.server.JBossMQService.startService(JBossMQService
.java:66)
[Default]
[Default] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.
java:107)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1628)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1523)
[Default]
[Default] at org.jboss.configuration.ConfigurationService$ServiceProxy.inv
oke(ConfigurationService.java:836)
[Default]
[Default] at $Proxy0.start(Unknown Source)
[Default]
[Default] at org.jboss.util.ServiceControl.start(ServiceControl.java:81)
[Default]
[Default] at java.lang.reflect.Method.invoke(Native Method)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1628)
[Default]
[Default] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl
.java:1523)
[Default]
[Default] at org.jboss.Main.(Main.java:210)
[Default]
[Default] at org.jboss.Main$1.run(Main.java:116)
[Default]
[Default] at java.security.AccessController.doPrivileged(Native Method)
[Default]
[Default] at org.jboss.Main.main(Main.java:112)
[Default]
[JBossMQService] Started
[JMSProviderLoader] Starting
[JMSProviderLoader] bound adapter DefaultJMSProvider to java:/DefaultJMSProvider -
4. Re: Multiple JBoss Instances
adrian.brock Jan 30, 2002 1:46 PM (in response to rsrivast)Have a look at the following link.
There is no port redefinition required :-)
http://www.geocrawler.com/lists/3/SourceForge/10767/500/7544127/
He answered me privately that this does indeed work.
Regards,
Adrian -
5. Re: Multiple JBoss Instances
frebe73 Feb 1, 2002 6:31 AM (in response to rsrivast)Do not use Ctrl-C for stopping a JBoss instance. Use the class org.jboss.Shutdown instead.
I am not using MQ but it sounds that you have missed some port reconfiguration somewhere.
/Fredrik -
6. Re: Multiple JBoss Instances
edludke Mar 26, 2002 4:41 PM (in response to rsrivast)The meat of the post that the above link points to is:
"Try adding -Djava.rmi.server.hostname to run.sh . . ."
This needs to be in a FAQ (if it isn't already).
Or even better: Why doesn't the default script, that is distributed with the release, have this option to begin with?
As someone who was just trying to get started with JBoss, this bind exception crud has been incredibly frustrating.
Please don't get me wrong - I'm grateful that something like JBoss even exists, but this bind error has hit me from a couple of different ways and I suspect it's making things a bit tough for alot of the newbies out there.
I think this tip was the key though, so thanks!
Ed Ludke