We encountered one issue in the last production change and getting an exception on the UI while submitting enrollments to downstream system.
Please find the steps which we performed.
Deleted the Database instance as this is duplicate and having database connection string, username / Password hard coded in this instance and we have already PEGA_RULES with JNDI connection.
After that we bounced all Pega servers.
As part of testing killed one database instance to check the application availability and database server automatically restarting or not? (we have a RAC node solution in the Database)
Oracle server restarted successfully and traffic routed to the second instance successfully.
We were able to login into application, and able to create enrollments & at final submission process to downstream system getting an exception on the UI <<Implementation class name>> Java.lang.NoClasssDefFoundError:Com/Pega/apache/log4J/spi/ThrowableInformation
We need to bounce Pega Serves bounce or not ? after the oracle instance restarted.
Observed this error in the log files while testing. << Security Access Error: Fail: No credentials supplied >>
***Edited by Moderator Marissa to update platform capability tags***
If you could provide the complete stack trace/PegaRULES_log for the above error will be helpful. The exception could be as a result of failure to load the engine classes(ThrowableInformation and StackTrace are common classes to preload). It is recomended to restart the a prpc instance on restarting the database instance.
Thanks for your response Basavarj. We have a RAC node solution from the Database side, as part of this work we are testing the PROD application availability. Incase if the first instance went down, it should automatically connect to the second database instance (This step is successfully tested)
After killing the 1st database instance the overall application is okay to connect (The application relies on database connections) only issue when submitting this application at final step to downstream systems.
Questions here, even the database is available to connect, Pega servers bounce is required?
Are you saying that your DB failover appears to have worked fine, in the sense that the connection was re-established, however, when you tested the application end to end, you saw some failure with submitting your applications.
And you are asking, if you should also restart the app server?
If so, are you asking because you notice the issue goes away after restart?
Yes connection was re-established to second database instance successfully and application is available to create enrollments, issue is while submitting to downstream system getting an error on the UI Java.lang.NoClassDefFound:Com/Pega/apache/log4j/spi/ThrowableInformation
After Pega servers restarted we are able to submit to application successfully without any issues.
now question is even the applications is available and database connection is established why servers bounce is required? and also normally in which scenario's this exception is generating.
Hi Veera, yes this is a good question. If you can consistently reproduce this problem then an SR may be a good idea so that a deeper dive can be performed. It sounds likes the high availability/failover is working, but not 100% here.