Strange bug inside jetty at shenandoah/jdk8u

Aleksey Shipilev shade at redhat.com
Thu Dec 14 18:02:14 UTC 2017


On 12/14/2017 06:52 PM, Kirill A. Korinsky wrote:
> Good day!
> 
> I've tried use shenandoah on real application and found strange behaviour.

Thanks for reporting this!

> The application is usual java-http-server (jgroup, spring, jetty, etc) that listen to port and responses to request.
> 
> If remove from arguments all `-D[application settings]` the start command looks like:
>> java -server -Duser.timezone=UTC -XX:-OmitStackTraceInFastThrow -Xmx4096 -Xms4096 -server ${GC_OPTIONS} -Djava.net.preferIPv4Stack=true -Djava.security.auth.login.config=/opt/server/conf/jaas.conf -jar /path/to/shade.jar

Any chance you can whip up a simple reproducer for this? Something like Maven project that produces
a JAR in question.

> I can't run it at shipilev/openjdk:8-shenandoah-fastdebug because JVM crashed without logs

Crashing without logs is weird. Can you run the non-Docker nightly JDK from here?
  https://builds.shipilev.net/openjdk-shenandoah-jdk8/

Our wiki outlines some steps to better dissect this:
  https://wiki.openjdk.java.net/display/shenandoah/Main#Main-FunctionalDiagnostics

Thanks,
-Aleksey




More information about the shenandoah-dev mailing list