I've tried changing to that version as well, didn't work.
If I run the command that broke the test:
"C:\Program Files\Java\jdk1.8.0_161\jre\bin\java"
-javaagent:C:\Users\Ferdi_S672\Documents\Personal\Projects\tomee\container\openejb-core\target\openejb-javaagent-8.0.0-SNAPSHOT.jar
-Dopenejb.classloader.forced-skip=org.apache.openejb.jee.,org.apache.openejb.api.
-Dopenejb.classloader.forced-load=org.apache.openejb -enableassertions
-Dopenejb.descriptors.output.folder=./dump/
-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=org,java -jar
C:\Users\FERDI_~1\AppData\Local\Temp\surefire4923413819281954940\surefirebooter7579699950053744316.jar
C:\Users\Ferdi_S672\AppData\Local\Temp\surefire4923413819281954940
2018-11-27T15-00-14_583-jvmRun1 surefire7936970543296277600tmp
surefire_04537004988640125092tmp
I got this:
# Created at 2018-11-27T15:08:14.729
System.exit() or native command error interrupted process checker.
java.lang.IllegalStateException: Cannot use PPID 5228 process
information. Going to use NOOP events.
at
org.apache.maven.surefire.booter.PpidChecker.checkProcessInfo(PpidChecker.java:155)
at
org.apache.maven.surefire.booter.PpidChecker.isProcessAlive(PpidChecker.java:116)
at
org.apache.maven.surefire.booter.ForkedBooter$2.run(ForkedBooter.java:214)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
On 11/26/2018 8:02 PM, Jonathan Gallimore wrote:
> Going to fire this off on a Linux and a Windows machine here to see a) if I
> see the same thing, and b) see if I can give some pointers. I don't have
> ideas right off the top of my head at the moment. Romain's suggestion is
> definitely worth a try.
>
> For reference, we have a CI build here:
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8 - it doesn't look
> like we have the same issue there (we have different ones!)
>
> Thanks for trying this - and thanks for trying it on a Windows machine too,
> its good to know whether it is or isn't working there.
>
> Jon
>
> On Mon, Nov 26, 2018 at 7:55 AM Romain Manni-Bucau <rmannibu...@gmail.com>
> wrote:
>
>> Hi Ferdi,
>>
>> surefire got some "hiccup" in last versions, maybe try 3.0.0-M1 or or
>> 2.22.1 which should work, if not the output dump can help sometimes to
>> identify if it is a memory issue or (more likely) another one.
>>
