karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Lichtin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2348) Tooling-Exam does not wait for a complete test container shutdown
Date Wed, 19 Jun 2013 09:06:21 GMT

    [ https://issues.apache.org/jira/browse/KARAF-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687798#comment-13687798
] 

Martin Lichtin commented on KARAF-2348:
---------------------------------------

Ah, thanks. Only 3 migration issues left.. 

1. Is defining the 'strategy' no longer necessary? So far I've used

   import org.ops4j.pax.exam.junit.ExamReactorStrategy;
   import org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactorFactory;

2. For the @Inject, javax.inject.Inject was pulled in as a dependency from org.apache.karaf.tooling.exam.container.
   Not sure where to get this package from now. 

3. What should I replace "org.ops4j.pax.exam.CoreOptions.scanFeatures" with?

                
> Tooling-Exam does not wait for a complete test container shutdown
> -----------------------------------------------------------------
>
>                 Key: KARAF-2348
>                 URL: https://issues.apache.org/jira/browse/KARAF-2348
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-tooling
>    Affects Versions: 2.3.1
>            Reporter: Martin Lichtin
>
> Symptoms of the issue:
>  - a subsequent Karaf tooling exam test cannot open its ports
>  - the target folder cannot be deleted. log output:
>    ("Can't remove runtime system; shedule it for exit of the jvm.")
> The approach to stop Karaf is to stop bundle 0. However, KarafJavaRunner
> should then also wait for the Karaf process in its shutdown() method.
> Probably something like
>     @Override
>     public synchronized void shutdown() {
>         // runner.shutdown();
>         runner.waitForExit(); // and calls runner.shutdown()
>     }

--
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

Mime
View raw message