WebLogic Server Hangs When Configuring JRMC -XManagement and Post Bind UID
Last updated on NOVEMBER 05, 2016
Applies to:Oracle JRockit - Version R28 to R28.1.1 [Release JRockit]
Oracle Weblogic Server - Version 10.3.3 and later
Information in this document applies to any platform.
WebLogic Server (WLS) hangs on JRockit R28 when:
- Configured WebLogic JVM to remote Monitoring with: -Xmanagement
- Run the process as root And post bind to a non root user (wl configuration).
The server is stuck in starting state.
The process was started by running startWebLogic.sh as root. Note that with post bind, the process will be bound to the post-binded user (normal user).
With this configuration, the server does not start. If you remove the jrockit option the server starts properly.
WLS logs show no errors.
Thread dumps show main thread hanging forever, as seen on this stack trace:
"Main Thread" id=1 idx=0x4 tid=18453 prio=5 alive, in native
at oracle/jrockit/jfr/VMJFR.start(Z)V(Native Method)
^-- Holding lock: java/lang/Object@0xe0ac6660[biased lock]
at com/oracle/jrockit/jfr/client /FlightRecordingClient.start(FlightRecordingClient.java:225)
at weblogic/diagnostics/image /JRockitFlightRecorderSource.startRecording(JRockit FlightRecorderSource.java:218)
The -Xmanagement option was added to the JAVA_OPTIONS, AND WebLogic Server was configured to post bind to another user when the process starts.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms