[
https://issues.apache.org/jira/browse/QPIDJMS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113178#comment-17113178
]
yair ogen commented on QPIDJMS-507:
-----------------------------------
[~robbie] Why not at least honor the send timeout? so the wait call in the sync
method uses wait like is done in the close flow (where close timeout is indeed
honored)
> async send isn't really async
> -----------------------------
>
> Key: QPIDJMS-507
> URL: https://issues.apache.org/jira/browse/QPIDJMS-507
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Reporter: yair ogen
> Priority: Critical
>
> When calling send with CompletionListener, the api indicates this create an
> async call.
> However, it seems that internally, there is still blocking.
> JmsSession has this code:
> {code:java}
> transactionContext.send(connection, envelope, null)
> {code}
> This in turn, calls:
> {code:java}
> connection.send(envelope, new ProviderSynchronization() {
> {code}
> And in there:
> {code:java}
> try {
> provider.send(envelope, request);
> request.sync();
> } finally {
> requests.remove(request);
> }
> {code}
> the sync call is blocking. so it seems there is no real async implementation?
> Also, the sync is called without timeout even if user sets a
> {code:java}
> sendTimeout{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
