stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anuruddha Lanka Liyanarachchi (JIRA)" <>
Subject [jira] [Updated] (STRATOS-1168) Introduce Ability to Switch Messaging Transports and Add Support for AMQP
Date Thu, 14 May 2015 09:42:59 GMT


Anuruddha Lanka Liyanarachchi updated STRATOS-1168:
    Fix Version/s: 4.1.0 RC1

> Introduce Ability to Switch Messaging Transports and Add Support for AMQP
> -------------------------------------------------------------------------
>                 Key: STRATOS-1168
>                 URL:
>             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 Beta, 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
> 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

View raw message