activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: MQTT and JMS/NMS: ActiveMQ vs. Apollo
Date Mon, 03 Dec 2012 12:44:55 GMT
On the Apollo side, the "rich protocol" conversions aren't there yet:

For ActiveMQ 5.7 seems like the dead connection isn't being cleaned up
properly when it goes away. Is this something you can reproduce?

On Mon, Dec 3, 2012 at 4:56 AM, Christian Webel <> wrote:

> Hi,
> I'm currently trying to add mobile clients (Android, eclipse paho client
> API) via the MQTT protocol to our ActiveMQ and Apollo server. The other
> clients use JMS/NMS. Transport connectors are correctly defined.
> I have experienced following problems:
> Using ActiveMQ 5.7:
> Everthing seems to be OK. But when the mobile device looses connection to
> the server (e.g. in area with no reception) and reconnects, I get an
> javax.jms.InvalidClientIDException: Broker: localhost - Client: XXX already
> connected from tcp:YYY. As the client ID is used by the server to identify
> a client when it reconnects, the client has to use the same identifier
> between connections if durable subscriptions are used.
> Can I somehow disable this clientID check in ActiveMQ? Any idea how to
> solve that issue?
> Using Apollo:
> Reconnect works fine, but interacting bezween JMS/NMS and mqtt clients is
> not possible. It seems that there is no proper protocol conversion
> implemented since I receive the JMS client data in mqtt as a large binary
> blob. Vice versa, I receive  nothing. From mqtt to mqtt clients, everthing
> works perfect!
> Any ideas on that?
> Every little help is appreciated!
> Best regards,
> Christian

*Christian Posta*
twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message