You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Ferdi <de...@ferdi.id> on 2018/11/26 07:25:34 UTC
Building TomEE, openejb-core, crashed test:
org.apache.openejb.assembler.DeployerEjbTest
Hi,
I've got the latest master from github and was trying to run `mvn clean
install`, but I've got this error:
[ERROR] Crashed tests:
[ERROR] org.apache.openejb.assembler.DeployerEjbTest
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
ExecutionException The forked VM terminated without properly saying
goodbye. VM crash or System.exit called?
[ERROR] Command was cmd.exe /X /C ""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\surefire925326680556375235\surefirebooter1103379934330427088.jar
C:\Users\Ferdi_S672\AppData\Local\Temp\surefire925326680556375235
2018-11-26T14-39-15_252-jvmRun1 surefire1842635169862471047tmp
surefire_521382701203330047466tmp"
[ERROR] Process Exit Code: 0
[ERROR] Crashed tests:
[ERROR] org.apache.openejb.assembler.DeployerEjbTest
The rest is in this gist:
<https://gist.github.com/ferdisn/19d4d8d697d12f3c1bcc2787483b3b67>
Has anyone found / seen this before? I've tried:
1. -Xmx1024m -XX:MaxPermSize=256m
2. -Xmx2048m -XX:MaxPermSize=512m
3. Change Surefire to 2.22
My computer has 16 GB RAM, and plenty of space available during the run.
Re: Building TomEE, openejb-core, crashed test:
org.apache.openejb.assembler.DeployerEjbTest
Posted by Bruno Baptista <br...@gmail.com>.
Hi All,
I've also experienced this error a few times. Never tried to change the
surefire version, though.
Bruno Baptista
https://twitter.com/brunobat_
On 26/11/18 07:25, Ferdi wrote:
> Hi,
>
> I've got the latest master from github and was trying to run `mvn
> clean install`, but I've got this error:
>
> [ERROR] Crashed tests:
> [ERROR] org.apache.openejb.assembler.DeployerEjbTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C ""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\surefire925326680556375235\surefirebooter1103379934330427088.jar
> C:\Users\Ferdi_S672\AppData\Local\Temp\surefire925326680556375235
> 2018-11-26T14-39-15_252-jvmRun1 surefire1842635169862471047tmp
> surefire_521382701203330047466tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] org.apache.openejb.assembler.DeployerEjbTest
>
> The rest is in this gist:
> <https://gist.github.com/ferdisn/19d4d8d697d12f3c1bcc2787483b3b67>
>
> Has anyone found / seen this before? I've tried:
>
> 1. -Xmx1024m -XX:MaxPermSize=256m
> 2. -Xmx2048m -XX:MaxPermSize=512m
> 3. Change Surefire to 2.22
>
> My computer has 16 GB RAM, and plenty of space available during the run.
Re: Building TomEE, openejb-core, crashed test:
org.apache.openejb.assembler.DeployerEjbTest
Posted by Ferdi <de...@ferdi.id>.
Tried on linux, works. Well, the test failed, but at least maven wasn't
terminated abruptly.
On Windows, still getting the same message, but this time a new problem:
C:\Users\Ferdi_S672\Documents\Personal\Projects\tomee (master -> origin)
λ "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\surefire7924936420170998629\surefirebooter7022447534707396131.jar
C:\Users\Ferdi_S672\AppData\Local\Temp\surefire7924936420170998629
2018-11-28T09-38-01_693-jvmRun1 surefire50447437123862647tmp
surefire_728217078389408279960tmp
Error: Unable to access jarfile
C:\Users\FERDI_~1\AppData\Local\Temp\surefire7924936420170998629\surefirebooter7022447534707396131.jar
The referenced jar in Temp wasn't there, so the test failed.
On 11/27/2018 10:37 PM, Jonathan Gallimore wrote:
> I managed to reproduce the issue - looks like it works ok under Cygwin on
> my machine, but not in a DOS box. A brief test has shown some better
> results with surefire 2.18.1 - can you give that a try?
>
> Jon
>
> On Tue, Nov 27, 2018 at 10:40 AM Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
>
>> The build on my Windows machine here ran for ages, and then the machine
>> rebooted for some weird reason. It seemed to get further through the
>> openejb-core tests than yours from the log I have here. Going to run it
>> again. Thanks for including the command, that is really useful.
>>
>> For completeness, here's my java -version and mvn -v output:
>>
>> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
>> $ java -version
>> openjdk version "1.8.0_181"
>> OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_181-b13)
>> OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.181-b13, mixed mode)
>>
>> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
>> $ mvn -v
>> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
>> 2018-06-17T19:33:14+01:00)
>> Maven home: C:\Java\apache-maven-3.5.4
>> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
>> C:\Java\jdk8u181-b13\jre
>> Default locale: en_GB, platform encoding: Cp1252
>> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>>
>> I can try different JDK versions if we think that might be a factor.
>>
>> Cheers
>>
>> Jon
>>
>> On Tue, Nov 27, 2018 at 7:10 AM Ferdi <de...@ferdi.id> wrote:
>>
>>> 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 <
>>> rmannibucau@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.
>>>>>
>>>
>>>
>
Re: Building TomEE, openejb-core, crashed test: org.apache.openejb.assembler.DeployerEjbTest
Posted by Jonathan Gallimore <jo...@gmail.com>.
I managed to reproduce the issue - looks like it works ok under Cygwin on
my machine, but not in a DOS box. A brief test has shown some better
results with surefire 2.18.1 - can you give that a try?
Jon
On Tue, Nov 27, 2018 at 10:40 AM Jonathan Gallimore <
jonathan.gallimore@gmail.com> wrote:
> The build on my Windows machine here ran for ages, and then the machine
> rebooted for some weird reason. It seemed to get further through the
> openejb-core tests than yours from the log I have here. Going to run it
> again. Thanks for including the command, that is really useful.
>
> For completeness, here's my java -version and mvn -v output:
>
> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
> $ java -version
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_181-b13)
> OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.181-b13, mixed mode)
>
> jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
> $ mvn -v
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T19:33:14+01:00)
> Maven home: C:\Java\apache-maven-3.5.4
> Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
> C:\Java\jdk8u181-b13\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> I can try different JDK versions if we think that might be a factor.
>
> Cheers
>
> Jon
>
> On Tue, Nov 27, 2018 at 7:10 AM Ferdi <de...@ferdi.id> wrote:
>
>> 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 <
>> rmannibucau@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.
>> >>
>>
>>
Re: Building TomEE, openejb-core, crashed test: org.apache.openejb.assembler.DeployerEjbTest
Posted by Jonathan Gallimore <jo...@gmail.com>.
The build on my Windows machine here ran for ages, and then the machine
rebooted for some weird reason. It seemed to get further through the
openejb-core tests than yours from the log I have here. Going to run it
again. Thanks for including the command, that is really useful.
For completeness, here's my java -version and mvn -v output:
jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
$ java -version
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.181-b13, mixed mode)
jon@DESKTOP-D9NMDPA /cygdrive/c/Users/jon/dev/tomee
$ mvn -v
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T19:33:14+01:00)
Maven home: C:\Java\apache-maven-3.5.4
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
C:\Java\jdk8u181-b13\jre
Default locale: en_GB, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
I can try different JDK versions if we think that might be a factor.
Cheers
Jon
On Tue, Nov 27, 2018 at 7:10 AM Ferdi <de...@ferdi.id> wrote:
> 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 <
> rmannibucau@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.
> >>
>
>
Re: Building TomEE, openejb-core, crashed test:
org.apache.openejb.assembler.DeployerEjbTest
Posted by Ferdi <de...@ferdi.id>.
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 <rm...@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.
>>
Re: Building TomEE, openejb-core, crashed test: org.apache.openejb.assembler.DeployerEjbTest
Posted by Jonathan Gallimore <jo...@gmail.com>.
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 <rm...@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.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le lun. 26 nov. 2018 à 08:25, Ferdi <de...@ferdi.id> a écrit :
>
> > Hi,
> >
> > I've got the latest master from github and was trying to run `mvn clean
> > install`, but I've got this error:
> >
> > [ERROR] Crashed tests:
> > [ERROR] org.apache.openejb.assembler.DeployerEjbTest
> > [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> > ExecutionException The forked VM terminated without properly saying
> > goodbye. VM crash or System.exit called?
> > [ERROR] Command was cmd.exe /X /C ""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\surefire925326680556375235\surefirebooter1103379934330427088.jar
> >
> > C:\Users\Ferdi_S672\AppData\Local\Temp\surefire925326680556375235
> > 2018-11-26T14-39-15_252-jvmRun1 surefire1842635169862471047tmp
> > surefire_521382701203330047466tmp"
> > [ERROR] Process Exit Code: 0
> > [ERROR] Crashed tests:
> > [ERROR] org.apache.openejb.assembler.DeployerEjbTest
> >
> > The rest is in this gist:
> > <https://gist.github.com/ferdisn/19d4d8d697d12f3c1bcc2787483b3b67>
> >
> > Has anyone found / seen this before? I've tried:
> >
> > 1. -Xmx1024m -XX:MaxPermSize=256m
> > 2. -Xmx2048m -XX:MaxPermSize=512m
> > 3. Change Surefire to 2.22
> >
> > My computer has 16 GB RAM, and plenty of space available during the run.
> >
>
Re: Building TomEE, openejb-core, crashed test: org.apache.openejb.assembler.DeployerEjbTest
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le lun. 26 nov. 2018 à 08:25, Ferdi <de...@ferdi.id> a écrit :
> Hi,
>
> I've got the latest master from github and was trying to run `mvn clean
> install`, but I've got this error:
>
> [ERROR] Crashed tests:
> [ERROR] org.apache.openejb.assembler.DeployerEjbTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
> ExecutionException The forked VM terminated without properly saying
> goodbye. VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C ""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\surefire925326680556375235\surefirebooter1103379934330427088.jar
>
> C:\Users\Ferdi_S672\AppData\Local\Temp\surefire925326680556375235
> 2018-11-26T14-39-15_252-jvmRun1 surefire1842635169862471047tmp
> surefire_521382701203330047466tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] org.apache.openejb.assembler.DeployerEjbTest
>
> The rest is in this gist:
> <https://gist.github.com/ferdisn/19d4d8d697d12f3c1bcc2787483b3b67>
>
> Has anyone found / seen this before? I've tried:
>
> 1. -Xmx1024m -XX:MaxPermSize=256m
> 2. -Xmx2048m -XX:MaxPermSize=512m
> 3. Change Surefire to 2.22
>
> My computer has 16 GB RAM, and plenty of space available during the run.
>