qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Patierno (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped
Date Fri, 31 Mar 2017 14:06:42 GMT

     [ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paolo Patierno updated DISPATCH-506:
------------------------------------
    Comment: was deleted

(was: I'm re-opening it because after the fix the router sends the detach with closed=false,
this is what I see :

[0x1f0bc80]:0 -> @detach(22) [handle=0, closed=false, error=@error(29) [condition=:"qd:routed-link-lost",
description="Connectivity to the peer container was lost"]]
)

> Detach with no "error" sent by router on client TCP connection dropped
> ----------------------------------------------------------------------
>
>                 Key: DISPATCH-506
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-506
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.6.1
>            Reporter: Paolo Patierno
>            Assignee: Ted Ross
>             Fix For: 0.8.0
>
>
> Hi,
> I got the following scenario.
> A router with a link routing configured on address "my_queue".
> A broker hosting "my_queue".
> A Python receiver connected to that queue through the link routing provided by the router.
> If I kill the receiver, so the TCP connection between client and router is dropped, the
client (of course) doesn't send a detach to the broker for the link but the router is in charge
to do that.
> What happens is that this detach message doesn't contain an "error" field in order to
distinguish between a clean detach from the client or a detach sent by router due to client
"brute" disconnection.
> Following the trace I have :
> [0x16e07f0]:  <- EOS
> [0x16e07f0]:  -> EOS
> Closed 127.0.0.1:42308
> Unexpected poll events: 0020 on 127.0.0.1:42308
> [0x16cf470]:0 -> @detach(22) [handle=0, closed=true]
> [0x16cf470]:0 <- @detach(22) [handle=0, closed=true]
> [0x16cf470]:0 -> @end(23) []
> [0x16cf470]:0 <- @end(23) []
> I think that it could make sense that router sends a detach with "error" when something
like that happens.
> The current is a bug or a behavior ?
> Thanks,
> Paolo.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message