Campaign Classic: Postupgrade start failure of web module due to Java 11 JVM recognition
This article lists the troubleshooting steps to resolve a postupgrade problem with JRE detection after an upgrade.
Description description
After an upgrade of an on premise instance to 7.4.2 9391 version the customer was not able to start the web module of their instance and saw an error:
JVM-510015 Error while recovering the 'com/neolane/jssp/JSSPServlet' class (iRc=-53)
Resolution resolution
Recommended troubleshooting steps:
- run the postupgrade command again
- regenerate the serverConf.xml file following the steps:
- stop web process
- rename the serverConf.xml to serverConf.xml.tmp
- restart web then you can get a new file serverConf.xml
- merge this new file with the customisation
- restart the service
- verify that both files that handle JSSP servlets exist on PROD after the upgrade.
$(XTK_INSTALL_DIR)/tomcat/lib/servlet-api.jar
$(XTK_INSTALL_DIR)/java/lib/nlweb.jar
It is advisable to compare the contents of these directories between instances that work and don’t work to ensure they match.
If the files and directory contents are identical in both environments, the environment variables must also be compared and verified to be the same.
- R&D confirmed that after 7.4.1 version, JRE_HOME variable needs to be declared. The JRE is no longer detected automatically. Instead the env variable JRE_HOME has to be defined manually, the folder pointed by this variable should contain bin/server/jvm.dll.
Reference -> https://experienceleague.adobe.com/en/docs/campaign-classic/using/installing-campaign-classic/install-campaign-on-prem/deployment-guidelines/application-server
- the final recommendation was that the customer runs the postupgrade log without any errors, and declare variables after that to point to Java 11.