Question
Tata Consultancy Services
IN
Last activity: 10 Dec 2017 9:49 EST
Virtualizing using PEGA 7 tomcat ready docker does not work
Hi,
I was trying out the docker virtualization but for some reason it is not working . i am not able to start the prweb component. I have attached the docker logs. Please let me know what i am missing here. Appreciate the earlier response
Tata Consultancy Services
IN
Hi Team,
I have narrowed down my issues, the issue seems to be JDBC connection is not happening successfully but i am very sure jndi name is getting passed correctly. Please assist me on resolving this, thanks in advance.
Catalina logs param logs
Hi Team,
I have narrowed down my issues, the issue seems to be JDBC connection is not happening successfully but i am very sure jndi name is getting passed correctly. Please assist me on resolving this, thanks in advance.
Catalina logs param logs
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdbName=postgres
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdbHostname= Proprietary information hidden
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdbPort=5438
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdbUsername=postgres
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdbPassword=postgres
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcUrl=jdbc:postgresql://10.XX.XX.207:5438/postgres
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcMinActive=50
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcMaxActive=250
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcMinIdle=10
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcMaxIdle=50
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcMaxWait=30000
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcInitialSize=50
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcDriverClass=org.postgresql.Driver
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DjdbcValidationQuery=SELECT 1
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DrulesSchema=pegarules
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -DdataSchema=pegadata
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Didentification.nodeid=0fb4f1ad3083
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dindex.directory=
Dec 01, 2017 5:26:21 PM org.apache.catalina.startup.VersionLoggerListener log
catalina error log
"INFO: Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup
Dec 01, 2017 5:26:31 PM com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource
1050: Bootstrap datatables schema: pegadata
Dec 01, 2017 5:26:32 PM com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource
SEVERE: Unable to connect to database. Will only use properties from file.
org.postgresql.util.PSQLException: ERROR: relation "pegadata.pr_data_admin" does not exist
Position: 34"
More info :
Database: PostgreSQL 9.6.1 (which has pega 7.3.1 running )
Driver: PostgreSQL JDBC Driver 42.1.4.jre7
If database connection is failing for some reason do we have logs stating what is the reason since i dont see any logs specifying the reason
Note : I was able to run a local version of PEGA using the jndi souce specified it ran successfully.
Let me know if any more info is needed. i need this to be resolved at the earliest
AGL Electricity
AU
It looks like you're hitting the database but the pr_data_admin column does not exist.
Have you set up your database correctly? Start reading at page 15 here:
https://docs-previous.pega.com/pega-731-platform-installation-guide-apache-tomcat-and-postgresql
p.s. I'm working on this today, if you've resolved this problem can you upload your dockerfile to github?
Cheers!
Tata Consultancy Services
IN
Hi All,
Yes the database connection was correct but schema mapping is incorrect.
The only configuration i missed was schema names .... Once i changed the schema name it worked correctly. The idea is all the env variables exposed in PEGA7-tomcat-readty docker file should be cross verified with your set up. Thanks for the support