7:06 a.m.
[
https://issues.jboss.org/browse/ARQ-837?page=com.atlassian.jira.plugin.sy...
]
Vineet Reynolds updated ARQ-837:
--------------------------------
Description:
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.
was:
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.
Managed GlassFish container does not shutdown when a test errors out
--------------------------------------------------------------------
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
Reporter: 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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira