Mailing-List: contact commits-help@openejb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openejb.apache.org
Message-ID: <4978383.37781287459869194.JavaMail.jira@thor>
Date: Mon, 18 Oct 2010 23:44:29 -0400 (EDT)
From: "David Blevins (JIRA)" <jira@apache.org>
To: commits@openejb.apache.org
Subject: [jira] Updated: (OPENEJB-1305) Standalone Server shutdown fails
In-Reply-To: <30259894.110611277802232874.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENEJB-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Blevins updated OPENEJB-1305:
-----------------------------------

    Fix Version/s:     (was: 3.1.x)

> Standalone Server shutdown fails
> --------------------------------
>
>                 Key: OPENEJB-1305
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1305
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.2
>         Environment: All
>            Reporter: Andy Gumbrecht
>            Assignee: Andy Gumbrecht
>             Fix For: (trunk/openejb3)
>
>         Attachments: Server.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The 'Server' component is never registered so the following call fails with a null pointer.
> Server server = SystemInstance.get().getComponent(Server.class);
> server.stop();
> The order of shutdown in Server.java should be:
> OpenEJB.destroy();
> manager.stop();
> Remove redundant code in SimpleServiceManager.java - In fact the removed code could potentially cause shutdown race conditions on RA's if Server.stop() is called.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.