qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milan Nikl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-230) AmqpFixedProducer created for every message sent
Date Fri, 09 Dec 2016 11:27:59 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735062#comment-15735062
] 

Milan Nikl commented on QPIDJMS-230:
------------------------------------

It it was only a server settings problem, I would see the same reconnecting issue on my desktop
every time I ran any application using Qpid JMS client, right?

As I see this problem only on my device I wonder what is actually causing it. Should I change
the ActiveMQ settings somehow, should I refrain from using JMSConnector or DestinationBridges?

Or can some system settings affect the reconnection policy? I admit I have no idea why messaging
behaves differently in the two applications I'm using.

> AmqpFixedProducer created for every message sent
> ------------------------------------------------
>
>                 Key: QPIDJMS-230
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-230
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.11.1
>            Reporter: Milan Nikl
>            Priority: Minor
>              Labels: performance
>         Attachments: amqps_frames.log, apache.qpid.log
>
>
> *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.
> Originaly filed in http://qpid.2158936.n2.nabble.com/AmqpFixedProducer-created-for-every-message-sent-td7655816.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message