[arquillian-issues] [JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown correctly in a Maven build

Vineet Reynolds (JIRA) jira-events at lists.jboss.org
Sat Nov 17 16:38:21 EST 2012


     [ https://issues.jboss.org/browse/ARQ-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vineet Reynolds updated ARQ-837:
--------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/arquillian/arquillian-container-glassfish/pull/19


Added a shutdown hook that fires a {{stop-domain}} command against the running instance of GlassFish. Takes a few seconds to run, and is meant to handle problematic versions of Surefire.

I could not use {{Process.destroy()}} since we do not have a handle to the actual AS process, which is forked from the initial {{start-domain}} invocation.
                
> Managed GlassFish container does not shutdown correctly in a Maven build
> ------------------------------------------------------------------------
>
>                 Key: ARQ-837
>                 URL: https://issues.jboss.org/browse/ARQ-837
>             Project: Arquillian
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: GlassFish Containers
>    Affects Versions: glassfish_1.0.0.CR3
>         Environment: Maven 3.0.3, Surefire 2.7.2
>            Reporter: Vineet Reynolds
>            Assignee: Vineet Reynolds
>
> When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message:
> {quote}
> The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
> To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
> {quote}
> The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the arquillian-issues mailing list