sap-java-buildpack-troubleshooting-ee609aa.md

SAP Java Buildpack: Troubleshooting

This page provides solutions on known issues related to SAP Java Buildpack 1 and 2.

If you can't find a solution to your problem, create an incident to component BC-CP-CF-BLDP.

To learn how to start, see: Troubleshooting

Application Deployment on TomEE 1.7 Fails

Problem

When trying to execute a Java application running on Apache TomEE 1.7, the following error appears:

SEVERE: Unhandled exception in Buildpack main method: None of the available runtimes [Tomee7, Tomcat, Java Main] supports the application in the specified path.

Reason

Since May 5, 2022, Apache TomEE 1.x is no longer supported by SAP Java Buildpack 1 (effective version 1.53.0). See: Release Notes

You need to modify your Java applications to run on Apache TomEE 7 instead. To do that, follow the solution below.

Solution

1. Configure the manifest.yml file of your Java application:

   • Make sure that the buildpack variable is set to sap_java_buildpack. If pinned to a particular version, it must be at least 1.53.0.

   • For the TARGET_RUNTIME variable, replace tomee with tomee7. To learn more, see TomEE 7.

     For example:

     
       ---
       applications:
       - name: myapp
         path: .\target\myapp.jar
         buildpacks: 
         - sap_java_buildpack
         . . .
         env:
           TARGET_RUNTIME: tomee7
           JBP_CONFIG_COMPONENTS: "jres: ['com.sap.xs.java.buildpack.jdk.SAPMachineJDK']"
     
     

2. Check the information provided for Apache TomEE: Migrate from TomEE 1 to TomEE 7

3. Besides the TARGET_RUNTIME variable, additional setups are needed. Please follow the guide for using TomEE 7.

4. After applying the new change, if your application fails with an OutOfMemoryError exception, change your memory size configuration. See:

   Memory Calculator V1

   XS Advanced Model: Memory Size Options

Application running on SAP Java Buildpack 1 fails after restage or redeploy

Problem

You have a working Java application, which runs on sap_java_buildpack (SAP Java Buildpack 1). After restage or redeploy, it fails and is no longer working. In the logs, you see the following error message:

For application '<app_name>': Specified unknown buildpack name: "sap_java_buildpack"
FAILED

Reason

As previously announced, sap_java_buildpack has been deprecated. It was removed from SAP BTP, Cloud Foundry environment on October 30, 2025.

Solution

To keep your Java applications up and running, you need to migrate to SAP Java Buildpack 2 as soon as possible. To learn how, see: Migrate your Applications to SAP Java Buildpack 2

In exceptional cases (if you haven’t managed to migrate yet), you can keep using SAP Java Buildpack 1 till the end of 2025. To do that:

1. Open your manifest.yml or mtad.yaml file.
2. Replace sap_java_buildpack with sap_java_buildpack_to_be_removed.
3. Restage or redeploy your application.

Note:

This is just a temporary solution – please migrate to SAP Java Buildpack 2 as soon as you can!