{"id":57859,"date":"2023-07-31T23:10:22","date_gmt":"2023-07-31T17:40:22","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=57859"},"modified":"2024-06-10T15:38:11","modified_gmt":"2024-06-10T10:08:11","slug":"resolving-adobes-cloud-manager-deployment-issue-with-java-version-compatibility","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/resolving-adobes-cloud-manager-deployment-issue-with-java-version-compatibility\/","title":{"rendered":"Resolving Adobe\u2019s Cloud Manager Deployment Issue with Java Version Compatibility"},"content":{"rendered":"

Adobe’s Cloud Manager is a popular platform that provides continuous delivery capabilities for code deployments into Adobe Cloud service. However, we encountered a sudden pipeline failure during a recent deployment due to a Java version compatibility issue. In this blog post, we’ll share our experience in diagnosing and resolving this problem, ensuring a smooth deployment.<\/span><\/p>\n

The Error:<\/span><\/h2>\n

The error message that surfaced during the deployment is as follows:<\/span><\/p>\n

java.lang.RuntimeException: Unable to initialize JCR_MOCK resource resolver factory: Unable to invoke method ‘activate’ for class org.apache.sling.testing.mock.sling.MockJcrSlingRepositoryCaused by: java.lang.RuntimeException: Unable to invoke method ‘activate’ for class org.apache.sling.testing.mock.sling.MockJcrSlingRepositoryCaused by: java.lang.UnsupportedClassVersionError: org\/apache\/jackrabbit\/api\/observation\/JackrabbitObservationManager has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0<\/strong><\/em><\/p>\n

Investigation and Root Cause:<\/span><\/h2>\n

Upon thorough investigation, we found that the AEM Cloud Manager was set to use Java 8 as the default Java version and certain out-of-the-box classes were not compiled with Java 8, leading to the mentioned exception.<\/span><\/p>\n

Solution:<\/span><\/h2>\n

To address the compatibility issue and ensure a smooth deployment, we opted to build the Cloud Manager code using Java 11. We explored two approaches to achieve this:<\/span><\/p>\n

1. Maven Toolchains<\/span>
\n<\/span><\/a>One way to select an alternate JDK version for the entire Maven execution process is by using Maven Toolchains. However, we decided not to follow this approach because it would require additional steps to make it work locally, particularly since we were using OpenJDK for local development.<\/span><\/p>\n

2. Alternate Maven Execution JDK Version<\/a>
\nThe second approach ensures that you don’t need to change the local vendor for Java 11.<\/p>\n

Step 1<\/strong>. [Optional Step]<\/strong> Open the parent pom.xml file, and if you are using the maven-compiler-plugin, update it to use Java 11 as shown below:
\n<\/span><\/span><\/span><\/span><\/p>\n

\"\"<\/p>\n

Step 2<\/strong>. Create a file named .cloudmanager\/java-version<\/strong> at the parent level in the codebase.<\/p>\n

\"\"<\/p>\n

Step 3.<\/strong> Open the java-version file and add the value 11 to it.<\/p>\n

\"\"<\/p>\n

By implementing this second approach, we ensured that the AEM Cloud Manager was built using Java 11, resolving the Java version compatibility issue during deployment without requiring local configuration changes.<\/p>\n

Keeping your technology stack up-to-date is crucial for improving performance and stability. We hope this blog post helps you deal with similar issues and streamline your AEM deployments for optimal results. Happy coding!<\/p>\n

References:<\/h2>\n