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

[Rob Stryker (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12406953 ] 
            
Rob Stryker commented on JBIDE-1891:
------------------------------------

Ok... So...

I recognize there's an issue with negative (unlimited) delay. I don't have a solution to that *right* now, but, I'm more concerened about why your server isnt starting properly to begin with. You say you've gotten it to work with timeout poller, and so that's a plus.   At least you have that work-around. 

My suggestion to you is:  
  1) Server Timeout delay =>  "Normal" 
  2) Start Timeout => 450
  3) Stop Timeout => 450
  4) Startup Poller => JMX Poller

I really want to figure out why the JMX poller isn't working for startup ;) 

>I then tried to start JBoss and received the error "Server JBoss 4.2 Server Failed to Start". 

Try to start the server and get this error up again. When it happens, tell me:
 1)  How long was it after trying to start that you got that error?
 2)  What does the Event Log say in the JBoss Servers View? 

Thanks ;) 

> 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: LATER, 2.2.x
>
>
> 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