Existing JAVA App failed to upgrade by updating java buildpack and errorred out "Could not find agent library xxx in absolute path, with error: xxxx_RELEASE: cannot open shared object file: No such file or directory"
search cancel

Existing JAVA App failed to upgrade by updating java buildpack and errorred out "Could not find agent library xxx in absolute path, with error: xxxx_RELEASE: cannot open shared object file: No such file or directory"

book

Article ID: 298358

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

Customer's app is built on java buildpack v4.49, when they upgrade the app to v4.53 by updating the manifest.yaml file, the jvmkill version does not get updated to 1.17.0_RELEASE from current jvmkill-1.16.0_RELEASE and the app throws below error -
Error : Could not find agent library /home/vcap/app/.java-buildpack/open_jdk_jre/bin/jvmkill-1.16.0_RELEASE in absolute path, with error: /home/vcap/app/.java-buildpack/open_jdk_jre/bin/jvmkill-1.16.0_RELEASE: cannot open shared object file: No such file or directory
If customer deploy a new app with v4.53, they won't see this issue and the latest jvmkill version is updated in the start command. The error only happens when trying to update the java buildpack version.

Environment

Product Version: 2.11

Resolution

This issue could due to the application was provided with an explicit command (either in a manifest, procfile, or on the command line). To fix this, useĀ "cf push -c null" to delete a custom command once once is pushed OR delete the app and push a fresh app.