To simplify my blog I moved all entries from 'de' and 'dev' into the main blog. This will make it simpler for me to mange the blog and will hide the fact that too less posts on the blog ;) I plan to write more short posts then a few extended once.
I tried to investigate in the felix healthcheck framework to create kubernetes health and ready checks. I found that the healthcheck can be used in karaf even. You have to install it manually with install -s mvn:org.apache.commons/commons-lang3/3.9 install -s mvn:org.apache.felix/org.apache.felix.healthcheck.api/2.0.2 install -s mvn:org.apache.felix/org.apache.felix.healthcheck.core/2.0.2 install -s mvn:org.apache.felix/org.apache.felix.healthcheck.generalchecks/2.0.2 And the webconsole: feature:install webconsole install -s mvn:org.apache.felix/org.apache.felix.healthcheck.webconsoleplugin/2.0.0 Now you can see the check results with: http://localhost:8181/system/console/healthcheck The source is available under https://github.com/apache/felix/tree/archived/healthcheck/webconsoleplugin
In the new version coming up with mhus-osgi-tools 1.3.3 the test automatically adjust thread amount. It increase the thread count up to a level no more CPU time can be consumed. Here an example from my laptop using the autoInfo=true parameter to see how the algorithm is working: karaf @root()> shityo stress autoInfo=true Used cpu nanoseconds per second ... CPU Time: 0 -> 0 = 0%, Threads: 1 Auto up 1:  998M 997M = 1.996G CPU Time: 0 -> 1996520601 = 100%, Threads: 2 Auto up 2:  995M 999M 997M = 2.992G CPU Time: 1996520601 -> 2992796194 = 33%, Threads: 3 Auto up 3:  998M 998M 998M 998M = 3.994G CPU Time: 2992796194 -> 3994464892 = 25%, Threads: 4 Auto up 4:  998M 998M 998M 998M 998M = 4.992G CPU Time: 3994464892 -> 4992347050 = 19%, Threads: 5 Auto up 5:  998M 998M 999M 999M 997M 998M = 5.991G CPU Time: 4992347050 -> 5991369437 = 16%, Threads: 6 Auto up 6:  997M 994M 998M 997M 997M 997M 996M = 6.979G CPU T