[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-1128) Stop/ server does not have failsafe behavior

[Max Andersen (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-1128?page=all ]

Max Andersen updated JBIDE-1128:
--------------------------------

    Priority: Critical  (was: Major)

> Stop/ server does not have failsafe behavior
> --------------------------------------------
>
>                 Key: JBIDE-1128
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1128
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.CR1
>            Reporter: Max Andersen
>         Assigned To: Rob Stryker
>            Priority: Critical
>             Fix For: 2.0.0.CR1
>
>
> e.g. if the server runs out of memory and I click stop I got the following in the console:
> 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 retrieve stub from server localhost:1099 [Root exception is java.io.EOFException]]
> 	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
> 	at javax.naming.InitialContext.lookup(InitialContext.java:351)
> 	at org.jboss.Shutdown.main(Shutdown.java:214)
> Caused by: javax.naming.CommunicationException: Failed to retrieve stub from server localhost:1099 [Root exception is java.io.EOFException]
> 	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:263)
> 	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
> 	... 4 more
> Caused by: java.io.EOFException
> 	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498)
> 	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273)
> 	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
> 	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:251)
> 	... 5 more
> And the server state is now forever "Stopping..." and I can't do anything about it.
> Why don't we register that communication failure and forcefully kill the server ? (of course asking the user first) then the server can get back to "normal"

-- 
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