[ https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751239#comment-12751239 ]
Rob Stryker commented on JBIDE-12913:
-------------------------------------
Jesper:
This dialog only shows up if the poller recognizes something on the 'web port'. The web port is set in your server editor, so if you have some other value other than 8080 there, then that's where its polling.
The three pollers are pretty hard (almost impossible) to trick into believing there's a running server when there isn't. The web poller makes a simple web connection to your server's hostname (set in the server editor's "host" section) at the web port (set int he server editor).
Typically we do not set the host to 0.0.0.0. If you want to bind to all ports, your hostname should remain 'localhost' but you should check the "Listen on all interfaces to allow remote web connections" checkbox. This ensures that your server editor still says your host is localhost, but when launched, jboss will receive the -b 0.0.0.0 flags.
I suppose I haven't tested this in the situation of a server who's HOSTNAME is 0.0.0.0, but this should not be done.
See if this makes a difference for you.
> Startup/Shutdown Pollers fails with EAP511
> ------------------------------------------
>
> Key: JBIDE-12913
> URL: https://issues.jboss.org/browse/JBIDE-12913
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha2
> Environment: Windows XP
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Fix For: 4.0.0.Beta2
>
> Attachments: server-startup-poller-problem.png
>
>
> When we use Web Port Startup Poller with EAP511, the server is not started.
> We get an error about the port (8080) already being in use. Which it is not (confirmed with netstat).
> When changing Startup Poller to JMX, the server starts as expected.
> When using the JMX Shutdown Poller, it also fails. This time with failed attempts to access the JMX server after the server has shut down:
> Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 0.0.0.0:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
> at javax.naming.InitialContext.lookup(Unknown Source)
> at org.jboss.Shutdown.main(Shutdown.java:219)
> Caused by: javax.naming.CommunicationException: Failed to connect to server /0.0.0.0:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
> at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
> ... 4 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server /0.0.0.0:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
> ... 5 more
> Caused by: java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(Unknown Source)
> at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
> at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
> at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
> ... 5 more
> Using Process Terminated Poller works as expected though.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira