[jboss-user] [JBoss Tools] - Re: Alpha2 sporadic deployment problems

Jesper Skov do-not-reply at jboss.com
Fri Oct 19 07:52:38 EDT 2012 

Jesper Skov [https://community.jboss.org/people/jskovjyskebankdk] created the discussion

"Re: Alpha2 sporadic deployment problems"

To view the discussion, visit: https://community.jboss.org/message/767045#767045

--------------------------------------------------------------
The other issue is related to the start/stop of the server.

We had problems starting EAP511 with the JBossTools4 defaults, so we changed (both) state detectors to JMX.

The server would start fine, but a stop always causes this:


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



And looking in one of the logs, we saw the below (note third entry):


!ENTRY org.jboss.ide.eclipse.as.core 4 16973826 2012-10-18 10:44:30.447
 !MESSAGE The server was shutdown forcefully. All processes were terminated.

!ENTRY org.jboss.ide.eclipse.as.core 4 16842768 2012-10-18 10:44:30.525
 !MESSAGE Server Shutdown Failed

!ENTRY org.jboss.ide.eclipse.as.core 4 33816577 2012-10-18 10:44:32.447
 !MESSAGE Error adding deployment folder to deployment scanner

!STACK 0
 javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1: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.ide.eclipse.as.jmx.integration.JBossServerConnection.createConnection(JBossServerConnection.java:159)
     at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
     at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
     at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:105)
     at org.jboss.ide.eclipse.as.jmx.integration.JBossJMXConnectionProviderModel.run(JBossJMXConnectionProviderModel.java:79)
     at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureScannersAdded(JMXServerLifecycleListener.java:65)
     at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.modifyDeploymentScanners(JMXServerLifecycleListener.java:54)
     at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions$1.run(LocalJBoss7DeploymentScannerAdditions.java:127)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1: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)
     ... 12 more

Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
     at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
     ... 13 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)
     ... 13 more





So this happened as part of a server restart.

It may not be a full explanation, since some of the other developers don't restart unless they already see deployment problems....


I've asked them all to switch Shutdown Poller to 'Process Terminated' which I suspect will fix the problem when caused as a side effect of a bad shutdown.
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/767045#767045]

Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2128]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20121019/da4b10ec/attachment.html

More information about the jboss-user mailing list