Question
TATA CONSULTANCY SERVICES
IN
Last activity: 29 Sep 2017 0:46 EDT
What does EXCP0001 ALERT mean in PegaCALL CTI Logs?
What does EXCP0001 ALERT mean in PegaCALL CTI Logs? Have checked in PDN & Support Articles but not able to find any information. Never seen this in 6.X versions. Looks like a new alert/Exception ID introduced as a part of 7.X
Message indicates that connection to both Primary & Secondary CTI Servers failed.
2015-07-24 01:19:00,099 [.PRPCWorkManager : 3] ( com.pega.pegacti) ALERT - 2015-07-24 08:19:00,098 GMT*7*EXCP0001*0*0*3930254ea3658d3d97c69ded
18856614*NA*NA*BAB169042C5DF2E1B0AAA21B842B85571*System*blank*PORTAL:02.60.01*e7bd1e6647dd254d158bb5fd06b4effe*N*1*6528*WorkManager.PRPCWorkManager : 3*STAND
ARD*com.pega.pegacti**ChannelServices-Admin-CTILink.AutoStartLinks*Rule-Obj-Activity:AutoStartLinks*CHANNELSERVICES-SESSION-CTILINK-LOCAL CREATESESSION #2014
0919T172158.053 GMT Step: 3 Circum: 0*NA*NA*ChannelServices-Session-CTILink-Local*TempLocalPage*ChannelServices-Session-CTILink-Local*TempLocalPage*java;RULE
-OBJ-ACTIVITY CHANNELSERVICES-SESSION-CTILINK-LOCAL CREATESESSION #20140919T172158.053 GMT Step: 3 Circum: 0;doActivity Rule-Obj-Activity:CreateSession;call
CreateSession;RULE-OBJ-ACTIVITY CHANNELSERVICES-SESSION-CTILINK-LOCAL OPENSESSION #20140919T172207.629 GMT Step: 5 Circum: 0;12 additional frames in stack;*S
What does EXCP0001 ALERT mean in PegaCALL CTI Logs? Have checked in PDN & Support Articles but not able to find any information. Never seen this in 6.X versions. Looks like a new alert/Exception ID introduced as a part of 7.X
Message indicates that connection to both Primary & Secondary CTI Servers failed.
2015-07-24 01:19:00,099 [.PRPCWorkManager : 3] ( com.pega.pegacti) ALERT - 2015-07-24 08:19:00,098 GMT*7*EXCP0001*0*0*3930254ea3658d3d97c69ded
18856614*NA*NA*BAB169042C5DF2E1B0AAA21B842B85571*System*blank*PORTAL:02.60.01*e7bd1e6647dd254d158bb5fd06b4effe*N*1*6528*WorkManager.PRPCWorkManager : 3*STAND
ARD*com.pega.pegacti**ChannelServices-Admin-CTILink.AutoStartLinks*Rule-Obj-Activity:AutoStartLinks*CHANNELSERVICES-SESSION-CTILINK-LOCAL CREATESESSION #2014
0919T172158.053 GMT Step: 3 Circum: 0*NA*NA*ChannelServices-Session-CTILink-Local*TempLocalPage*ChannelServices-Session-CTILink-Local*TempLocalPage*java;RULE
-OBJ-ACTIVITY CHANNELSERVICES-SESSION-CTILINK-LOCAL CREATESESSION #20140919T172158.053 GMT Step: 3 Circum: 0;doActivity Rule-Obj-Activity:CreateSession;call
CreateSession;RULE-OBJ-ACTIVITY CHANNELSERVICES-SESSION-CTILINK-LOCAL OPENSESSION #20140919T172207.629 GMT Step: 5 Circum: 0;12 additional frames in stack;*S
essionType=ACD;pyTempPlaceHolder=TempPlaceHolder;pxObjClass=;GroupName=CHANNELSERVICES-ADMIN-CTILINK-LOCAL-CISCO WPPLOCAL_CA_PEMBROKE;Dedicated=false;*[MSG][
Failed to open the session. Connection to primary and backup CTIServers failed.][STACK][pega.ChannelServicesException: Failed to open the session. Connection
to primary and backup CTIServers failed.<CR> at com.pega.pegacti.ciscoicm.cti.CiscoCTISession.open(CiscoCTISession.java:376)<CR> at com.pega.pegacti.c
ore.SessionManager.createSession(SessionManager.java:907)<CR> at com.pegarules.generated.activity.ra_action_createsession_d744c23d170d14f55961360d7d2c95a5.
step3_circum0(ra_action_createsession_d744c23d170d14f55961360d7d2c95a5.java:351)<CR> at com.pegarules.generated.activity.ra_action_createsession_d744c23d1
70d14f55961360d7d2c95a5.perform(ra_action_createsession_d744c23d170d14f55961360d7d2c95a5.java:103)<CR> at com.pega.pegarules.session.internal.mgmt.Executabl
e.doActivity(Executable.java:3375)<CR> at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)<CR> at com.pegaru
les.generated.activity.ra_action_opensession_1c768dc1a3e0b383c6de78a998fb429b.step5_circum0(ra_action_opensession_1c768dc1a3e0b383c6de78a998fb429b.java:624)<
CR> at com.pegarules.generated.activity.ra_action_opensession_1c768dc1a3e0b383c6de78a998fb429b.perform(ra_action_opensession_1c768dc1a3e0b383c6de78a998fb
429b.java:137)<CR> at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)<CR> at com.pega.pegarules.session.interna
l.mgmt.Executable.invokeActivity(Executable.java:10450)<CR> at com.pegarules.generated.activity.ra_action_createsession_940c52b9ac1b702b85f969e16ea78040.
step6_circum0(ra_action_createsession_940c52b9ac1b702b85f969e16ea78040.java:550)<CR> at com.pegarules.generated.activity.ra_action_createsession_940c52b9a
c1b702b85f969e16ea78040.perform(ra_action_createsession_940c52b9ac1b702b85f969e16ea78040.java:169)<CR> at com.pega.pegarules.session.internal.mgmt.Executabl
e.doActivity(Executable.java:3375)<CR> at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)<CR> at com.pegaru
les.generated.activity.ra_action_startlink_f6e34b4c1a44b550e94073627ce6e57b.step6_circum0(ra_action_startlink_f6e34b4c1a44b550e94073627ce6e57b.java:664)<CR>-at com.pegarules.generated.activity.ra_action_startlink_f6e34b4c1a44b550e94073627ce6e57b.perform(ra_action_startlink_f6e34b4c1a44b550e94073627ce6e57b.java:17
7)<CR> at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)<CR> at com.pega.pegarules.session.internal.mgmt.Executabl
e.invokeActivity(Executable.java:10450)<CR> at com.pegarules.generated.activity.ra_action_autostartlinks_56f2a579481c57dece476adf0f7a9493.step4_6_circum0
(ra_action_autostartlinks_56f2a579481c57dece476adf0f7a9493.java:956)<CR> at com.pegarules.generated.activity.ra_action_autostartlinks_56f2a579481c57de
ce476adf0f7a9493.step4_0_circum0_ChannelServices_Admin_CTILink(ra_action_autostartlinks_56f2a579481c57dece476adf0f7a9493.java:634)<CR> at com.pegarules.gene
rated.activity.ra_action_autostartlinks_56f2a579481c57dece476adf0f7a9493.perform(ra_action_autostartlinks_56f2a579481c57dece476adf0f7a9493.java:191)<CR> -at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)<CR> at com.pega.pegarules.session.internal.async.agent.QueueProce
ssor.runActivity(QueueProcessor.java:719)<CR> at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:600)<CR> at co
m.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:913)<CR> at com.pega.pegarules.session.internal.PRSessionProviderImpl.
performTargetActionWithLock(PRSessionProviderImpl.java:1177)<CR> at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PR
SessionProviderImpl.java:926)<CR> at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:825)<CR
> at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:646)<CR> at com.pega.pegarules.session.internal.async.
Agent.queueBatchActivityForAgent(Agent.java:1505)<CR> at com.pega.pegarules.session.internal.async.Agent.queueBatchActivityForAgent(Agent.java:1294)<CR> -at com.pega.pegarules.session.internal.async.AgentQueue.run(AgentQueue.java:769)<CR> at com.pega.pegarules.session.internal.async.Agent.runAgentTask(Agent
.java:937)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:220)<CR> at com.pega.p
egarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:166)<CR> at com.pega.pegarules.session.internal.engineinterfac
e.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:315)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEn
gine(EngineImpl.java:263)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225)<CR> at su
n.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)<CR> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)<CR>-at java.lang.reflect.Method.invoke(Method.java:611)<CR> at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:338)<CR> at co
m.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:379)<CR> at com.pega.pegarules.boot.internal.extbridge
.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:216)<CR> at com.pega.pegarules.boot.internal.extbridge.AppServerBridge
ToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:238)<CR> at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBe
anBoot.java:168)<CR> at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)<CR> at com.pega.p
egarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:155)<CR> at com.pega.pegarules.session.internal.engineinterfac
e.etier.asynchbeans.AsyncTask.run(AsyncTask.java:64)<CR> at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(
RunnableWrapper.java:71)<CR> at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:269)<CR> at java.security.AccessController.doPrivilege
d(AccessController.java:298)<CR> at javax.security.auth.Subject.doAs(Subject.java:495)<CR> at com.ibm.websphere.security.auth.WSSubject.doAs(WSS
ubject.java:131)<CR> at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:89)<CR> at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J
2EEContext.java:336)<CR> at java.security.AccessController.doPrivileged(AccessController.java:327)<CR> at com.ibm.ws.asynchbeans.J2EEContext.run(J2E
EContext.java:778)<CR> at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)<CR> at com.ibm.ws.asynchbeans.ABW
orkItemImpl.run(ABWorkItemImpl.java:159)<CR> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1660)<CR>Caused by: pega.ChannelServicesException: C
onnection to primary and backup CTIServers failed.<CR> at com.pega.pegacti.ciscoicm.cti.CiscoCTISession.connect(CiscoCTISession.java:1608)<CR> at com.pega.p
egacti.ciscoicm.cti.CiscoCTISession.open(CiscoCTISession.java:353)<CR> ... 60 more<CR>]*
Accepted Solution
Pegasystems
IN
Pega 7.1.7 introduced the concept of writing exceptions as alerts. Therefore exceptions are written to the alert log as EXCP0001.
This was done to capture additional metadata, which an alert captures, for exceptions. It is also useful if you are using AES or Predictive Diagnostic Cloud to monitor your nodes. AES or PDC can use the metadata to help you identify the issues better.
TATA CONSULTANCY SERVICES
IN
Thanks Rajiv for the explanation. Can you please check if this be documented in PDN/HELP resources ?
Pegasystems
IN
Hi Hari,
This is currently not documented and the documentation team has been notified about the same. They should be updating PDN soon.
-Rajiv
Pegasystems Inc.
US
Confirming Rajiv's info, I submitted doc FDBK-12027.
(Pega employees can view and follow Pega-internal PMF work items; customers cannot. The numbers are provided in this community space for reference.)
Pegasystems Inc.
US
FDBK-12027 has generated US-94889.
Pegasystems Inc.
HK
Rajiv
What are the types of exceptions that will be written to the alter log file?
I see EXCP0001 occurred in a performance log file, do we have further categorization on other exceptions, like EXCP0002, EXCP0003, etc.
thanks,
Pegasystems
IN
There is no further categorization as of today. In future we might have. As of now, any exception in the log file (done at the level of "error" or "fatal") will result in EXCP0001 alert which AES / PDC can parse and process better.
Amazon.com Inc
US
Hi Rajeev,
Does AES receives the ERROR log messages that are written to log file using Log-Message method? OR Does it only processes the exceptions that are occurred in the system? Is there any configuration in AES to receive ERROR log messages as well?