# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 5
# self = https://watcher.sour.is/conv/axdk46q
Java inside docker: What you must know to not FAIL | Red Hat Developer

TIL: (_but I didn't want to!_) -- To configure your Java/JVM based apps to run in a container (Linux cgroup) environment _correctly_ set these JVM options:


-XX:+UnlockExperimentalVMOptions and -XX:+UseCGroupMemoryLimitForHeap


If you don't, the JVM does stupid shit 😅 #Java #Docker #Linux #Containers
Java inside docker: What you must know to not FAIL | Red Hat Developer

TIL: (_but I didn't want to!_) -- To configure your Java/JVM based apps to run in a container (Linux cgroup) environment _correctly_ set these JVM options:


-XX:+UnlockExperimentalVMOptions and -XX:+UseCGroupMemoryLimitForHeap


If you don't, the JVM does stupid shit 😅 #Java #Docker #Linux #Containers
Also if you're lucky enough to be using JVM 10+ (or unlucky to be forced into writing Java™ code 🤮) this _correct_ behaviour is now just built-in to the newest JVM v10+ and the options are no longer required.
Also if you're lucky enough to be using JVM 10+ (or unlucky to be forced into writing Java™ code 🤮) this _correct_ behaviour is now just built-in to the newest JVM v10+ and the options are no longer required.
@prologic Back in the days in an R&D project we ran into something similar (or the same? – didn't read the article). I don't remember the details anymore, but each containerized JVM thought, that it could use up the whole hardware cluster system resources and didn't obey the limits set in the container. And then of course it got killed.