[
https://issues.apache.org/jira/browse/QPIDJMS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719034#comment-16719034
]
Robbie Gemmell commented on QPIDJMS-438:
----------------------------------------
Ok, the logging shows the producer links are actually being closed after send,
though not because your application code is closing the producer.
In AMQP 1.0 sending links be established to a given 'address' of a 'node' (e.g
queue). An extension mechanism was defined to allow producing to an 'anonymous
relay' node for use with things like JMS anonymous producers. Service Bus is
not advertising support for the mechanism, and so the client is falling back to
an behaviour which opens and closes sender links as messages are produced using
the anonymous producer. As a result, when inbetween sends, your session really
is 'unused' and so ServiceBus does decide to close it. Can you use
fixed-address producers?
> Remotely closed session are not removed from the connection
> -----------------------------------------------------------
>
> Key: QPIDJMS-438
> URL: https://issues.apache.org/jira/browse/QPIDJMS-438
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.39.0
> Reporter: David De Franco
> Priority: Major
> Attachments: amqp.log, out-of-memory1.PNG, out-of-memory2.PNG
>
>
> We use Qpid JMS to connect to the Azure service bus.
> In our applications we cache the connections in a pool and cache a session
> for each connection for sending messages.
> When Azure believes the connection is idle for 5 minutes it is remotely
> closed. Resulting in closing the cached session in the application. The
> application responds by replacing the cached session with a newly created
> session.
> The problem here is that the closed sessions are not removed from the
> connection. Eventually resulting in an OutOfMemoryError.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
