Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

NotSerializableException in logs PRPC 7.1.6 JBoss 6.1 EAP

SA-1294

Summary



PRPC 7.1.6 fails to start on JBoss 6.1 EAP server.

Error Messages


 
16:50:05,289 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (ServerService Thread Pool -- 73) ISPN000136: Execution error: org.infinispan.marshall.NotSerializableException: org.jboss.as.clustering.registry.RegistryService$1
Caused by: an exception which occurred:
in object [email protected]
in object [email protected]
in object [email protected]

16:50:05,289 ERROR [org.infinispan.transaction.TransactionCoordinator] (ServerService Thread Pool -- 73) ISPN000188: Error while processing a commit in a two-phase transaction: org.infinispan.marshall.NotSerializableException: org.jboss.as.clustering.registry.RegistryService$1
Caused by: an exception which occurred:
in object [email protected]
in object [email protected]
in object [email protected]

16:50:05,290 ERROR [org.infinispan.transaction.tm.DummyTransaction] (ServerService Thread Pool -- 73) ISPN000111: afterCompletion() failed for SynchronizationAdapter{localTransaction=LocalTransaction{remoteLockedNodes=null, isMarkedForRollback=false, lockedKeys=null, backupKeyLocks=null, topologyId=-1, isFromStateTransfer=false} [email protected]3} or[email protected]22: org.infinispan.CacheException: Could not commit.
at org.infinispan.transaction.synchronization.SynchronizationAdapter.afterCompletion(SynchronizationAdapter.java:83)
at org.infinispan.transaction.tm.DummyTransaction.notifyAfterCompletion(DummyTransaction.java:285)
at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:334)
at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:91)
at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:102)
at org.infinispan.batch.BatchContainer.resolveTransaction(BatchContainer.java:123)
at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:105)
at org.infinispan.batch.BatchContainer.endBatch(BatchContainer.java:86)
at org.infinispan.CacheImpl.endBatch(CacheImpl.java:684)
at org.infinispan.AbstractDelegatingCache.endBatch(AbstractDelegatingCache.java:80)
at org.jboss.as.clustering.infinispan.invoker.BatchCacheInvoker.invoke(BatchCacheInvoker.java:53)
at org.jboss.as.clustering.registry.RegistryService.refreshLocalEntry(RegistryService.java:140)
at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.start(DistributedCacheManager.java:121)
at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:174) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:452) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:283) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:201) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:354) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:153) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:194) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3717) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: javax.transaction.xa.XAException
at org.infinispan.transaction.TransactionCoordinator.handleCommitFailure(TransactionCoordinator.java:224)
at org.infinispan.transaction.TransactionCoordinator.commit(TransactionCoordinator.java:185)
at org.infinispan.transaction.synchronization.SynchronizationAdapter.afterCompletion(SynchronizationAdapter.java:81)
... 31 more

Steps to Reproduce


Not Applicable


Root Cause



The serializer.jar file is present in the PR_ENGINECLASSES table in the PRPC schema. To resolve the issue, the serializer.jar file in the PRPC schema has to be suppressed since JBoss also loads the serializer.jar file from its implicit modules. 

Resolution



Follow these steps to resolve the problem:

Step 1: Shut down the JBoss application server.

Step 2: Connect to PRPC Database schema and execute the following statements to update 'PR_ENGINECLASSES' table, so that the serializer.jar file present in the PRPC schema does not get loaded.
 
----> By executing this query, you should see the result of pzcodeset value appearing as 'pega-enginecode' for serializer jar file.
select pzcodeset from <YOUR_SCHEMA_NAME>.pr_engineclasses where pzjar like '%serializer%'; 

---->Execute following query to update the pzcodeset value to 'pega-enginecodenouse'.
update <YOUR_SCHEMA_NAME>.pr_engineclasses set pzcodeset='pega-enginecodenouse' where pzjar like '%serializer%';
commit; 
 
Above statement was executed so that serializer.jar file present in PRPC schema does not get loaded.
---->Execute the following query to confirm the pzcodeset value is set to 'pega-enginecodenouse'.
 select pzcodeset from <YOUR_SCHEMA_NAME>.pr_engineclasses where pzjar like '%serializer%'; 

Step 3: Delete the PegaRULES_Extract_Marker.txt file from the Pega temporary directory.
  
Step 4: Restart the server.

 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us