|Bug in stopping JBoss? [message #206440]
||Mon, 07 January 2008 08:41
Originally posted by: obdennis2007.hotmail.com|
The configuration for server includes a JNDI port number. I have setup two
server configs for JBoss 4 in Eclipse web server tool.
Each of these JBoss server are configured to be able to run at the same
time (i.e. all conflicting ports resolved). They both starts and run fine
in Eclipse. One server is using jndi port 1099 and the other using 11099.
When stopping the one that is 11099, Eclipse reports error:
Exception in thread "main" javax.naming.CommunicationException: Could not
obtain connection to any of these urls: localhost:1099 [Root exception is
javax.naming.CommunicationException: Failed to connect to server
localhost:1099 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect to server
localhost:1099 [Root exception is java.net.ConnectException: Connection
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java :1416)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:5 96)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:5 89)
at javax.naming.InitialContext.lookup(Unknown Source)
This is so when the other (normal standard config server with port 1099)
server is stopped. If that other one is running, stopping the one with
11099 port will stop the 1099 one..
This leads me think that Eclipse is not using the configured 11099 (or
any) in the server config to stop it. It will going to use 1099 (hard
coded somewhere) regardless of the setting made in the server config. I
have verified the xml file in the workspace it is set as 11099 for that
server which failed to stop from Eclipse. Can anyone confirm this?
Thanks in advance.
Powered by FUDForum
. Page generated in 0.01593 seconds