Question

7
Replies
213
Views
GladsonS3738 Member since 2017 9 posts
Commonwealth Bank of Australia
Posted: 3 years ago
Last activity: 3 years 1 month ago
Closed
Solved

Pega client unable to connect to Pega-Ignite server

Hi,

I have spinned up 3 ignite docker containers in server mode connecting to DATA SCHEMA. When I start my pega application (separate docker container) with reference to ignite server in prconfig.xml, but neither the application starts up nor do I see any errors in the logs. When I remove the ignite reference from prconfig.xml in pega client, the application starts up successfully. Below are the config details

Ignite prconfig.xml

<?xml version="1.0" encoding="UTF-8"?>

<pegarules>
<!-- This is a minimum format prconfig.xml file. Only the settings which are required to access settings in the database are included.
All other settings which were formerly located only in this file are now Data-Admin-System-Settings. -->
<env name="initialization/settingsource" value="merged" />
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="security/urlaccesslog" value="NORMAL" />
<env name="security/urlaccessmode" value="WARN" />
<env name="identification/cluster/protocol" value="ignite" />
<env name="identification/cluster/public/address" value="public ip address xxxxxxx"/>

</pegarules>

Pega client prconfig.xml

<?xml version="1.0" encoding="UTF-8"?>
<pegarules>
<!-- This is a minimum format prconfig.xml file. Only the settings which are required to access settings in the database are included.
All other settings which were formerly located only in this file are now Data-Admin-System-Settings. -->
<env name="initialization/settingsource" value="merged" />
<env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>
<env name="agent/threadpoolsize" value="5" />
<env name="security/urlaccesslog" value="NORMAL" />
<env name="security/urlaccessmode" value="WARN" />
<!-- IGNITE -->
<env name="cluster/clientserver/clientmode" value="true" />
<env name="identification/cluster/protocol" value="ignite" />
<!-- IGNITE -->
</pegarules>

Log file:

Below is the log , there is no activity after loading Pega bootstrap configuration

01-Aug-2017 12:51:11.517 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: CEP_OUTBOUND_BR_DATA_OWNER
01-Aug-2017 12:51:12.397 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0 ]
01-Aug-2017 12:51:12.397 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null
01-Aug-2017 12:51:12.397 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: CEP_OUTBOUND_BR_RULES_OWNER
01-Aug-2017 12:51:12.397 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: CEP_OUTBOUND_BR_RULES_OWNER
01-Aug-2017 12:51:12.398 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings
01-Aug-2017 12:51:12.460 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 07-10-31). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.
01-Aug-2017 12:51:12.462 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:07-10-31
01-Aug-2017 12:51:12.788 INFO [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl. Using PRAppLoader implementation class: com.pega.pegarules.bootstrap.loader.PRAppLoader
01-Aug-2017 12:54:36.677 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl. PegaRULES signed jar files will be extracted to: /opt/apache-tomcat-8.5.11/work/Catalina/localhost/prweb/extractedFiles
01-Aug-2017 12:54:47.048 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl. PegaRULES classes will be loaded from the database
01-Aug-2017 12:54:47.909 1050 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap.
============ PegaRULES Bootstrap Configuration ============
Date: Tue Aug 01 12:54:47 AEST 2017
Java Version: Oracle Corporation 1.8.0_60
Configuration: file:/opt/apache-tomcat-8.5.11/webapps/prweb/WEB-INF/classes/prbootstrap.properties
Pega-EngineCode: 07-10-31
ASM Version: 762781845
Database: Oracle Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
Driver: Oracle JDBC driver 12.1.0.1.0
Active CodeSets: pega-enginecode:07-10-31 at (latest patch)
customer:06-01-01 at (latest patch)
=============== End Bootstrap Configuration ===============

DevOps Low-Code App Development Installation and Deployment SR Created
Moderation Team has archived post
Share this page LinkedIn