[
https://issues.apache.org/jira/browse/AMQ-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682383#comment-14682383
]
ASF subversion and git services commented on AMQ-5889:
------------------------------------------------------
Commit 04ee70a161b463f69692debea623d754a5c781c2 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=04ee70a ]
https://issues.apache.org/jira/browse/AMQ-5889
Adding support for auto detection of wire protocols over a transport.
OpenWire, AMQP, STOMP, and MQTT can all be detected and the broker
will properly handle each one over a given Transport. Currently
auto TCP, NIO, SSL, and NIO+SSL transports can handle auto-detection
of the wire format and client but support could be added in the
future for other transports like websockets.
> 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
> Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> 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)
