How to Connect Boomi to ActiveMQ Without Crashing Atom Queues

If you are building an integration in Boomi that connects to an external ActiveMQ broker (like version 5.19.x) while also utilizing Boomi’s internal Atom Queues, you might run into a fatal issue: your Atom crashes and refuses to restart. Here is a breakdown of why this happens and the exact steps to fix it. The Problem: Classpath Collisions To connect to an external ActiveMQ broker, Boomi requires the specific ActiveMQ client driver (e.g., activemq-client-5.19.1.jar). The standard Boomi documentation often suggests dropping custom JAR files directly into the Atom’s userlib or userlib/jms directories. However, if you are also using Atom Queues, this creates a massive problem. Boomi’s Atom Queues are powered by an embedded version of ActiveMQ. When you enable them, Boomi automatically loads its own internal ActiveMQ JARs into the JVM. When you manually place your new activemq-client JAR into the userlib folder, Boomi tries to load both versions at startup. The result? A fatal classpath c