[
https://issues.apache.org/jira/browse/MTOMCAT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oriel Maute updated MTOMCAT-305:
--------------------------------
Description:
We have a multi-module project with the modules A and B.
In module A we start and stop an embedded tomcat server within our integration
tests; same in module B.
The integration-tests for module A work perfectly. But after this, the start of
the embedded tomcat server for module B is not working because the port 8080 is
still in use from the integration test of module A.
The reason is that the shutdown on module A invokes on the Catalina Container
the "stop()" method, this method does not unbind the port 8080.
I think - specially in this scenario - the shutdown mojo should also invoke the
"destroy()" method after the "stop()" method on the Catalina Container. If this
is not possible in every case, it would be great to have a parameter for the
shutdown goal to specify if "stop" or "stop & destroy" should be called on the
Catalina Container.
was:
We have a multi-module project with the modules A and B.
In module A we start and stop an embedded tomcat server within our integration
tests; same in module B.
The integration-tests for module A work perfectly. But after this, the start of
the embedded tomcat server for module B is not working because the port 8080 is
still in use from the integration test of module A.
The reason is that the shutdown on module A invokes on the Catalina Container
the "stop()" method, this method does not unbind the port 8080.
I think - specially in this scenario - the shutdown mojo should invoke the
"destroy()" method on the Catalina Container. If this is not possible in every
case, it would be great to have a parameter for the shutdown goal to specify if
"stop" or "destroy" should be called on the Catalina Container.
> shutdown not correct working if embedded tomcat is started twice in same
> maven build
> ------------------------------------------------------------------------------------
>
> Key: MTOMCAT-305
> URL: https://issues.apache.org/jira/browse/MTOMCAT-305
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.2
> Environment: multi-module project
> Reporter: Oriel Maute
> Assignee: Olivier Lamy (*$^¨%`£)
> Labels: maven
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> We have a multi-module project with the modules A and B.
> In module A we start and stop an embedded tomcat server within our
> integration tests; same in module B.
> The integration-tests for module A work perfectly. But after this, the start
> of the embedded tomcat server for module B is not working because the port
> 8080 is still in use from the integration test of module A.
> The reason is that the shutdown on module A invokes on the Catalina Container
> the "stop()" method, this method does not unbind the port 8080.
> I think - specially in this scenario - the shutdown mojo should also invoke
> the "destroy()" method after the "stop()" method on the Catalina Container.
> If this is not possible in every case, it would be great to have a parameter
> for the shutdown goal to specify if "stop" or "stop & destroy" should be
> called on the Catalina Container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
