[
https://issues.apache.org/jira/browse/PROTON-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910266#comment-17910266
]
Timothy A. Bish commented on PROTON-2866:
-----------------------------------------
When using auto reconnect the client will attempt to recover the existing links
however if the remote fails to respond to the attach as the error above
indicates the link is now considered failed and your only recourse is to close
it and attempt to create a new sender and see if the remote decides to respond
this time to the attach request. When a send throws that is an indication that
either the link was closed locally or has become failed due to remote
interactions.
> [protonj2] can't send from client after broker restart
> ------------------------------------------------------
>
> Key: PROTON-2866
> URL: https://issues.apache.org/jira/browse/PROTON-2866
> Project: Qpid Proton
> Issue Type: Bug
> Components: protonj2
> Affects Versions: protonj2-1.0.0-M22
> Reporter: Tomáš Kukosa
> Assignee: Timothy A. Bish
> Priority: Major
>
> Client is connected to AMQP brker and sometimes after broker restart all send
> calls are immediately finished with stored exception and the error is not
> cleared anymore
> {{org.apache.qpid.protonj2.client.exceptions.ClientOperationTimedOutException:
> Link open timed out waiting for remote to respond}}
> {{at
> org.apache.qpid.protonj2.client.impl.ClientLinkType.lambda$handleLocalOpen$1(ClientLinkType.java:309)
> ~[protonj2-client-1.0.0-M22.jar:?]}}
> {{at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at
> io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:156)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:408)
> ~[netty-transport-classes-epoll-4.1.113.Final.jar:4.1.113.Final]}}
> {{at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> ~[netty-common-4.1.115.Final.jar:4.1.115.Final]}}
> {{at java.base/java.lang.Thread.run(Unknown Source) ~[?:?]}}
> Unfortunately I can not reproduce it. It always work well when I start
> investigating it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
