Frequently Asked Questions (FAQs)

5 Frequently Asked Questions (FAQs)

This section consists of resolutions to the frequently asked questions noticed during the Compliance Studio Installation.

What should I do if the data pipelines are failing with the following error?

09/Jun/2022 10:48:32,978- ImportDAOImpl: Exception in import processor
org.springframework.web.client.ResourceAccessException: I/O error on
POST request for "https://<LOAD_BALANCER_HOSTNAME>:18004/
datapipelineservice/MAP/IMPORT": PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target; nested exception is
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
at
org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:
748) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
at
org.springframework.web.client.RestTemplate.execute(RestTemplate.java:67
4) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
at
org.springframework.web.client.RestTemplate.postForObject(RestTemplate.j
ava:418) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
at
com.oracle.fccm.amlxe.pipelineService.client.RESTClient.callRESTService(
RESTClient.java:107) ~[class]

To resolve this issue, ensure that the pem format of the studio_server certificate is referred to in the frontend configuration in the load balancer configuration.

For example,

frontend datapipeline_service
bind *:18006 ssl crt /etc/ssl/certs/haproxy.pem
mode http
default_backend datapipeline_service

Here, haproxy.pem is the pem format of the studio_server.p12 file that is available in the / etc/ssl/certs/path.

What should I do if Compliance Studio server fails with the below error in metaservice.log when switching from one server to another?

26-03-2024 08:35:26.942 [ main] ERROR
ofss.fccm.applicationserver.server.GrizzlyServer - Server failed to
start liquibase.exception.ValidationFailedException: Validation Failed:
1 change sets check sum model/datamodel/
fccstudio_Atomic_Schema_8121.xml::FCC_DATASTUDIO_CONFIG_8121::Compliance
Studio 8.1.2.1 was: 8:34bcb65a5125e53bd31acbc46a504d04 but is now:
8:c52d8dba1a04bcd378a9744484ab01be at
liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:29
6) ~[liquibase-core-4.8.0.jar:?]

To resolve this issue, before switching the Compliance Studio instance from one server to another delete the record returned by the following query:

select * from DATABASECHANGELOG where author = 'Compliance Studio 8.1.2.1' and id = 'FCC_DATASTUDIO_CONFIG_8121';

What should I do if PGX fails to start/restart and displays the below error in the pgx- server.log?

22-05-2024 08:48:33 ERROR o.p.r.PgxContextListener - Exception while
initializing PGX webapp
java.util.concurrent.ExecutionException:
java.lang.IllegalArgumentException: javax.net.ssl.SSLHandshakeException:
No name matching <PGX_SERVER_HOSTNAME> found
at java.base/
java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:
395)
at java.base/
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
at oracle.pgx.api.PgxFuture.get(PgxFuture.java:113)
at
oracle.pgx.rest.PgxContextListener.contextInitialized(PgxContextListener
.java:64)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.j
ava:4462)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.j
ava:4914)
at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:171)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.jav
a:1332)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.jav
a:1322)
at java.base/
java.util.concurrent.FutureTask.run(FutureTask.java:264)

.. .. ..
Caused by: java.lang.IllegalArgumentException:
javax.net.ssl.SSLHandshakeException: No name matching
<PGX_SERVER_HOSTNAME> found
at oracle.pgx.engine.admin.Ctrl.preloadGraphs(Ctrl.java:355)
at oracle.pgx.engine.admin.Ctrl.access$1600(Ctrl.java:97)
at oracle.pgx.engine.admin.Ctrl$1.call(Ctrl.java:248)
at oracle.pgx.engine.admin.Ctrl$1.call(Ctrl.java:186)
at
oracle.pgx.api.admin.internal.AbstractControl.runOnCallerThread(Abstract
Control.java:45)
at oracle.pgx.engine.admin.Ctrl.start(Ctrl.java:186)
at
oracle.pgx.api.admin.internal.AbstractControl.start(AbstractControl.java
:115)
at
oracle.pgx.api.admin.internal.AbstractControl.lambda$start$5(AbstractCon
trol.java:101)
at java.base/
java.util.function.Function.lambda$andThen$1(Function.java:88)
at java.base/
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture
.java:1106)
at java.base/
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.jav
a:2235)
at oracle.pgx.api.PgxFuture.thenCompose(PgxFuture.java:178)
at
oracle.pgx.api.admin.internal.AbstractControl.start(AbstractControl.java
:101)
at
oracle.pgx.api.admin.internal.AbstractControl.lambda$start$1(AbstractCon
trol.java:79)
at java.base/
java.util.function.Function.lambda$andThen$1(Function.java:88)
at java.base/
java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture
.java:1106)
at java.base/
java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.jav
a:2235)
at oracle.pgx.api.PgxFuture.thenCompose(PgxFuture.java:178)
at
oracle.pgx.api.admin.internal.AbstractControl.start(AbstractControl.java
:67)
at
oracle.pgx.rest.PgxContextListener.contextInitialized(PgxContextListener
.java:62)
... 26 common frames omitted

This happens due to graph was loaded with IN-MEMORY mode which is not supported in a HA PGX configuration.

To clean up the IN-MEMORY graph and reload it in OFFLOADED mode, follow these steps:

Truncate the records from FCC_PGX_M_CONFIG, FCC_GRAPH_M_DATA_SOURCES and FCC_GRAPH_M_CONFIG_JSON tables.
Start the PGX server.
Run the Refresh Graph task with graph type as OFFLOADED.