[
https://issues.apache.org/jira/browse/AMQ-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635551#comment-14635551
]
Christopher L. Shannon commented on AMQ-5889:
---------------------------------------------
I now have this working for all 4 transports. (nio+ssl took a while to get
right). The main thing left to do is to clean up the code and to write some
more tests to make sure there are no issues. I especially need to test to make
sure all the different configuration options get applied properly. The
configuration is going to look like:
{noformat}
<transportConnectors>
<transportConnector name="auto" uri="auto://0.0.0.0:61616"/>
<transportConnector name="auto+nio" uri="auto+nio://0.0.0.0:61617"/>
<transportConnector name="auto+ssl" uri="auto+ssl://0.0.0.0:61618"/>
<transportConnector name="auto+nio+ssl"
uri="auto+nio+ssl://0.0.0.0:61619"/>
</transportConnectors>
{noformat}
> Support a single port for all wire protocols
> --------------------------------------------
>
> Key: AMQ-5889
> URL: https://issues.apache.org/jira/browse/AMQ-5889
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Christopher L. Shannon
>
> Both Apollo and Artemis support the ability to use a single port for all
> protocols and to have automatic detection for the protocol being used. It
> would be nice to be able to support at least a subset of this feature in the
> 5.x broker as well.
> Ideally we should at least be able to detect OpenWire, MQTT, STOMP, and AMQP
> over a TCP, SSL, and NIO transport. Websockets and HTTP would be a bonus but
> could be more difficult to implement depending on how this could work with
> Jetty so that would take some investigation.
> This is especially useful in environments where having to open up several new
> ports can be difficult because of firewall and security restrictions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
