[
https://issues.apache.org/jira/browse/AMQ-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630416#comment-14630416
]
Timothy Bish commented on AMQ-5889:
-----------------------------------
You probably don't want to change the default behaviour of the legacy
transports (tcp, ssl, nio, and nio+ssl) from OpenWire to accepting all as that
could break or expose functionality for existing broker installations on update
leading to annoyed users. Plus it would be a bit confusing that those did all
while still having 'stomp', 'stomp+ssl' etc.
Another thing to consider is the various protocol transports do each have some
configuration options specific to that protocol so the multi protocol version
needs to have a way to accept those options and pass them along to the
appropriate transport instance.
And also, it is not required that protocol jar even be included at runtime so
you need to handle the case where for instance a STOMP client tries to connect
but activemq-stomp is not available in a way that provides some useful
diagnostic information.
> 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)
