Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

NoClassDefFoundError for BouncyCastleProvider during Start-Up

SA-8962

Summary



User performed cloning and experienced the below issues:
  • Unable to bring up Pega 7 system
  • Unable to reindex

Error Messages



 PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Problem during method invocation (doStartup)
java.lang.NoClassDefFoundError: org.bouncycastle.jce.provider.BouncyCastleProvider
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:94)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:171)
at com.pega.pegarules.exec.internal.PRExecProviderImpl.getCrypto(PRExecProviderImpl.java:383)
at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.<clinit>(ParUtilsImpl.java:159)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:237)
at com.pega.pegarules.deploy.internal.PRDeployProviderImpl.getParUtils(PRDeployProviderImpl.java:96)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:506)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)



Steps to Reproduce



Start the Server

Root Cause



BouncyCastleProvider class is a JAR file that needs to be extracted from DB to drive in extractedFiles folder. Unable to locate the io.tmpdir or the default tmp directory did not have write permission.

Reindexing does not work as it was a cloned system and contained old node ID for indexing in DSS.

Resolution



Issue was resolved through the following Local-change:

NoClassDefFoundError: org.bouncycastle.jce.provider.BouncyCastleProvider was resolved by adding below line to prbootstrap.properties file:


    
com.pega.pegarules.bootstrap.tempdir=/absolutePath

Reindexing issue is resolved by mapping indexing/hostid DSS to pxProcess > pxSystemNodeID.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us