You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Rafael H. Schloming (JIRA)" <ji...@apache.org> on 2012/12/13 22:38:13 UTC

[jira] [Resolved] (PROTON-164) Messenger not handling connection errors properly

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

Rafael H. Schloming resolved PROTON-164.
----------------------------------------

    Resolution: Fixed
      Assignee: Rafael H. Schloming
    
> Messenger not handling connection errors properly
> -------------------------------------------------
>
>                 Key: PROTON-164
>                 URL: https://issues.apache.org/jira/browse/PROTON-164
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.2
>            Reporter: Affan Dar
>            Assignee: Rafael H. Schloming
>              Labels: messenger
>             Fix For: 0.3
>
>
> There seems to be an issue with redirects and maybe connection level errors in general where the client seems to get stuck.
> E.g. in the following scenario where the server sends back a CLOSE frame to the proton client with the ‘redirect’ error. The client should sent back a CLOSE frame but instead it gets stuck (the send sample app does not proceed and eventually you have to Ctrl+C it).
> Connected to INT7-SN1-008-23257-0-9.servicebus.int7.windows-int.net:5671
>     -> SASL
> [0x25dd720:0] -> SASL-INIT @65 [:PLAIN, b"XXXX"]
>     <- SASL
> [0x25dd720:0] <- SASL-MECHANISMS @64 [@PN_SYMBOL[:PLAIN, :EXTERNAL]]
> [0x25dd720:0] <- SASL-OUTCOME @68 [0, b"Welcome!"]
>     -> AMQP
> [0x25d7e60:0] -> OPEN @16 ["0c753746-89de-4c4c-bd17-fb6d6e36a081", "INT7-SN1-008-23257-0-9.servicebus.int7.windows-int.net", null, null, null, null, null, null, null]
> [0x25d7e60:1] -> BEGIN @17 [null, 0, 1024, 1024]
> [0x25d7e60:1] -> ATTACH @18 ["sender-xxx", 1, false, null, null, @40 ["q1", 0, null, 0, false, null, null, null, null, null, null], @41 ["q1", 0, null, 0, false, null, null], null, null, 0]
>     <- AMQP
> [0x25d7e60:0] <- CLOSE @24 [@29 [:"amqp:connection:redirect", "Exception of type 'Microsoft.ServiceBus.Messaging.Amqp.AmqpException' was thrown..TrackingId:eb33c8f31c9f4b0c9a2c8aa7c2622ca7_G3,TimeStamp:11/27/2012 6:06:24 AM", {:hostname="INT7-SN1-008-23257-0-9.servicebus.int7.windows-int.net", :"network-host"="70.37.116.39", :port=5671}]]
> Debugging through the code a little bit, it seems like the client is expecting to receive more data from the socket and keeps on waiting since the default timeout is infinite.
> Please let me know if more details are required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira