Support Article
Excption when deploying prgateway.war as application
SA-11840
Summary
Error stacktrace started to occur after deploying prgateway.war. The PRPC Application has been deployed in EAR file format on WebLogic Application Server. Despite the errors, the applications appears to be functional.
Error Messages
SEVERE: Error initializing TrustStore:- null/WEB-INF/lib/prgateway.jks (No such file or directory)
java.io.FileNotFoundException: null/WEB-INF/lib/prgateway.jks (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:146)
at com.pega.pegarules.gateway.web.PRGatewayConfiguration.initializeTrustStore(PRGatewayConfiguration.java:704)
at com.pega.pegarules.gateway.web.PRGatewayConfiguration.initialize(PRGatewayConfiguration.java:136)
at com.pega.pegarules.gateway.web.PRGatewayServlet.init(PRGatewayServlet.java:84)
at javax.servlet.GenericServlet.init(GenericServlet.java:240)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:337)
Steps to Reproduce
- Deploy prgateway.war on WebLogic Application Server. The same server must already have PRPC application deployed in EAR format.
Root Cause
The root cause of this problem is a defect in the deployment descriptor ejb-jar.xml.
Resolution
Modify the ejb-jar.xml in PRPC Application EAR and redeploy the application as documented in the below PDN article:
https://pdn.pega.com/support-articles/peganbam-oom-restarts-invoke-node-id-not-found-in-request
Published July 16, 2015 - 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.