Community

Collecting Diagnostic Data After a Crash

Share this post:

If a Liberty Bluemix application crashes, the default behavior is that it will immediately restart. The problem with this behavior is that all diagnostic files such as dumps and traces are lost. In order to delay the restart so that dumps and traces can be collected, set this environment variable for your application:

IBM_JAVA_OPTIONS: -Xdump:tool:events=gpf,exec="sleep 1d" -Xdump:what

This environment variable results in the JVM remaining available (but non-functional) after a crash. Traces and dumps can be collected with the cf files command, and then the application can be restarted with cf stop and cf start.

The application will be automatically restarted after the time period specified on the sleep command (1 day, in the above example). Note that you can specify any time period using s, m, h, or d for seconds, minutes, hours, or days, respectively.

Setting the environment variable can be done in a number of ways:

  • Using the cf push command with -f option to provide a manifest.yml that contains the environment variable. Here is a sample manifest.yml:
<strong><code># manifest for crashTest<br />applications:<br />- name: crashTest<br />  memory: 512M<br />  path: c:\tmp\zips\crashTest.zip<br />  env:<br />    IBM_JAVA_OPTIONS: -Xdump:tool:events=gpf,exec="sleep 1d" -Xdump:what</code></strong>
  • Using the cf set-env command on an already pushed app, followed by cf push to activate the new setting. This command requires outer quotes for the entire value and escaping the inner quotes around the sleep command with backslashes like this:

cf set-env <appName> IBM_JAVA_OPTIONS "-Xdump:tool:events=gpf,exec=\"sleep 1d\" -Xdump:what"

  • Using the ACU UI to set the environment variable under the runtime. The application is automatically restarted when you press ‘save’. No outer quotes or backslashes are required on the value.

Details on the -Xdump option can be found here:
http://www-01.ibm.com/support/docview.wss?uid=swg21242497

Using cf logs <app> –recent may provide some useful diagnostics after a crash even without the IBM_JAVA_OPTIONS environment variable set. If issued promptly, it may confirm that a crash and restart has occurred.

More stories
May 7, 2019

We’ve Moved! The IBM Cloud Blog Has a New URL

In an effort better integrate the IBM Cloud Blog with the IBM Cloud web experience, we have migrated the blog to a new URL: www.ibm.com/cloud/blog.

Continue reading

May 1, 2019

Two Tutorials: Plan, Create, and Update Deployment Environments with Terraform

Multiple environments are pretty common in a project when building a solution. They support the different phases of the development cycle and the slight differences between the environments, like capacity, networking, credentials, and log verbosity. These two tutorials will show you how to manage the environments with Terraform.

Continue reading

April 29, 2019

Transforming Customer Experiences with AI Services (Part 1)

This is an experience from a recent customer engagement on transcribing customer conversations using IBM Watson AI services.

Continue reading