<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Java on Ben Petito</title><link>http://peti.to/tags/java/</link><description>Recent content in Java on Ben Petito</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 20 Jul 2026 09:00:00 +0930</lastBuildDate><atom:link href="http://peti.to/tags/java/index.xml" rel="self" type="application/rss+xml"/><item><title>The process was running. The system was dead.</title><link>http://peti.to/posts/process-was-running-system-was-dead/</link><pubDate>Mon, 20 Jul 2026 09:00:00 +0930</pubDate><guid>http://peti.to/posts/process-was-running-system-was-dead/</guid><description>&lt;p&gt;A couple of weeks ago, one of the systems we built and support stopped doing its job for about 42 hours, and almost nothing looked wrong while it happened.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s a document-processing system: documents arrive by email; an AI step reads the PDFs and turns them into structured data; our application validates and processes them; and the results flow out to the customer&amp;rsquo;s system of record. They&amp;rsquo;d not long gone live and were steadily onboarding new clients, so the volume was climbing week on week. Over a weekend, the scheduled processing simply stopped. The web application stayed up; the Java process never fell over; and every check watching it kept reporting the service as healthy. No crash, no alert. It only surfaced because someone noticed documents weren&amp;rsquo;t coming through, not because anything told us.&lt;/p&gt;</description></item></channel></rss>