Benchmark crashes on Java 8 EA

Aleksey Shipilev aleksey.shipilev at oracle.com
Tue Feb 25 00:05:11 PST 2014


Ok, thanks. I need the steps to reproduce then :)

-Aleksey.

On 02/24/2014 02:09 PM, Chris Vest wrote:
> It runs just fine if I use -f 0.
> 
> Cheers,
> Chris
> 
> On 24 Feb 2014, at 09:35, Aleksey Shipilev <aleksey.shipilev at oracle.com
> <mailto:aleksey.shipilev at oracle.com>> wrote:
> 
>> The exception you see is the JMH infrastructural exception which can
>> float up when host VM figures the forked VM had broken the connection.
>> It then also figures the forked VM exited with non-zero exit code.
>> Hence, it means the forked VM had failed in some weird way, quite
>> possibly because of the workload you are having.
>>
>> Can you try the run with -f 0?
>>
>> -Aleksey.
>>
>> On 02/24/2014 12:17 PM, Chris Vest wrote:
>>> The project I’m benchmarking builds and run its tests in Java 8 without
>>> any problems. It doesn’t do any IO in the process, though.
>>>
>>> There is no hs_err* file. There is an empty jmh.out file.
>>>
>>> Cheers,
>>> Chris
>>>
>>> On 24 Feb 2014, at 07:28, Aleksey Shipilev
>>> <aleksey.shipilev at oracle.com <mailto:aleksey.shipilev at oracle.com>
>>> <mailto:aleksey.shipilev at oracle.com>> wrote:
>>>
>>>> On 02/24/2014 02:40 AM, Chris Vest wrote:
>>>>> # Benchmark:
>>>>> objectpoolbenchmark.suite.ClaimRelease.StormpotBlazePool.cycle
>>>>> # Warmup Iteration   1: Exception in thread "Thread-3"
>>>>> java.lang.IllegalStateException: java.io.EOFException
>>>>> at
>>>>> org.openjdk.jmh.link.BinaryLinkServer$Handler.run(BinaryLinkServer.java:283)
>>>>> Caused by: java.io.EOFException
>>>>> at
>>>>> java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2601)
>>>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1319)
>>>>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
>>>>> at
>>>>> org.openjdk.jmh.link.BinaryLinkServer$Handler.run(BinaryLinkServer.java:260)
>>>>> <forked VM failed with exit code 132>
>>>>
>>>> Why do you think this is JMH-related?
>>>>
>>>> Your forked VM crashed, look for hs_err*.log.
>>>>
>>>> -Aleksey.
>>>>
>>>
>>
> 



More information about the jmh-dev mailing list