[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1891) Error when stopping JBoss

[Gene Gretter (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12406279 ] 
            
Gene Gretter commented on JBIDE-1891:
-------------------------------------

I have tried a couple of scenarios and here it what I have found:

Note: I am now running with Server Timeout Delay set to Normal.

I tried your suggestion and changed the Startup Poller to Timeout Poller.  With this change I am able to start JBoss.  I then tried
setting Startup Poller back to JMX Poller and found that if I also set Start Timeout to zero, then I am able to start JBoss.  One issue
I noticed is that when I go back into Preferences -> JBoss Tools -> JBoss Servers, the Start Timeout is displayed as 450.  This
appears to only be the Display value and not the effective value since I am still able to start JBoss.  I can also change the
Start Timeout to 1 and still start JBoss; however, any value greater than 1 will cause the JBoss Start Failure error.  

I do have the JMX Console enable so I am not sure why there is an issue with the JMX Poller.

Let me know if there is something else you would like me to try.

> Error when stopping JBoss
> -------------------------
>
>                 Key: JBIDE-1891
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1891
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.GA
>         Environment: Windows XP, Eclipse 3.3.1.1, JBoss Tools 2.0.0GA, JBoss 4.2.0
>            Reporter: Gene Gretter
>         Assigned To: Rob Stryker
>             Fix For: 2.1, LATER
>
>
> When stopping JBoss from the Eclipse Server view, I receive the following error:  "Could not obtain connection to any of these urls: localhost:1099".  I found that this problem occurs because the process in which JBoss is running is terminated before shutdown is executed.  I found that eliminating the call to pollServer(IServerStatePoller.SERVER_DOWN); in the JBossServerBehavior.serverStopping() method resolves the problem, though I am not sure that this is the final fix.

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