11:40 a.m.
Implement a Graceful Shutdown API and Implementation
-----------------------------------------------------
Key: JBBOOT-116
URL: https://jira.jboss.org/jira/browse/JBBOOT-116
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
As identified by the Summer 2009 AS Meeting.
Requirements:
* Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies
* 2-phase event-listener registration API
* May be injected into MC Beans
* 1st phase is a concurrent broadcast to all subsystems which have registered:
"prepare for shutdown"
* When all listeners have reported "ready", fire 2nd phase:
"shutdown"
--
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
12:08 p.m.
New subject: [JBoss JIRA] Commented: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation
[
https://jira.jboss.org/jira/browse/JBBOOT-116?page=com.atlassian.jira.plu...
]
Andrew Lee Rubinger commented on JBBOOT-116:
--------------------------------------------
This may have to become an MC component, to be aware of the dependencies.
JBossWeb > EJB3 > JCA
JBossWeb must stop accepting new connections before EJB3 does, else the new connection may
come in via Web and then blow up upon hitting EJB3.
I see 3 solutions:
1) ThreadLocal to mark that you have an incoming request in process. Other subsystems
must honor this regardless of if they've already halted other normal requests. Ugly
contract.
2) Tie into MC dependency mechanism through some add-on
3) New lifecycle phase like "pre-stop", where we add this graceful shutdown
handling. Then the dep chain is built into and fired from MC, and we take advantage of
this in a lifecycle callback.
Implement a Graceful Shutdown API and Implementation
-----------------------------------------------------
Key: JBBOOT-116
URL: https://jira.jboss.org/jira/browse/JBBOOT-116
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
As identified by the Summer 2009 AS Meeting.
Requirements:
* Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies
* 2-phase event-listener registration API
* May be injected into MC Beans
* 1st phase is a concurrent broadcast to all subsystems which have registered:
"prepare for shutdown"
* When all listeners have reported "ready", fire 2nd phase:
"shutdown"
--
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
12:36 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation
[
https://jira.jboss.org/jira/browse/JBBOOT-116?page=com.atlassian.jira.plu...
]
Andrew Lee Rubinger edited comment on JBBOOT-116 at 11/23/09 1:36 PM:
----------------------------------------------------------------------
This may have to be spun up outside jboss-bootstrap, to be aware of the dependencies.
JBossWeb > EJB3 > JCA
JBossWeb must stop accepting new connections before EJB3 does, else the new connection may
come in via Web and then blow up upon hitting EJB3.
I see 3 solutions:
1) ThreadLocal to mark that you have an incoming request in process. Other subsystems
must honor this regardless of if they've already halted other normal requests. Ugly
contract.
2) Tie into MC dependency mechanism through some add-on
3) New lifecycle phase like "pre-stop", where we add this graceful shutdown
handling. Then the dep chain is built into and fired from MC, and we take advantage of
this in a lifecycle callback.
was (Author: ALRubinger):
This may have to become an MC component, to be aware of the dependencies.
JBossWeb > EJB3 > JCA
JBossWeb must stop accepting new connections before EJB3 does, else the new connection may
come in via Web and then blow up upon hitting EJB3.
I see 3 solutions:
1) ThreadLocal to mark that you have an incoming request in process. Other subsystems
must honor this regardless of if they've already halted other normal requests. Ugly
contract.
2) Tie into MC dependency mechanism through some add-on
3) New lifecycle phase like "pre-stop", where we add this graceful shutdown
handling. Then the dep chain is built into and fired from MC, and we take advantage of
this in a lifecycle callback.
Implement a Graceful Shutdown API and Implementation
-----------------------------------------------------
Key: JBBOOT-116
URL: https://jira.jboss.org/jira/browse/JBBOOT-116
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
As identified by the Summer 2009 AS Meeting.
Requirements:
* Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies
* 2-phase event-listener registration API
* May be injected into MC Beans
* 1st phase is a concurrent broadcast to all subsystems which have registered:
"prepare for shutdown"
* When all listeners have reported "ready", fire 2nd phase:
"shutdown"
--
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
9:39 a.m.
New subject: [JBoss JIRA] Commented: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation
[
https://jira.jboss.org/browse/JBBOOT-116?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf commented on JBBOOT-116:
--------------------------------------
This also needs to apply to CORBA traffic.
Implement a Graceful Shutdown API and Implementation
-----------------------------------------------------
Key: JBBOOT-116
URL: https://jira.jboss.org/browse/JBBOOT-116
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
As identified by the Summer 2009 AS Meeting.
Requirements:
* Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies
* 2-phase event-listener registration API
* May be injected into MC Beans
* 1st phase is a concurrent broadcast to all subsystems which have registered:
"prepare for shutdown"
* When all listeners have reported "ready", fire 2nd phase:
"shutdown"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 a.m.
New subject: [JBoss JIRA] Updated: (JBBOOT-116) Implement a Graceful Shutdown API and Implementation
[
https://issues.jboss.org/browse/JBBOOT-116?page=com.atlassian.jira.plugin...
]
SBS JIRA Integration updated JBBOOT-116:
----------------------------------------
Forum Reference: http://community.jboss.org/message/217818#217818
Implement a Graceful Shutdown API and Implementation
-----------------------------------------------------
Key: JBBOOT-116
URL: https://issues.jboss.org/browse/JBBOOT-116
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Andrew Rubinger
Assignee: Andrew Rubinger
As identified by the Summer 2009 AS Meeting.
Requirements:
* Decoupled sufficiently from other Bootstrap mechanisms as to not leak out dependencies
* 2-phase event-listener registration API
* May be injected into MC Beans
* 1st phase is a concurrent broadcast to all subsystems which have registered:
"prepare for shutdown"
* When all listeners have reported "ready", fire 2nd phase:
"shutdown"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4682
days inactive
5337
days old
4 comments
3 participants
participants (3)
-
Andrew Lee Rubinger (JIRA) -
Carlo de Wolf (JIRA)
-
SBS JIRA Integration (JIRA)