Hi,
Inorder to run more than one JBoss instance on a single rhel host, I edited the
ports jboss uses. I was able to startup jboss on new ports and use it. But
shutdown.sh -S is still looking on port 1099 and so jboss is not stopping.
These are changes i made:
jboss-3.2.5/server/default/deploy/jbossweb-tomcat50.sar/server.xml
--------------------------------------------------
8080 --> 9080
8009 --> 9009
jboss-3.2.5/server/default/deploy/jmx-console.war/cluster/clusterView.jsp
--------------------------------------------------
8080 --> 9080
jboss-3.2.5/server/default/deploy/jmx-console.war/cluster/bootstrap.html
--------------------------------------------------
1099 --> 9099
jboss-3.2.5/server/default/conf/jboss-minimal.xml
--------------------------------------------------
1099 --> 9099
jboss-3.2.5/server/default/conf/jboss-service.xml
--------------------------------------------------
8083 --> 9083
1098 --> 9098
1099 --> 9099
4444 --> 9444
4445 --> 9445
Please note that, I have taken care to set correct JBOSS_HOME and shutdown.sh
is picking up correct classpath. Error message I am getting is:
18:14:16,700 WARN [NamingContext] Failed to connect to localhost:1099
javax.naming.CommunicationException: Failed to connect to server localhost:1099
[Root exception is javax.naming.ServiceUnavailableException: Failed to connect t
o server localhost:1099 [Root exception is java.net.ConnectException:
Connection refused]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:213)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1185)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:188)
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server
localhost:1099 [Root exception is java.net.ConnectException: Connection
refused]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:187)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.(Socket.java:309)
at java.net.Socket.(Socket.java:211)
at
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
at
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:183)
... 5 more
Exception in thread "main" javax.naming.CommunicationException: Could not
obtain connection to any of these urls: localhost:1099
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1198)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:188)
thanks for your help.
regards,
sreedhar.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867476#3867476
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867476
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
