Hmm, I'm a bit surprised because I would expect the opposite between Windows and Unix :)
Can you share the activemq.xml you are using? Regards JB On Wed, Feb 11, 2026 at 7:33 PM Rob Kirkbride <[email protected]> wrote: > Yes the same in both cases I believe. > We are in an Aws environment so we've tried both Amazon Linux and Ubuntu > Linux and applied all available patches. > We've also tried increasing the iops on the SSD storage, though there's no > evidence that it's a bottleneck. > > On Wed, 11 Feb 2026, 18:27 Jean-Baptiste Onofré, <[email protected]> wrote: > > > Hi > > > > Are you using the same activemq.xml ? Same JVM configuration ? > > > > We would need more details to investigate. > > > > Regards > > JB > > > > On Wed, Feb 11, 2026 at 6:02 PM KIRKBRIDE Robert via users < > > [email protected]> wrote: > > > > > Classified as: {Hitachi Rail - Public} > > > > > > We seem to have hit an issue with Linux Broker vs Windows Broker > > > performance that we can't understand or resolve. > > > We are using v6.2.0 of ActiveMQ Classic. We have a service that is > > pushing > > > messages to a virtual topic (VirtualTopic.Name), typically around 20-30 > > > bytes and these are being published at a frequency of around 130 > > messages / > > > second. We then have two services consuming from separate virtual topic > > > queues (Consumer.service.VirtualTopic.Name). On a Windows broker we > are > > > seeing ActiveMQ easily deal with this, with low CPU and memory usage. > > With > > > a Linux broker the messages are being consumed but seemingly not fast > > > enough as the queues build up over time (probably running about half > the > > > speed required) > > > The specifications of the Linux and Windows VMs are the same and in > both > > > cases, memory and CPU is low. > > > The clients are C# .NET services. Nothing else about the environment > > > changes. Any ideas as how we can resolve this, anything to try? Thanks > a > > > lot in advance. > > > > > > > > > {Hitachi Rail - Public} > > > > > >
