Question
Anthem
US
Last activity: 3 Jan 2020 8:08 EST
Any documentation available for PEGA Exceptions,causes and solutions similar to PEGA alerts ?
Hi Team,
Do we have a PDN Article OR Formal documentation published by PEGA wrt the list of PEGA exception types,probable causes and recommended solutions ?
For Instance :
com.pega.pegarules.pub.generator.RuleNotFoundException
com.pega.pegarules.pub.services.ConnectorException
com.pega.pegarules.pub.clipboard.InvalidParameterException
java.lang.RuntimeException
com.pega.pegarules.pub.services.InboundMappingException
com.pega.pegarules.pub.services.RemoteApplicationException
com.pega.pegarules.pub.PRException
com.microsoft.sqlserver.jdbc.SQLServerException
com.pega.pegarules.pub.clipboard.InvalidReferenceException
Thank you.
Swedbank AB
SE
Hello Pradeep,
As per my understanding, there is no single page/link having information around all the classes. You should be able to locate multiple documents on the community on these classes linked to different issues.
Thank you,
Pawan
Pegasystems Inc.
IN
Agree to what Pawan had said.
May be this is a good place to start digging in community
Pegasystems Inc.
US
Hi Pradeep,
I agree with Santanu, Pega PDC is the place to go. It has been constantly adding new types of exception/alerts to help managing Pega environments. Have you implemented PDC in your environments?
For example, the latest PDC release 2.24 has the following additions:
Hi Pradeep,
I agree with Santanu, Pega PDC is the place to go. It has been constantly adding new types of exception/alerts to help managing Pega environments. Have you implemented PDC in your environments?
For example, the latest PDC release 2.24 has the following additions:
- PDC now recognizes the following alerts and exceptions:
- The Service package timeout exception is recognized as an OPS0023 alert.
- The Java heap space out of memory exception is recognized as an OPS0024 alert and treated as a critical event.
- The DSM Dataflow start/resume (PEGA0082) alert.
- The DSM Dataflow completed/paused/stopped (PEGA0083) alert.
- The Cluster segmentation causes sub cluster to form (PEGA0090) alert.
- The Queue Processor schedule (PEGA0102) alert.
- The Split-brain detection (PEGA0108) alert is treated as a critical event.
- The External service cannot be reached (PEGA0111) alert is treated as a critical event.
- The External service timeout waiting for response (PEGA0112) alert is treated as a critical event.
BPM Company
NL
Hi Pradeep,
I agree with KevinZheng and, generally, all the exceptions are (and must be) generic in nature. They triggered by different kind of events (especially, java.* ones).