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

Singleton has different conversion pattern

SA-9046

Summary



You use the log message conversion pattern "%d{yyyy-MM-dd}T%d{HH:mm:ss.SSS}*%p*%X{userid}%X{stack}*%c{3}*%m*%Y{instance_id}*PEGA%n" to send errors to a webservice via "com.pega.pegarules.priv.util.SOAPAppenderPega" in prlogging.xml configuration file.

For most errors there is a stacktrace at the end of the error. However, for "com.pega.pegarules.pub.runtime.ActivityTerminateException: Singleton: Set Initialization/UniqueActivityTerminateExceptions for unique exceptions" the stack trace appears to be in the middle of the entry. Is it intentional that these errors are entered differently for the same conversion pattern? Does %m get the content of %n if there is no 'error description'?



Resolution



Yes, %m gets the %n value in these cases (Singleton instance). Several of the other normal parameters are missing and what should be the end of the line before the stack trace now appears on a line after the stack trace.

Published June 12, 2015 - 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