Route ActiveMQ Classic's HTTP Transport Through a Proxy

Use this only for a broker exposing ActiveMQ Classic's HTTP transport, with the matching client transport implementation available. A TCP connector or administration web page is not that endpoint.

ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory(
    "http://broker.example:8081?proxyHost=proxy.example&proxyPort=8080");

broker.example:8081 is the HTTP broker destination. proxy.example:8080 is its forward intermediary. The proxy parameters remain URI options; they do not replace the broker hostname. If the broker’s HTTP transport is publicly reachable and public intermediaries are permitted, the HTTP proxy list can supply candidate proxyHost/proxyPort values for a route with no proxy credentials configured. Confirm access to the actual broker host and HTTP transport port.

ActiveMQ Classic 5.18.3 builds its route from proxyHost/proxyPort and accepts proxyUser/proxyPassword, scoping supplied HTTP credentials to that proxy endpoint. Construct authenticated URIs through the application's parameter handling so reserved credential characters remain encoded.

The intermediary account is separate from the broker account used by JMS connection methods. Keep this configured factory for its assigned route: changing another HTTP client elsewhere in the JVM does not update a factory already built with explicit options.