From dev-return-8749-apmail-aries-dev-archive=aries.apache.org@aries.apache.org Tue Jan 3 17:59:25 2012 Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B8EC195DE for ; Tue, 3 Jan 2012 17:59:25 +0000 (UTC) Received: (qmail 75060 invoked by uid 500); 3 Jan 2012 17:59:25 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 75024 invoked by uid 500); 3 Jan 2012 17:59:25 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 75015 invoked by uid 99); 3 Jan 2012 17:59:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 17:59:25 +0000 X-ASF-Spam-Status: No, hits=-2001.6 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 17:59:24 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E129F1362D1 for ; Tue, 3 Jan 2012 17:58:39 +0000 (UTC) Date: Tue, 3 Jan 2012 17:58:39 +0000 (UTC) From: "Alasdair Nottingham (Commented) (JIRA)" To: dev@aries.apache.org Message-ID: <1882138938.1103.1325613519923.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1007765280.156.1325592759666.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (ARIES-805) Blueprint container should re-enter Creating state when GracePeriod state is finished MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARIES-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178867#comment-13178867 ] Alasdair Nottingham commented on ARIES-805: ------------------------------------------- I don't think the Blueprint specification would allow us to do this. The event transition diagram for blueprint (on page 207 of the Enterprise 4.2 specification) shows the events we are allowed to emit and there is none for the grace period ending. We also can't set the replay flag because that is only valid when a listener is first registered. I do think this is a reasonable requirement so I'm going to email the EEG and get their view, but this probably isn't going to result in a quick fix. > Blueprint container should re-enter Creating state when GracePeriod state is finished > ------------------------------------------------------------------------------------- > > Key: ARIES-805 > URL: https://issues.apache.org/jira/browse/ARIES-805 > Project: Aries > Issue Type: Improvement > Components: Blueprint > Affects Versions: 0.2 > Environment: ServiceMix 4.3 > Reporter: metatech > Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > When a component is starting, the Blueprint container implementation (class BlueprintContainerImpl) enters the "Creating" state. > If a external dependency (namespace handler or OSGI service reference) is not available yet, it enters the "GracePeriod" state. > Once the GracePeriod is finished, the creation is performed, which ends up with the "Created" state. > However, when the creation takes a long time (for instance, in an ActiveMQ cluster configuration, the slave node waits forever until the master node goes down), the state is reported as "GracePeriod", although it is actually suspended in the "Creating" state. > This reporting can be misleading and makes troubleshooting require detailed understanding of the Blueprint states and transitions semantics . It would be clearer to re-fire a "Creating" state Blueprint event (possibly with the "replay" flag). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira