Recurring exception with very few information
We have installed a new Pega 7.3 environment with CPMFS, IFFS and OBFS frameworks and now we keep having this exception 4-5 times each 10 minutes:
2017-10-10 10:08:08,374 [rnal_WorkManager : 5] [ STANDARD] [ ] [ PegaRULES:07.10] ( etier.asynchbeans.AsyncTask) ERROR - com.ibm.ejs.container.UnknownLocalException: nested exception is: com.pega.pegarules.pub.PRRuntimeException: Cannot handle Async Request. NULL resource type
There is no any extra information and I have been unable to correlate it to other errors. The only thing that keeps changing is the application that generated it (PegaRULES:07.10, KYCFS:07.22, SalesAutomation -which we have not installed- 7.22 and PegaCSSSample 7.21)
Has anybody faced such an exception?
Thanks,
Víctor
***Moderator Edit: Vidyaranjan | Updated Categories & SR details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-48627 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,
Pegasystems Inc.
US
can you turn on the debug for the following logger until error is thrown few times and see whether any additional info logged about the error in pegarules log file?
Logger name:
com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Tech Mahindra
CA
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved. SA-48627 was created as a result of the investigation. Please reference that if you have the same question.
Thank you,