[jbosstools-issues] [JBoss JIRA] Created: (JBIDE-1350) Cannot stop JBoss server instance when using non-standard JNDI port number

[Rob Hasselbaum (JIRA)]

Cannot stop JBoss server instance when using non-standard JNDI port number
--------------------------------------------------------------------------

                 Key: JBIDE-1350
                 URL: http://jira.jboss.com/jira/browse/JBIDE-1350
             Project: JBoss Tools
          Issue Type: Bug
          Components: JBossAS
    Affects Versions: 2.0.0.CR1
         Environment: Eclipse 3.3.1.1 on openSUSE 10.3
            Reporter: Rob Hasselbaum


I get a communication error when I try to stop a running JBoss AS instance via the "JBoss Server" view in Eclipse. The error (pasted below) suggests that it is trying to contact the JNDI service on port 1099. However, in my environment, JNDI is configured to listen on port 1299. (I configured this by modifying the NamingService bean definition in "conf/jboss-service.xml" and "conf/jboss-minimal.xml".)

In the past, I think you could specify the JNDI port via the "Stop args" and "Twiddle args" tabs in the launch configuration, but according to the referenced forum post, those tabs have been removed in JBoss Tools 2.0, and somehow the plugin is supposed to automatically detect the JNDI port. It doesn't seem to be working here, though.

Stack trace for 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 refused]]]
	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
	at javax.naming.InitialContext.lookup(InitialContext.java:392)
	at org.jboss.Shutdown.main(Shutdown.java:214)
Caused by: 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 refused]]
	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385)
	... 4 more
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:243)
	... 5 more
Caused by: java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:519)
	at java.net.Socket.connect(Socket.java:469)
	at java.net.Socket.<init>(Socket.java:366)
	at java.net.Socket.<init>(Socket.java:267)
	at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
	at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
	... 5 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira