[
http://jira.amdatu.org/jira/browse/AMDATU-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10810#comment-10810
]
Toni Menzel commented on AMDATU-142:
------------------------------------
Can you make sure that you use a recent version like 1.2.3 of Exam?
Also, do the locks just happen on a CI Server with possibly concurrent
instantiations of tests ?
Would like to help out on this issue.
If you need quick help/support, don't hesitate to show op on the OPS4J
Mailinglist.
Toni
> Ghost java processes after terminating build during Pax Exam integration tests
> ------------------------------------------------------------------------------
>
> Key: AMDATU-142
> URL: http://jira.amdatu.org/jira/browse/AMDATU-142
> Project: Amdatu
> Issue Type: Bug
> Components: Integration Tests
> Affects Versions: 0.0.5
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_21
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_21\jre
> Default locale: nl_NL, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
> Reporter: Bram de Kruijff
> Priority: Critical
>
> When you kill the build (eg ^C on windows) during integration-test phase (eg
> because a test hands, see AMDATU-137) java processes forked by Pax Exam are
> not terminated. This is really anoying as these processes consume system
> resources and keep locks on the filesystem sometimes causing subsequent
> actions/builds to fail.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
