You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There could be differences between the environment where a snapshot gets created and the environment where the snapshot gets restored and run.
These differences could be related to:
Number of CPUs : affects thread counts in both the JVM (GC and JIT) and potentially the application (e.g. Liberty thread pool) if these are based on initialization done when the snapshot is created
Amount of RAM : affects heuristics for how much Java heap the JVM could end up using at run time
Random seeds need to be changed to avoid same sequences on all restored JVMs
File handles need to be attached properly, e.g. stdout/stderr in detached container
Timers need to be fixed up to avoid running N times to “catch up” after restore
Locale : a snapshot can be restored in a locale that is different to the one where the snapshot was created, e.g. via something like http://jaredmarkell.com/docker-and-locales/
TimeZone needs to be fixed up for restored locale environment
Date needs to be fixed up for restored environment
Environment variables need to be picked up from restored environment
ManagementFactory.getRuntimeMXBean().getUptime() (and maybe other similar fields) need to be restored to avoid giving large values for delta between snapshot and restore times
@DanHeidinga this issue can be used to catalogue what all we need to fix in the OpenJ9 hooks
The text was updated successfully, but these errors were encountered:
My goal is to work towards a common approach - new library feature? language changes? time will tell - to these kinds of issues. Especially useful if we can produce a single set of adaptations that can be broadly used by all consumers.
There could be differences between the environment where a snapshot gets created and the environment where the snapshot gets restored and run.
These differences could be related to:
@DanHeidinga this issue can be used to catalogue what all we need to fix in the OpenJ9 hooks
The text was updated successfully, but these errors were encountered: