I have setup Pega Platform '23 on a Tomcat ( version 9 ) server and facing below error to start pega application. Please help to resolve this issue.
Logs:
02-Apr-2024 04:59:50.196 INFO [main] java.util.ArrayList.forEach Name = PRFileStore Ignoring unknown property: value of “Database-based File Access” for “description” property
02-Apr-2024 04:59:50.203 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
02-Apr-2024 04:59:50.204 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
02-Apr-2024 04:59:50.205 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/prweb] startup failed due to previous errors
02-Apr-2024 04:59:50.214 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat9/webapps/prweb] has finished in [107] ms
The error message “Context [/prweb] startup failed due to previous errors” indicates that the Pega Platform application failed to start due to an error in one or more listeners. The “One or more listeners failed to start” message suggests that a specific listener component encountered an issue during initialization.
To resolve this issue, you need to identify the specific listener that is causing the failure. The full details of the error should be available in the catalina.out log file. You can check the log file for any exceptions or error messages that may provide more information about the cause of the failure.
Once you have identified the problematic listener, you can try the following steps to resolve the issue:
Check the listener configuration: Verify the configuration of the listener in the “web.xml” deployment descriptor file. Ensure that the listener class is specified correctly and that all required dependencies are met.
Update listener dependencies: If the listener requires any specific libraries or dependencies, make sure that they are available in the application’s classpath. Add the necessary JAR files to the “WEB-INF/lib” directory of the application.
Debug the listener code: If the configuration appears to be correct, you can try debugging the listener code to identify any potential issues. Set breakpoints in the listener’s initialization method and step through the code to see if there are any exceptions or errors being thrown.
Disable the problematic listener: As a last resort, you can temporarily disable the problematic listener to allow the application to start. Comment out or remove the listener declaration from the “web.xml” file. However, this should only be done as a temporary measure, as the listener may be essential for the proper functioning of the application.
Contact Pega Support: If you are unable to resolve the issue by following the above steps, you can contact Pega Support for further assistance. They may have specific knowledge or insights into the issue and can help you troubleshoot and resolve the problem.
Once you have resolved the issue with the problematic listener, you should be able to successfully start the Pega Platform application.
@Megha007 Thanks for your workaround , Now am facing the issue in sql driver and checked all configuration its all good. If I run the tomcat service could pegarules logs are not rolling and could see below errors.
ERROR:
NOTE: Picked up JDK_JAVA_OPTIONS: --add-exports java.base/jdk.internal.ref=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Cannot create JDBC driver of class ‘’ for connect URL ‘null’
java.sql.SQLException: No suitable driver
at java.sql/java.sql.DriverManager.getDriver(DriverManager.java:298)
Cannot create JDBC driver of class ‘’ for connect URL ‘null’
java.sql.SQLException: No suitable driver
at java.sql/java.sql.DriverManager.getDriver(DriverManager.java:298)
Please log your new error in a new question if you still need help.
The error message you’re seeing indicates that the JDBC driver cannot be created because no suitable driver was found. This usually happens when the driver is not properly installed or configured. In the context of Pega and Tomcat, this could mean that the driver is not correctly specified in the Tomcat context configuration file or the driver JAR file is not placed in the correct location. You should check your Tomcat configuration and ensure that the correct driver is specified and the driver JAR file is located in the Tomcat lib directory. If the problem persists, you may need to consult with your system administrator or Pega support for further assistance.
Now Pega’23 is running fine on my local machine but in Pega console its showing “Embedded/External Elasticsearch mode is deprecated. Configure external search using Search and Reporting Service.” popup.and I attached the popup in this thread. Is there any workaround to set a embedded kafka and elastic search to my pega’23 ?
@HarshithB17121293 I’m afraid I can’t answer your question. I’m not sure what console you are using. Please log a support ticket if you need further help.
