[
http://jira.amdatu.org/jira/browse/AMDATU-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10813#comment-10813
]
Bram de Kruijff commented on AMDATU-142:
----------------------------------------
@Toni we were on 1.2.2 so I upgraded under AMDATU-281 . Not sure yet that it
solves all our ploblems though. Problems only occur on the CI (except for
CTRL-C scenario on windows) but don't think it is concurrent execution as we
only have one build agent. Anyway, once I have more intel I'll drop it on the
OPS4J list. Thanks so far!
> 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
