ServiceMix Management port startup issues impacting activemq on stacked servers

Solution Unverified - Updated -

Issue

We're having an issue in our stacked farms (more than 1 SMX container per server) where, even though we change the management startup port for each instance to something unique, activemq is having issues binding.

Based on some traces I've done on startup, it appears that activemq sometimes attempts to bind to the wrong management port (default 1099) instead of the new one we've set for that instance. This is causing major issues in our shared test farms on a critical project and will soon carry over into production unless we can get some help.

Have you seen this before? Is there an easy fix we're unaware of?

Environment

Fuse ServiceMix 4.4.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.