Java Buildpack in 2017
summary
Java Buildpack 4.x introduces a memory calculator that bounds six JVM regions (heap, metaspace, compressed class space, reserved code cache, thread stacks, direct memory), which raises the true baseline to roughly 650 MB before any heap and is available as an opt‑in replacement. A container security provider injects OpenSSL trusted certs into the JVM, enables rotating Diego identities and transparent mutual TLS for outbound calls. A new JVM‑Kill tool emits histograms of the top offending types on OOM and can write heap dumps to mounted volume services; OpenJDK Zulu and IBM J9 and APM/debugger integrations are supported.
AI-written summary · about
chapters (9)
- 0:00Introduction to Java buildpack
- 1:02Role of Java buildpack
- 3:32JRE improvements in 2017
- 4:35Container options for Java apps
- 5:40Zero-touch service integrations
- 8:53Container security provider demo
- 17:50JVM memory calculator update
- 25:40Introducing JVM kill tool
- 31:17Summary and Q&A
related talks
47mLegal JVM Doping in Your Containers
31mRunning Java Applications on Cloud Foundry
42mA State of Java Elasticity
45mScooby RAM, where are you?
43mA Glance At The Java Performance Toolbox
48mJava in Containers - Part Deux
42mContainers & Java: What I wish I have been told!
40mA Glance At The Java Performance Toolbox