Support Article
Exception during startup processing when Introscope is present
SA-46755
Summary
Users see an error when trying to start WebSphere Application Server 8.5.5, Java 1.7 running Pega 7.3, and the engine does not initialize.
Error Messages
2017-10-30 20:05:25,014 [ server.startup : 0] [ ] [ ] [ ] (ervlet.WebAppLifeCycleListener) ERROR - Exception during startup processing
com.ibm.ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (doStartup)
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:257) ~[prbootstrap-api-7.3.0-77.jar:7.3.0-77]
Caused by: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.ensureError(J9VMInternals.java:134) ~[?:1.7.0]
at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:123) ~[?:1.7.0]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:398) ~[prprivate.jar:?]
Caused by: java.lang.RuntimeException: Unable to initialize provider Execution
at com.pega.pegarules.common.PREngineProvider.<clinit>(PREngineProvider.java:192) ~[?:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:398) ~[prprivate.jar:?]
Caused by: java.lang.VerifyError: JVMVRFY012 stack shape inconsistent; class=com/pega/pegarules/exec/internal/util/collections/StringPoolImpl, method=<init>()V, pc=22
at com.pega.pegarules.exec.internal.PRExecProviderImpl.getStringPool(PRExecProviderImpl.java:447) ~[prprivate.jar:?]
Steps to Reproduce
Run Pega 7.3 on WebSphere Application Server 8.5.5 with Wily Introscope.
Root Cause
A defect or configuration issue in the operating environment
Stack shape error is due to Introscope tool running in this environment.
Resolution
Perform one of the following local-changes:
Deactivate Introscope and restart the JVM.
If Introscope is your primary monitoring tool and disabling it is not feasible, then take this alternative approach:
- Stop the application server.
- Open the AGENT_HOME/core/config/IntroscopeAgent.profile and specify this setting:
introscope.autoprobe.constructor.policy=Partial introscope.autoprobe.constructor.instrumentation.affected.vendors=Oracle,SAP,IBM - Start the application server.
Published May 4, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.