<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Felipe Maschio on foojay.io - Friends Of OpenJDK</title><link>https://foojay.io/today/author/felipe-maschio/</link><description>Articles written by Felipe Maschio on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 11 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://foojay.io/today/author/felipe-maschio/index.xml" rel="self" type="application/rss+xml"/><item><title>How I got a thread dump from a timed-out GitHub Actions test</title><link>https://foojay.io/today/how-i-got-a-thread-dump-from-a-timed-out-github-actions-test/</link><pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/how-i-got-a-thread-dump-from-a-timed-out-github-actions-test/</guid><description>&lt;p&gt;A test hangs in CI, the job sits there for 30 minutes, and GitHub Actions cancels it. The log says the job exceeded its time limit and nothing about what the test was doing when it got stuck. Running it again locally rarely helps, because a timing problem that shows up on a 2-core runner can be close to impossible to reproduce on a laptop with 16.&lt;/p&gt;&#10;&lt;p&gt;What you want in that moment is a thread dump of the test JVM, taken while the test is still hung. I spent some time checking whether GitHub Actions leaves room for that, tried a few ways to get it, and ended up building an action around what I found. I built &lt;a href="https://threadmine.dev/" target="_blank" rel="noopener noreferrer"&gt;ThreadMine&lt;/a&gt;, the analyzer that action sends dumps to, but none of the collection methods below need it.&lt;/p&gt;</description></item><item><title>What jstack Misses When Your Java Service Uses Virtual Threads</title><link>https://foojay.io/today/what-jstack-misses-when-your-java-service-uses-virtual-threads/</link><pubDate>Tue, 27 Oct 2026 00:00:00 +0000</pubDate><guid>https://foojay.io/today/what-jstack-misses-when-your-java-service-uses-virtual-threads/</guid><description>&lt;p&gt;Take a Spring Boot service with virtual threads enabled, a HikariCP pool of 10 connections, and roughly 5,000 requests in flight. Latency is climbing. You grab a thread dump and find 43 platform threads, most of the scheduler workers waiting in &lt;code&gt;ForkJoinPool.awaitWork&lt;/code&gt;, and very little CPU activity.&lt;/p&gt;&#10;&lt;p&gt;If you used &lt;code&gt;jstack&lt;/code&gt;, the requests you&amp;rsquo;re looking for may never have made it into the file. On JDK 21 through 25, the traditional dump doesn&amp;rsquo;t list virtual threads. You can spend quite a while reading the scheduler&amp;rsquo;s stacks without seeing the requests waiting for your database.&lt;/p&gt;</description></item><item><title>Masking a JVM thread dump without breaking the analysis</title><link>https://foojay.io/today/masking-a-jvm-thread-dump-without-breaking-the-analysis/</link><pubDate>Wed, 09 Sep 2026 07:32:00 +0000</pubDate><guid>https://foojay.io/today/masking-a-jvm-thread-dump-without-breaking-the-analysis/</guid><description>&lt;p&gt;A few weeks ago I posted on r/java about detecting virtual thread pinning from a plain thread dump. The technical discussion was fine. The comment that stuck with me had nothing to do with pinning: &amp;ldquo;the problem isn&amp;rsquo;t taking the dump, it&amp;rsquo;s that uploading a production dump to a third-party site is against policy&amp;rdquo;. Not a preference. Policy. And the person saying it was right.&lt;/p&gt;&#10;&lt;p&gt;I run ThreadMine, a hosted thread dump analyzer, so that comment describes my own product. This article is about what I built in response: a small open-source CLI that rewrites the dump on your machine before it goes anywhere, in a way that keeps the analysis working. It&amp;rsquo;s called &lt;code&gt;tm-anon&lt;/code&gt;, it&amp;rsquo;s MIT, and it works with any analyzer, mine included. The interesting part isn&amp;rsquo;t the tool, it&amp;rsquo;s the constraint: you can&amp;rsquo;t just strip everything, because the analyzer needs most of what&amp;rsquo;s in there.&lt;/p&gt;</description></item><item><title>Your Loom App Quietly Became a Thread Pool Again: A Field Guide to Virtual Thread Pinning</title><link>https://foojay.io/today/virtual-thread-pinning-field-guide/</link><pubDate>Thu, 16 Jul 2026 07:43:16 +0000</pubDate><guid>https://foojay.io/today/virtual-thread-pinning-field-guide/</guid><description>&lt;p&gt;The incident that taught me to respect pinning looked like nothing. A service freshly migrated to virtual threads, a load test that plateaued at about 420 requests per second no matter how much traffic we threw at it, CPU sitting at 9%, zero errors, zero warnings, nothing in the logs. The machine had 8 cores, and the one downstream HTTP call in the hot path took about 19 ms. Do the arithmetic: 8 × (1000 / 19) ≈ 421.&lt;/p&gt;</description></item></channel></rss>