Reply posted on May 30, 2019 by Lochan_DVMod
Thank you for updating the solution! We will mark post as Answered.
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Vasilii Pozdeev for achieving the title of Participant of the Week! By participating in several posts, Vasilii is helping our users troubleshoot better. Sharing knowledge is a special quality found in great learners and we heartfully support sharing and learning on our community.
Thank you Abhinav. We can able to configure the following modification in the Tomcat application server by modifying the context.xml and web.xml. But Tomcat does not support JMS connection pooling mechanisms, which creates numerous connection when...
If I can answer for Nick, what likely happened is that when the error occurred, it was logged at the lowest level by the database system. However, when Pega saw the error, it swallowed it and then executed the alternate operation, which worked. As...
it was a caching issue. below thread helped me to solve the issue, https://community1.pega.com/community/pega-academy/question/cache-hit-not-found-cache-miss
Hello! On reviewing the SR we see that the below changed resolved the issue. Open the activity KMSearchRDHelpSite and update the value pySearchMethod to "CONTAINS" in 5th step of the activity. Thank you,
Thanks Abhinav. I should have mentioned this in my original post, we are using PRPC 7.2.1. We were able to install SMA module and can see requestor pools now.
I think that "Show-Property" is indicated as a debugging tool primarily because it breaks the normal processing flow that would otherwise be expected. For your use case, if it works without issue, I would say there is no problem using it. By...
Please wait while we search for PDN content that suits your question.