Unable to deploy prweb.war, DB connection issue?

Hi all,

I’m setting up Pega in a VM with CentOS 7, postgreSQL and Tomcat.

I’m having trouble deploying the prweb.war file. Each time I initiate the Tomcat server, it starts the deployment but after short, it gives me this error:

Dec 23, 2022 2:09:43 PM com.pega.pegarules.internal.bootstrap.phase2.jdbc.AbstractJdbcJarReader

SEVERE: Entry could not be loaded from the DB, jar name=[ prprivate-data.jar] package Name [com/pega/pegarules/data/internal/access] class name [PreparedStatementInsert.class], DB connectivity may have been interrupted

After that, a long series of errors follow, but this is the first one to appear.

I’ve tried deployment many times, and always the error seems to be the Entry could not be loaded from the DB and that connectivity fails at some point. Package name and class name change each time, so there’s something stopping the connection. Could it be the firewall? Do anyone know how to check it or what should I do?

Thanks,

Jun

@JunM16668902

Are you trying to setup containerized environment from VM? Because, Tomcat, CentOS image and postgreSQL ones are best in containerized environments. As said, If you’re trying to set up in Conatinerized one, prweb.war files etc… are from On-Prem specifications.

Request you to clarify your requirements so that i can assist you further.

@KishoreSanagapalli

No, I’m not trying to containerize from VM. I had installed pgAdmin 4 and tomcat to work on training projects. I have created a db, installed pega to create the prweb.war file and now being unable to deploy it with tomcat.

@JunM16668902

The combination that you’re trying to use will not work as per my experience. You should use helm charts with pega configurations instead of prweb.war file.

@JunM16668902 We have systems with similar config, can you share the complete logfiles? With just the one error, unable to identify the direct cause.

@JunM16668902 you can verify the DB account/user access or privileges if deploying the WAR file first time with these DB accounts/new DB accounts.

you will get the error if the DB account doesn’t have the correct permission as per the Pega deployment guideline document.

@JunM16668902 Thanks for all the replies. After some digging, it turned out that we were trying the deployment using Tomcat 7 instead of 8 or higher. Using Tomcat 8 resolved the issue!

@JunM16668902

Please mark it as SOLVED.