Support Article
Push functionality behavior incorrect post upgrade to Pega 7.4
SA-59728
Summary
Push functionality starts incorrectly and terminates the application post upgrade to Pega 7.4.
Error Messages
14:09:31,289 INFO [org.jboss.jca.core.api.connectionmanager.ccm.CachedConnectionManager] (WEBK106) IJ000100: Closing a connection for you. Please close them yourself:com.pega.pegarules.ra.cci.PRConnectionImpl@43c7615c: java.lang.Throwable: STACKTRACE at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.registerConnection(14:09:31,289 ERROR [org.jboss.msc.service.fail] (WEBK106) MSC000001: Failed to start service jboss.web.deployment.default-host./prweb: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./prweb: java.lang.RuntimeException: java.lang.RuntimeException: javax.resource.ResourceException: IJ000151: Some connections were not closed, see the log for the allocation stacktraces at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:99) [jboss-as-web-7.5.20.Final-redhat-1.jar:7.5.20.Final-redhat-1] Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000151: Some connections were not closed, see the log for the allocation stacktraces at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown(CachedConnectionManagerSetupProcessor.java:113) at org.jboss.as.web.ThreadSetupBindingListener.unbind(ThreadSetupBindingListener.java:61) [jboss-as-web-7.5.20.Final-redhat-1.jar:7.5.20.Final-redhat-1]... 11 more Caused by: javax.resource.ResourceException: IJ000151: Some connections were not closed, see the log for the allocation stacktraces"}} 14:09:31,382 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) JBAS015859: Deployed "prsysmgmt_jboss.ear" (runtime-name : "prsysmgmt_jboss.ear") 14:09:31,382 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) JBAS015859: Deployed "prpc_j2ee14_jboss61JBM.ear" (runtime-name : "prpc_j2ee14_jboss61JBM.ear") 14:09:31,461 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.20.GA (AS 7.5.20.Final-redhat-1) started (with errors) in 228793ms - Started 953 of 971 services (3 services failed or missing dependencies, 70 services are lazy, passive or on-demand) 14:09:31,289 INFO [org.jboss.jca.core.api.connectionmanager.ccm.CachedConnectionManager] (WEBK106) IJ000100: Closing a connection for you. Please close them yourself:com.pega.pegarules.ra.cci.PRConnectionImpl@43c7615c: java.lang.Throwable: STACKTRACE at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:99) [jboss-as-web-7.5.20.Final-redhat-1.jar:7.5.20.Final-redhat-1] Caused by: java.lang.RuntimeException: javax.resource.ResourceException: IJ000151: Some connections were not closed, see the log for the allocation stacktraces at org.jboss.as.web.ThreadSetupBindingListener.unbind(ThreadSetupBindingListener.java:61) [jboss-as-web-7.5.20.Final-redhat-1.jar:7.5.20.Final-redhat-1]... 11 more Caused by: javax.resource.ResourceException: IJ000151: Some connections were not closed, see the log for the allocation stacktraces"}} 14:09:31,382 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) JBAS015859: Deployed "prsysmgmt_jboss.ear" (runtime-name : "prsysmgmt_jboss.ear") 14:09:31,382 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) JBAS015859: Deployed "prpc_j2ee14_jboss61JBM.ear" (runtime-name : "prpc_j2ee14_jboss61JBM.ear") 14:09:31,461 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.20.GA (AS 7.5.20.Final-redhat-1) started (with errors) in 228793ms - Started 953 of 971 services (3 services failed or missing dependencies, 70 services are lazy, passive or on-demand)
Steps to Reproduce
- Upgrade from Pega 7.3.1 to Pega 7.4
- Start the server
Root Cause
A defect in Pegasystems’ code or rules. RAClientContainer.cleanup does not work when PushSubscriptionCleanerDaemon and PresenceSessionStateTrackerDaemon initialise.
Resolution
Apply HFix-44975.
Published December 4, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.