are durable subscribers so unless they ack, all
> > messages will be retained by the broker.
>
> I am using CleanSession = false to allow for offline queuing.
> Unless there is another way I really need this feature.
>
> > On 5 December 2012 00:27, Christian Webel wrote:
&
Dec 2012 16:20:07 +0100
> Von: "Christian Webel"
> An: users@activemq.apache.org
> Betreff: Re: MQTT and JMS/NMS: ActiveMQ vs. Apollo
> Thanks. That will be my first plugin, so let's try it :-)
>
> Original-Nachricht
> > Datum: Mon, 3 D
oke jmssemantic of
> failover, see; https://issues.apache.org/jira/browse/AMQ-3792
>
> The MQTT use case makes a strong argument for being able to disable this (
> clientID) check and not having to depend on the underlying tcp behaviour
> to
> promptly clean up closed or half
nection 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
>
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
