Posted: 31 Jul 2016 23:25 EDT Last activity: 8 May 2017 22:07 EDT
WebLogic errors on console
We are using Pega 7.2 on WebLogic 12.1.3c. Customer has reported that they are seeing error on Deployment Plan > Resource Dependencies in WebLogic console screen. We are unable to find any particular issues or errors on log files, but is this an issue? If our configuration is incorrect with any JDNI settings or deployment plan, we would like to know the impact and fix it properly.
How to get to this screen => Deployment Plan > prpc_wls_jee4 > Deployment Plan tab > Resource Dependencies
The message on screen is just a guidance - "Some application have dependencies on outside resources. This page describes the resources this application requires. Use this page to define what resources the application should use in this domain or create new ones." and it is not an error. But the three icons under PRAsync are red Xed and we are wondering if this is something wrong with our configuration. I am not sure if this is something we need to fix but we do not have other WebLogic environments to compare. Do you think this is an error or normal?
Posted: 5 years ago
Posted: 1 Aug 2016 7:37 EDT
Kevin Zheng (KevinZheng_GCS)
Director, Software Solutions Engineering
Never seen this before. Looks like the JMS resources of the PRAsync MDB modules are not defined correctly somewhere. Is the prpc accessible? There must be some error messages in the weblogic logs, can you please double check?
Thanks for your reply. PRPC is accessible / working well and we have not found any malfuctions. Infrastructure team says there are no error logs in this regard. The red X icons looks like an error but I am not sure. We followed the installation guide, but how could we check if these PRAsync things are configured correctly? If there is any WebLogic environment we can check, it would be great..
PRAsync is for batch processing within pega, are your agents running fine? It is hard to debug without error logs, if I were you I would just recreate those JMS resources to see if that fixes the issue.