The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Sat, 17 Apr 2004 9:50 AM
Changes:
assignee changed from Cactus Developers Mailing List
description changed from It happens sometimes that the <cactus> task
tells JBoss to shutdown whereas
JBoss has not completely finished starting. This leads to an exception trace
on the console from JBoss saying that it has not finished starting.
The reason is that we're polling a URL from the servlet container and this
container is listening on its port before JBoss is fully started.
One possible better implementation would be to use JMX to ask JBoss whether it
is started or not (if possible). to It happens sometimes that the <cactus> task tells
JBoss to shutdown whereas
JBoss has not completely finished starting. This leads to an exception trace
on the console from JBoss saying that it has not finished starting.
The reason is that we're polling a URL from the servlet container and this
container is listening on its port before JBoss is fully started.
One possible better implementation would be to use JMX to ask JBoss whether it
is started or not (if possible).
environment changed from Operating System: Other
Platform: Other to Operating System: Other
Platform: Other
priority changed to Major
Fix Version changed to 1.7
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/CACTUS-62?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/CACTUS-62
Here is an overview of the issue:
---------------------------------------------------------------------
Key: CACTUS-62
Summary: Sometimes, JBoss is stopped before it has finished starting
Type: Bug
Status: Unassigned
Priority: Major
Project: Cactus
Components:
Ant Integration
Fix Fors:
1.7
Versions:
1.5-beta1
Assignee:
Reporter: Vincent Massol
Created: Thu, 23 Oct 2003 12:40 PM
Updated: Sat, 17 Apr 2004 9:50 AM
Environment: Operating System: Other
Platform: Other
Description:
It happens sometimes that the <cactus> task tells JBoss to shutdown whereas
JBoss has not completely finished starting. This leads to an exception trace
on the console from JBoss saying that it has not finished starting.
The reason is that we're polling a URL from the servlet container and this
container is listening on its port before JBoss is fully started.
One possible better implementation would be to use JMX to ask JBoss whether it
is started or not (if possible).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
