12:46 a.m.
Jesper Skov created JBIDE-12913:
-----------------------------------
Summary: 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
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
5:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12913:
-------------------------------------
seems theres two shutdown pollers launched. Horrid race condition where first poller may
somehow get indications the server is shut down, force-terminate the process, all before
the shutdown has actually launched itself. Then the shutdown command fails and the server
is marked as started again. (?!). Investigating.
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
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
6:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12913:
-------------------------------------
also seems jmxpoller was never meant to be a shutdown poller. Not sure how it slipped in.
It is not coded at all for shutdown, only startup. Ugh.
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
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
6:52 a.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12913.
---------------------------------
Resolution: Done
i am 100% unable to replicate any such 'port in use' issues. From the way you
phrase the error, it seems this is the server sayign the port is in use, and not the
tooling. If the tooling felt 8080 was in use, it would simply mark the server as started.
I will not address webpoller in this jira.
Things i did fix:
1) on shutdown, two pollers were launched instead of one. This has been fixed
2) JMX poller was very badly coded and not prepared to handle shutdown requests... only
startup requests. This has been fixed.
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
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
6:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Jesper Skov commented on JBIDE-12913:
-------------------------------------
Suits me. Just glad to help you find things to fix :)
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
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
4:37 p.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Denis Golovin updated JBIDE-12913:
----------------------------------
Fix Version/s: 4.0.0.Beta2
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
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
4:32 a.m.
[
https://issues.jboss.org/browse/JBIDE-12913?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-12913.
---------------------------------
I tried using different options for startup and shutdown poller with EAP 5.1.2 and all
seems to work. Verified in JBT 4.0.0.Beta2 B43.
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
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
4898
days inactive
4919
days old
jbosstools-issues@lists.jboss.org
6 comments
4 participants
participants (4)
-
Denis Golovin (JIRA) -
Jesper Skov (JIRA)
-
Martin Malina (JIRA)
-
Rob Stryker (JIRA)