[
https://jira.jboss.org/jira/browse/JBIDE-5267?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5267:
---------------------------------------
Fix Version/s: 3.1.0.GA
How about an option (which should be default on) on JMX poller that if it timesout assume
it is running ? i.e. that would make the jmx poller finish early if jmx becomes available
but otherwise behave like the timeout poller.
WDYT ?
Maybe even not an option, just make it behave like that an then log a warning about it
somewhere ?
JBoss 5.0 runtime fails to start with minimal server in JBDS 2.1
----------------------------------------------------------------
Key: JBIDE-5267
URL:
https://jira.jboss.org/jira/browse/JBIDE-5267
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.next
Environment: Fedora 11, JBoss Enterprise Application Platform 5.0.0 GA
Reporter: Matt Davis
Assignee: Rob Stryker
Fix For: 3.1.0.GA
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