davsclaus opened a new pull request, #28056: URL: https://github.com/apache/camel/pull/28056
CAMEL-25754: `camel infra run artemis` started the container with the broker's default `max-disk-usage` of 90%. On a developer machine, the disk that counts is the Docker VM disk, which often fills with images. Above 90%, the broker blocks every producer: ``` WARN AMQ222210: Free storage space is at 2.3GB of 84.4GB total. Usage rate is 97.3% which is beyond the configured <max-disk-usage>. System will start blocking producers. WARN AMQ222212: Disk Full! Blocking message production on address 'orders'. Clients will report blocked. ``` The route then hangs on its send. Its own log shows only a WARN from the Artemis client (`AMQ212054: Destination address=orders is blocked`). Found while building a JMS example for the AI benchmark, on a machine with 212 GB free on its own disk and a Docker disk at 98%. ## What - **The container** (`ArtemisContainer`, which `camel infra run artemis` uses) switches the disk check off: `JAVA_ARGS_APPEND=-Dbrokerconfig.maxDiskUsage=-1`. - **The embedded services** used `setMaxDiskUsage(98)`; they use `-1` now as well. ## Tests - **The container setting**, checked by hand with the same image on that machine. Without it, the broker blocked as above. With it, it logged no disk warning, and the example's routes and its Citrus test passed. - **The embedded broker:** `JmsSimpleRequestReplyTest` (camel-jms, embedded Artemis from test-infra) passes with `-1`. - camel-test-infra-artemis builds. It has no tests of its own. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
