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

PegaCall and Avaya libraries are lost after restart



The PegaCall engine and Avaya jtapi sdk libraries disappear once we the JBoss application server restarts. The PegaCALL Engine version information does not appear in the PegaCall landing page and softphone does not work. The system doesn't find the related PegaCALL related classes.

Error Messages

2015-04-22 07:54:23,705 [ttp-/a.a.a.a:8543-12] [ STANDARD] [ ] [ AAAAAAAA:01.16.01] (ngineinterface.service.HttpAPI) ERROR| SW21CV - PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
Caused by: java.lang.NoClassDefFoundError: com/pega/pegacti/core/SessionManager
at com.pegarules.generated.activity.ra_action_getsharedsessionidbyname_be023e92cba12ad19e8cdaacd671951d.step1_circum0(
at com.pegarules.generated.activity.ra_action_getsharedsessionidbyname_be023e92cba12ad19e8cdaacd671951d.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at java.lang.ClassLoader.loadClass(

JBoss Application Server log:
07:39:10,295 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 50) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener( 
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(

Steps to Reproduce

Restart the JBoss  application server of Pega CPM application.

Root Cause

When JBoss Application Server restarts, the system replaces all the 3rd party jar files in /tmp/extractedFiles/apploader/ directory.
To do so it, the server must connect to the database to retrieve the latest version of the jar and put it into the apploader directory.

Based on the error in the log file, occasionally there are database connection issue which prevents the download and causes the reported issue.


To resolve the issue, increase the Database connection timeout value and increae the Database connection pool size.

Published June 29, 2015 - Updated December 2, 2021

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