[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-941) JBoss 5.0 runtime fails to start with minimal server in JBDS 2.1

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBDS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12494538#action_12494538 ] 

Rob Stryker commented on JBDS-941:
----------------------------------

The problem here is that the default way to check if a server is up is to check via JMX.  I'm not sure what would be a proper fix here. The workaround is to double-click the server and in the server editor, go to the "Server Poller" section and change it to a timeout poller. This will just wait for the set amount of time to expire, and then say the server is up.

One possible fix from my end would be to have the timeout poller be the default poller if the configuration name is "minimal". At one time we had considered checking the server output but had decided that was too cludgy.  We had also considered having an http poller which would just check {hostname}:8080,  but this wouldn't work in the minimal configuration either as the minimal configuration doesn't put anything up by default. 

So any thoughts are welcome, but for now the workaround is to use the timeout poller instead

> JBoss 5.0 runtime fails to start with minimal server in JBDS 2.1
> ----------------------------------------------------------------
>
>                 Key: JBDS-941
>                 URL: https://jira.jboss.org/jira/browse/JBDS-941
>             Project: JBoss Developer Studio
>          Issue Type: Bug
>          Components: servers
>    Affects Versions: 2.1.0
>         Environment: Fedora 11, JBoss Enterprise Application Platform 5.0.0 GA
>            Reporter: Matt Davis
>            Assignee: Rob Stryker
>
> To reproduce, 
> -in the server Window select new server
> - for 'server type' select JBoss AS 5.0
> - for 'Server runtime environment' select JBoss 5.0 Runtime 
> - click 'add' link
>  -point it to an existing 5.0.0.GA server installation
> -under Configuration select minimal
> -add the server
> -start the server in JBDS from the server window
> The server.log will show that the server relatively quickly :
> Started in 10s:285ms
> After 450 seconds (default timeout for JBDS), the following message will pop up :
> Server JBoss 5.0 Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor.
> JBDS will call the shutdown hook for JBoss EAP server.  From the server.log file :
> 2009-11-10 11:27:39,892 INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown Hook) Runtime shutdown hook called, forceHalt: true
> 2009-11-10 11:27:40,843 INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown Hook) Shutdown complete
> The server itself starts up and functions normally. JDBS just doesn't acknowledge that it has started.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira