[
https://issues.apache.org/jira/browse/QPIDJMS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941270#comment-16941270
]
ASF subversion and git services commented on QPIDJMS-476:
---------------------------------------------------------
Commit e04e3f847859cddecc4704d6a9c628cf435bf97f in qpid-jms's branch
refs/heads/master from Timothy Bish
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=e04e3f8 ]
QPIDJMS-476 Enhance anonymous fallback producer to allow asynchronous sends
Improves performance of anonymous fallback producer mode by allowing
asynchronous sends and sends that reuse existing cache anonymous
fallback producer instances avoiding the need for open -> send -> close
on each send.
> Improve send performance of anonymous fallback producer
> -------------------------------------------------------
>
> Key: QPIDJMS-476
> URL: https://issues.apache.org/jira/browse/QPIDJMS-476
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.46.0
> Reporter: Timothy A. Bish
> Assignee: Timothy A. Bish
> Priority: Minor
> Fix For: 0.47.0
>
>
> For remotes that do not report support for the anonymous relay we implement a
> fallback mechanism that creates a single sender link that is opened on send
> and close on completion of the send (remote sends disposition). This
> mechanism essentially makes ever send using the anonymous fallback mechanism
> synchronous with the overhead of Attach -> Transfer -> Detach for each call
> to send. We can improve this mechanism and also allow for asynchronous sends
> both from the JMS 1.1 send methods and from the JMS completion send methods
> as is currently done when the anonymous relay is supported. By allowing for
> caching of sender links we can reduce the number of attach and detach cycles
> for sends that encompass a fixed set of addresses as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
