[jira] Updated: (STANBOL-84) The integration test harness is leaking running JVM processes

["Olivier Grisel (JIRA)" <ji...@apache.org>]

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

Olivier Grisel updated STANBOL-84:
----------------------------------

    Priority: Minor  (was: Critical)

By protecting the StanbolTestCase init against concurrent classloading it seems that I no longer get leaked processes. Hence I downgrade the level to minor. I will try to further implement the early subprocess stopping in @AfterClass if not too complicated to implement.

> The integration test harness is leaking running JVM processes
> -------------------------------------------------------------
>
>                 Key: STANBOL-84
>                 URL: https://issues.apache.org/jira/browse/STANBOL-84
>             Project: Stanbol
>          Issue Type: Bug
>            Reporter: Olivier Grisel
>            Priority: Minor
>
> At least on my machine, after a successful run of "mvn clean install" from the top-level stanbol folder I get:
>     $ ps aux | grep integration-tests | grep -v grep
>     ogrisel  10603 11.5  6.0 1108056 481348 pts/1  Sl   12:03   0:18 java -Xmx512m -jar /home/ogrisel/coding/stanbol-svn/enhancer/integration-tests/target/dependency/org.apache.stanbol.enhancer.launchers.full-0.9-SNAPSHOT.jar -p 51738
> This is an inconvenience for the individual developers to have to kill the JVMs manually but would also be a major service disruption if this is happening on the ASF Hudson slaves, hence the critical level. If for whatever reason this is not happening on the Hudson slaves, we can downgrade this issue to minor.
> I don't seem to have the rights to ssh into the slave to check myself.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira