pivotal-david-osullivan
commented
2 years ago Although I produced the same Memory Calculator values on startup using your sample app, I did not hit the OOM error:
Setting Active Processor Count to 4
Memory Calculation: (100% * (30531 + 12562 + 144 + 0)) * 0.35
Calculated JVM Memory Configuration: -XX:MaxDirectMemorySize=10M -Xmx437195K -XX:MaxMetaspaceSize=99380K -XX:ReservedCodeCacheSize=240M -Xss1M (Total Memory: 1G, Thread Count: 250, Loaded Class Count: 15132, Headroom: 0%)
Enabling Java Native Memory Tracking
Adding 127 container CA certificates to JVM truststore
Spring Cloud Bindings Enabled
Configuring AppDynamics properties
Picked up JAVA_TOOL_OPTIONS: -Djava.security.properties=/layers/paketo-buildpacks_microsoft-openjdk/java-security-properties/java-security.properties -XX:+ExitOnOutOfMemoryError -javaagent:/layers/tanzu-buildpacks_appdynamics/appdynamics-java/javaagent.jar -XX:ActiveProcessorCount=4 -XX:MaxDirectMemorySize=10M -Xmx437195K -XX:MaxMetaspaceSize=99380K -XX:ReservedCodeCacheSize=240M -Xss1M -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary -XX:+PrintNMTStatistics -Dorg.springframework.cloud.bindings.boot.enable=true
...
2022-09-08 08:08:10.471 INFO 1c852f0cfb1b --- [kground-preinit] o.h.v.i.u.Version : HV000001: Hibernate Validator 6.0.22.Final
2022-09-08 08:08:10.813 INFO 1c852f0cfb1b --- [ main] c.a.s.c.t.c.c.MasonApplication : Starting MasonApplication on 1c852f0cfb1b with PID 1 (/workspace/BOOT-INF/classes started by cnb in /workspace)
2022-09-08 08:08:10.831 INFO 1c852f0cfb1b --- [ main] c.a.s.c.t.c.c.MasonApplication : No active profile set, falling back to default profiles: default
2022-09-08 08:08:15.255 INFO 1c852f0cfb1b --- [ main] o.s.b.w.e.t.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2022-09-08 08:08:15.351 INFO 1c852f0cfb1b --- [ main] o.a.c.h.Http11NioProtocol : Initializing ProtocolHandler ["http-nio-8080"]
2022-09-08 08:08:15.354 INFO 1c852f0cfb1b --- [ main] o.a.c.c.StandardService : Starting service [Tomcat]
2022-09-08 08:08:15.357 INFO 1c852f0cfb1b --- [ main] o.a.c.c.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.41]
2022-09-08 08:08:15.532 INFO 1c852f0cfb1b --- [ main] o.a.c.c.C.[.[.[/] : Initializing Spring embedded WebApplicationContext
2022-09-08 08:08:15.532 INFO 1c852f0cfb1b --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4499 ms
2022-09-08 08:08:16.434 INFO 1c852f0cfb1b --- [ main] o.s.s.c.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor'
2022-09-08 08:08:17.013 INFO 1c852f0cfb1b --- [ main] o.s.b.a.e.w.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path '/actuator'
2022-09-08 08:08:17.091 INFO 1c852f0cfb1b --- [ main] o.a.c.h.Http11NioProtocol : Starting ProtocolHandler ["http-nio-8080"]
2022-09-08 08:08:17.171 INFO 1c852f0cfb1b --- [ main] o.s.b.w.e.t.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2022-The Metaspace size is automatically calculated using a formula, by counting the number of classes loaded, i.e. the number of class files in the jar, multiplied by a fixed class size value + a fixed class overhead value. This calculation usually works well for Spring Boot apps. We recently added support for counting classes specified within javaagent: property jars to ensure a more accurate calculation, so in this case we know the AppD agent classes are included.
Unless there is another difference here, it is possible that the calculated value for Metaspace is just below the amount required. Adding the Eureka jar will increase the class count and therefore increase the calculated Metaspace size (by around 30M here) which seems to be just enough to start successfully.
One thing you can try is adjusting the class count - a runtime variable exists to set a class count adjustment factor. BPL_JVM_CLASS_ADJUSTMENT. Try setting this to a percentage value, e.g. 120% which will result in a higher Metaspace size and see if the app starts successfully.
zhoufenqin
showpune
dmikusa
I create a spring boot app with Dynamic buildpack, the app failed to start with
Terminating due to java.lang.OutOfMemoryError: Metaspaceerror. The OOM app sample respo: https://github.com/zhoufenqin/java-sample/tree/main/echo-app-oomThe buildpack i'm using: tanzu-java-azure:7.28.0 libjvm v1.37.0
The errorlog show:
Then I add some other dependency in
pom.xml, likeThe app can be started, the metaspace is larger than before The correct app repo: https://github.com/zhoufenqin/java-sample/tree/main/echo-app
The log shows:
These two app are only different in
pom.xml, the correct one have eureka dependency but the oom one hasn'tHow the
Metaspace sizecalculate?Expected Behavior
The calculate Metaspace size should large enough
Current Behavior
The app failed to start because of OOM metaspace
Possible Solution
Steps to Reproduce
1.
Motivations