[
https://issues.apache.org/jira/browse/STRATOS-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesh Gunaratne resolved STRATOS-1168.
--------------------------------------
Resolution: Fixed
Fix Version/s: 4.1.0 RC1
- Introduced above feature, messaging transport can be switched between AMQP
and MQTT by setting the following system property:
{code}
messaging.transport=mqtt|amqp
{code}
- Fixed with commit revision:
{code}
4bead36d4399487ef61c3ba7d86300f2acecb8e3
{code}
> Introduce Ability to Switch Messaging Transports and Add Support for AMQP
> -------------------------------------------------------------------------
>
> Key: STRATOS-1168
> URL: https://issues.apache.org/jira/browse/STRATOS-1168
> Project: Stratos
> Issue Type: Improvement
> Components: Messaging
> Affects Versions: 4.1.0 Alpha
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Priority: Critical
> Fix For: 4.1.0 RC1
>
>
> Currently messaging component only supports MQTT transport. This has several
> drawbacks:
> I wanted to implement an automated integration test which could start an
> ActiveMQ instance (using ActiveMQ embedded server) and a Stratos server
> instance and run sample applications against Mock IaaS. However as I found
> ActiveMQ embedded server does not support MQTT transport out of the box
> however it works with AMQP.
> During past months most of us noticed an instability behaviour in MQTT. Once
> the Stratos server is run for several hours the connection to the message
> broker drops.
> Another important reason is that MQTT requires each client to specify a
> globally unique ID. We managed to solve this by generating a random number. A
> UUID is much larger than the limit specified by MQTT. This is not a proper
> way of handling a Client ID in a distributed environment.
> Due to above reasons it would be great if we can introduce factory classes
> for TopicPublisher and TopicSubscriber and add support for AMQP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
