Question
Onstar
US
Last activity: 1 Aug 2017 11:21 EDT
Pega on Pivotal Cloud Foundry
Hello
I am trying to deploy prweb.war in the Pivotal Cloud Foundry on Tomcat. I specified the database connection attributes in the prbootstrap.properties but at startup I see this error:
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRMiniLoader 19830421 Will load phase 2 bootstrap from Pega-EngineCode:
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT /home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/lib/boot/prbootphase2.jar (No such file or directory)
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT ============ PegaRULES Bootstrap Configuration ============
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Date: Wed May 10 14:58:33 UTC 2017
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Java Version: Oracle Corporation 1.8.0_111
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Configuration: file:/home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/classes/prbootstrap.properties
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Pega-EngineCode:
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Unable to locate classes on filesystem
Hello
I am trying to deploy prweb.war in the Pivotal Cloud Foundry on Tomcat. I specified the database connection attributes in the prbootstrap.properties but at startup I see this error:
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRMiniLoader 19830421 Will load phase 2 bootstrap from Pega-EngineCode:
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT /home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/lib/boot/prbootphase2.jar (No such file or directory)
2017-05-10T10:58:33.34-0400 [APP/PROC/WEB/0] OUT Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT ============ PegaRULES Bootstrap Configuration ============
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Date: Wed May 10 14:58:33 UTC 2017
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Java Version: Oracle Corporation 1.8.0_111
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Configuration: file:/home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/classes/prbootstrap.properties
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Pega-EngineCode:
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT Unable to locate classes on filesystem
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] OUT =============== End Bootstrap Configuration ===============
2017-05-10T10:58:33.35-0400 [APP/PROC/WEB/0] ERR Unable to load phase 2 bootstrap class: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
I set it up to connect to the existing Pega deployment. I can see that it connects to database, but fails to download prbootstrapphase2.jar.
What configuration am I missing? Any help is appreciated.
Below is how the DB connection attributes are setup in the prbootstrap.properties:
com.pega.pegarules.bootstrap.allclasses.dbcpsource=pcf.oracle
pcf.oracle.url=jdbc:oracle:thin:<XXXXXXX>
pcf.oracle.username=<XXXXXXX>
pcf.oracle.password=<XXXXXXX>
oracle.jdbc.class=oracle.jdbc.OracleDriver
com.pega.pegarules.bootstrap.allclasses.schema=RULES
com.pega.pegarules.bootstrap.datatables.schema=DATA
***Updated by moderator: Lochan to update Categories; add SR details ***
***Updated by moderator: Brendan to replace some details with generic placeholders***
Accepted Solution
Pegasystems Inc.
IN
Hi Abdul,
I took a look into the SR and the root cause of the issue was that the running of Pega on PCF using 'cf push...' is not supported for Pega 7.2.1
The use case has been put forward to the Pega Product Management team for review and if approved, inclusion in furture product releases.
Hope this helps!
Pegasystems Inc.
US
I assume you are not using pega PCF tile (which is in beta and only available for upcoming pega 7.3+) instead simply using PCF infrastructure to deploy pega, can you elaborate more on that? What pega version are you running? The log suggests that your rule base may not even be loaded, can you double check on that. Also wondering why you have to change prbootstrap.properties manually, which is not normal. You database info should be specified in tomcat context.xml normally.
Onstar
US
Kevin
I use PCF CLI command to deploy the prweb.war. The Pega version is 7.2.1. In this PCF installation the JNDI and Tomcat configuration facility is restricted, so I am not able to use context.xml. In the OOB prbootstrap.properties it uses JNDI, so I had to change that to explicitly specify the DB connection parameters. I am not sure how to tell if rule base is loaded, below are the log messages before the error:
Kevin
I use PCF CLI command to deploy the prweb.war. The Pega version is 7.2.1. In this PCF installation the JNDI and Tomcat configuration facility is restricted, so I am not able to use context.xml. In the OOB prbootstrap.properties it uses JNDI, so I had to change that to explicitly specify the DB connection parameters. I am not sure how to tell if rule base is loaded, below are the log messages before the error:
2017-05-11T08:47:26.06-0400 [APP/PROC/WEB/0] OUT [CONTAINER] org.apache.catalina.core.StandardEngine INFO Starting Servlet Engine: Apache Tomcat/8.0.38
2017-05-11T08:47:26.55-0400 [APP/PROC/WEB/0] OUT [CONTAINER] rg.apache.tomcat.dbcp.dbcp2.BasicDataSourceFactory INFO Name = AdminPegaRULES Ignoring unknown property: value of "PegaRULES Admin datasource" for "description" property
2017-05-11T08:47:26.59-0400 [APP/PROC/WEB/0] OUT [CONTAINER] org.apache.jasper.servlet.TldScanner INFO At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were
scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] pegarules.internal.bootstrap.PRBootstrapDataSource 19830421 Loading bootstrap properties from /prbootstrap.properties
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] ega.pegarules.internal.bootstrap.SettingReaderJNDI 19830421 Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] ega.pegarules.internal.bootstrap.SettingReaderJNDI 19830421 Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] pegarules.internal.bootstrap.PRBootstrapDataSource 19830421 Bootstrap datatables schema: DATA
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] pegarules.internal.bootstrap.PRBootstrapDataSource 19830421 Archive version [0]
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421 Engine schema defined in allclasses: RULES
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421 Engine classes schema: RULES
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421 Assembled classes schema: RULES
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421 prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421 PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: null
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRMiniLoader 19830421 Will load phase 2 bootstrap from Pega-EngineCode:
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT /home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/lib/boot/prbootphase2.jar (No such file or directory)
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT [CONTAINER] com.pega.pegarules.internal.bootstrap.PRBootstrap 19830421
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT ============ PegaRULES Bootstrap Configuration ============
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT Date: Thu May 11 12:47:26 UTC 2017
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT Java Version: Oracle Corporation 1.8.0_111
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT Configuration: file:/home/vcap/app/.java-buildpack/tomcat/webapps/ROOT/WEB-INF/classes/prbootstrap.properties
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT Pega-EngineCode:
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT (!) Unable to locate classes on filesystem
2017-05-11T08:47:26.64-0400 [APP/PROC/WEB/0] OUT =============== End Bootstrap Configuration ===============
2017-05-11T08:47:26.65-0400 [APP/PROC/WEB/0] ERR Unable to load phase 2 bootstrap class: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
Thank you
Vlad
Pegasystems Inc.
US
query select distinct pzcodeset from <rule>.pr_engineclasses; What do you have? Also I am still concerned your ways of changing prboostrap.properties file. If you like, I would like to check in details how you install this on a PCF. Create a SR so that we can help in more details.
Tata Consultancy Services
US
Hi-
Have you added any database as service to your prweb app? If yes then which database service? If you are going with service broker for SQL server then you need to make sure that base rule load is done at database end. I am trying to deploy same prweb but with free account on PCF , I do not see sql server as service. So, stuck with next step. To deploy pega on PCF, we will have to make sure that database is loaded with base rules successfully and proper connectivity configuration between app(prweb) and database .
Pegasystems Inc.
US
"Unable to locate classes on filesystem"
Some things to check:
- path issue?
- file permissions issue?
- file(s) exist?
You may want to consult your friendly local SysAdmin as well.
Pegasystems Inc.
IN
Hi Vlad,
Please share the SR number here if you end up creating one. We will tag that to your post above and continue to track it.
Thank you,
Onstar
US
Lochana
The only SR types available in the support portal are defect, hotfix, and media. None of them seems to match the nature of my request. I am not sure how to proceed at this point. Your help is appreciated.
Thank you
Vlad
Pegasystems Inc.
IN
Hi Vlad,
I believe defect SR type is the most suitable for this issue as you are seeing an error. Please mention this URL of this post in the details.
Regards,
Accepted Solution
Pegasystems Inc.
IN
Hi Abdul,
I took a look into the SR and the root cause of the issue was that the running of Pega on PCF using 'cf push...' is not supported for Pega 7.2.1
The use case has been put forward to the Pega Product Management team for review and if approved, inclusion in furture product releases.
Hope this helps!