I wasn't sure if it is normal or exceptional behaviour so I started with a
mail...

Now there is issue created at
https://issues.apache.org/jira/browse/QPIDJMS-230 Some fields are yet to be
edited or checked (estimate, labels, priority etc).

2016-12-09 10:01 GMT+01:00 Rob Godfrey <[email protected]>:

> Hi,
>
> unfortunately the mailing list strips attachments from mails - perhaps you
> could raise a JIRA here: https://issues.apache.org/jira/browse/QPIDJMS and
> attach the files to that?
>
> Thanks in advance,
> Rob
>
> On 9 December 2016 at 08:34, Milano Nicolum <[email protected]> wrote:
>
> > *Configuration:* Hi, I'm using ActiveMQ 5.14.1 to connect from a device
> > (running linux derivate OS) to Azure IoT Hub. With Qpid JMS client 0.11.1
> > and protonj 0.15.0 providing AMQPS based JmsConnection implementation.
> I'm
> > using Destination bridges to connect my local queues to remote queues.
> >
> > *Problem description:* For every message I send to the server there is
> > new connection attempt made. I can see those reconnections in Azure IoT
> Hub
> > monitoring, in AMQPS frames logs, qpid log etc. And while I have the same
> > JmsConnection instance active for the whole time, in reality the device
> > keeps connecting and disconnecting for each message, which presents
> > additional load for both IoT Hub and device. Message throughput is really
> > affected by this behaviour.
> >
> > When I try running similar code from my desktop using Qpid JMS client
> > 0.11.1 to send messages, it creates single AmqpFixedProducer at start and
> > disconnects when all messages are sent. I'm not aware of any special
> > settings, both application use JmsConnectionFactory.
> > setForceSyncSend(true).
> >
> > So ActiveMQ or some of its components could be blamed for this. But I
> > would like to know if someone has any experience with similar problem and
> > maybe some idea how to solve it.
> >
> > Thanks!
> >
> > *Attachments: *In logs you can see the device connecting, then some
> > already enqueued messages are sent. Once the initial load is processed,
> one
> > message per minute should be sent.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
>

Reply via email to