Why is the JRockit JVM slower when Oracle WebLogic Server is running in development mode?
When WebLogic Server is started in development mode, the JRockit JVM is by default started with the -Xdebug option. This makes the JRockit JVM run with some overhead. Sometimes, when running the JRockit JVM, I encounter a NotAvailableException when the console tries to connect to JRockit or if the program itself tries to access the CPU load counters. Occasionally, the process counter does not initialize. This happens only on Windows installations where either the security settings are such that the Performance Data Helper (PDH; a Windows API that reads performance metrics from the operating system) process counter can’t be read or where, for reasons unknown, the PDH process counter is simply turned off. This will deny you the rights to look at the process counter and throw the error. You will receive this message: [JRockit] WARNING: Could not initialize the virtualbytes counter, some functionality in jrockit.management.Memory will not be available. Message was: failed to create counter
