Why you’re going to FAIL running Java on docker

Running Java on docker is easy, right? Just create a Dockerfile, run a Docker build, and then you’re ready to go. But thinking this way is the easiest path to complete FAILURE when running Docker containers in production.

A Java virtual machine (JVM) knows how to auto-tune itself to achieve the best possible performance in its environment, comprised of a single physical or virtual machine. But containers changes everything: you now need to know how containers manages their own resources and apply this knowledge when running and optimizing your JVM running in a container.

Attend this session about JVM and containers and avoid the highway to debugging hell. You’ll get simple tips & tricks that will save you hundreds of hours of debugging and logging container issues.

  • Date:Wednesday, May 9
  • Time:11:45 AM - 12:30 PM
  • Room:207
  • Location:Moscone South - 207
  • Session Type:Breakout
  • Session Code:S1714
  • Industry:
  • Best for people who:Build applications, Design application/system architectures
  • Technical difficulty:Appropriate for all levels
  • Primary solution:None of the above
  • Topic(s):Application development, Application platforms, Containers
  • Products and Services:Community project(s), Red Hat OpenShift Container Platform, Red Hat JBoss Enterprise Application Platform (EAP)
  • Session Includes:Demo
  • Time slot:Afternoon