Slowness or failure in startup of "authoring image"("business-central" or "decision-central") in OpenShift

Issue

• I had deployed PAM 7.8.1 on OCP using Business Automation Operator. I have been able to create 3 projects but now Business Central Pod keeps Crashing and restarting. I am not sure why Readiness probe is failing
• After starting up Process Automation Manager authoring image in OpenShift, we see a lot indexing logs then the pod gets killed as shown in below log snippet:

09:35:07,316 INFO  [org.uberfire.ext.metadata.io.IndexerDispatcher] (Thread-146) Completed indexing 1 events for indexer [id=org.drools.workbench.screens.guided.dtable.backend.server.indexing.GuidedDecisionTableFileIndexer] in cluster [KClusterImpl [clusterId=pam-poc/RHPAMQuickstart/junit-tests]].
09:35:07,334 INFO  [org.uberfire.ext.metadata.io.IndexerDispatcher] (Thread-165) Completed indexing 1 events for indexer [id=org.kie.workbench.common.stunner.bpmn.project.backend.indexing.BpmnFileIndexer] in cluster [KClusterImpl [clusterId=pam-poc/RHPAMQuickstart/master]].
09:35:07,335 INFO  [org.uberfire.ext.metadata.io.IndexerDispatcher] (Thread-153) Completed indexing 1 events for indexer [id=org.kie.workbench.common.stunner.bpmn.project.backend.indexing.BpmnFileIndexer] in cluster [KClusterImpl [clusterId=MySpace/Mortgage_Process/master]].
09:35:07,358 INFO  [org.uberfire.ext.metadata.io.IndexerDispatcher] (Thread-148) Completed indexing 1 events for indexer [id=org.drools.workbench.screens.guided.dtable.backend.server.indexing.GuidedDecisionTableFileIndexer] in cluster [KClusterImpl [clusterId=MySpace/Mortgage_Process/master]].
09:35:07,431 INFO  [org.uberfire.ext.metadata.io.IndexerDispatcher] (Thread-156) Completed indexing 3 events for indexer [id=org.kie.workbench.common.screens.datamodeller.backend.server.indexing.JavaFileIndexer] in cluster [KClusterImpl [clusterId=pam-poc/RHPAMQuickstart/master]].
*** JBossAS process (996) received KILL signal ***