[BUG] Azure Spring Apps deployment failed with Java 21

[kirankumar994]

Describe the bug I have a spring boot application running with Java 17 which has been to deployed to azure spring apps and it is up and running. Recently, I have upgraded to Java 21 as well as Spring boot version to v3.3.3. The application is up and running on my local machine with latest versions. But, when I try to deploy it to azure spring apps, the deployment is getting failed with message says "InternalServerError".

Later, I tried with simple spring demo application with Java 21. I have faced the same issue. Please find the below screenshots for the same. I am getting an option to select Java 21 runtime, but when I am trying to deploy with Java 21 it is failed. The azure spring apps documentation also says Java 21 is supported. I have created Azure spring apps with Standard plan pay as you go, East US region, FYI. Please help me out what is wrong here. Thanks in advance.

Exception or Stack Trace

To Reproduce Steps to reproduce the behavior:

Code Snippet Add the code snippet that causes the issue.

Expected behavior The deployemnt should be succeeded as it is shown for other applications with Java 17.

Screenshots

Setup (please complete the following information):

• Java version: 21

  My local machine set up: Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) Maven home: /opt/maven Java version: 21.0.4, vendor: Microsoft, runtime: /home/user/.sdkman/candidates/java/21.0.4-ms Default locale: en_IN, platform encoding: UTF-8 OS name: "linux", version: "6.8.0-40-generic", arch: "amd64", family: "unix"

[github-actions[bot]]

@moarychan @netyyyy @rujche @saragluna

[github-actions[bot]]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[saragluna]

@kirankumar994 Seems like not an issue related to the Spring Cloud Azure library but will ask the Azure Spring Apps folks to help take a look at it.

[kirankumar994]

Thank you for your reply, @saragluna . Could you please get it resolved as soon as possible as the new release of my application is on hold?

[saragluna]

@kirankumar994 the Azure Spring Apps team is working on it now.

[TobiasB91]

My company's application is blocked by this bug as well.

[saragluna]

Azure Spring Apps updates that the fix has been out. Could you please help check again?

[TobiasB91]

Thanks for the quick response! I tried to recreate my app this morning, but even though the InternalServerError is gone I'm not able to start my app. My AppEnvSpringAppConsoleLogs logs "Error occurred during initialization of VM" and "Too small maximum heap".

[kirankumar994]

Thanks for your reponse, @saragluna . I am able to deploy it with Java 21 only by uploading the jar file directly on the portal.

But, however the application deployment is still failing from the pipelines. I am using the below plugin to deploy my application to the Azure spring apps. I have also created a separate app to double check the issue, but no luck though. I think it is always taking the default or the first option i.e., Java 11 even though I am giving run time version Java_21 in the plugin. Seems like the plugin issue. When I am trying to deploy with "az spring app deploy" cmd with the respective arguments as below, it is success.

cmd: az spring app deploy -n dms-backend -s dms-apigateway -g plevenn-plm-dev-reg --artifact-path dms-launcher/target/dms-launcher-0.0.1-SNAPSHOT.jar --runtime-version Java_21

I am getting the below error when I try to deploy with the below cmd. "mvn azure-spring-apps:deploy"

[kirankumar994]

Hi @saragluna , hope you had a chance to look at my comment. However, I managed to deploy my application with the below cmd in my pipelines.

"az spring app deploy"

Seems like the issue lies on the plugin side where it doesn't have Java 21 runtime version, so it is taking Java 11 by default. Thanks for looking into it.

[saragluna]

Closing this issue now, please reopen it if there is further issue.