Open amichair opened 10 months ago
Just to clarify, I'm referring to my application's itests, not pax exam's own tests (which I haven't run).
Also happens on Pax Exam 4.13.6-SNAPSHOT as of this writing.
Is there any general roadmap for when the next release might come out, hopefully fixing this issue?
Hello
See how I "solved" this problem with Pax Web: https://github.com/ops4j/org.ops4j.pax.web/blob/main/pax-web-itest/pax-web-itest-karaf/pom.xml#L43-L44 ;)
And see related https://issues.apache.org/jira/browse/SUREFIRE-1374
regards Grzegorz Grzybek
czw., 26 paź 2023 o 09:09 amichair @.***> napisał(a):
Is there any general roadmap for when the next release might come out, hopefully fixing this issue?
— Reply to this email directly, view it on GitHub https://github.com/ops4j/org.ops4j.pax.exam2/issues/1093#issuecomment-1780537206, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACK3BNAFGZWJ6KIGCPEJPLYBIEDXAVCNFSM6AAAAAA47QCRNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBQGUZTOMRQGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I think I'm seeing PAXEXAM-920 re-surface when upgrading maven-failsafe-plugin from 2.22.2 to 3.1.2 (running in Karaf 4.4.4, Pax Exam 4.13.3, OpenJDK 11.0.20.1+1, Linux). With 2.22.2 all is fine, and after changing to 3.1.2, for some application itests, the tests pass successfully but then hang for 30 seconds and the console shows
I haven't fully analyzed what's going on, though it seems the forked JVM has no application threads left running, and the only non-daemon thread is the main one stuck waiting for an ack for a bye command or something like that. Sounds very similar to the original issue description...