[PROTON-483] detach with closed=false (or unspecified) not handled

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.6
• Component/s: proton-c
• Assignee: Dominic Evans
• Reporter: Gordon Sim
• Created: 02/Jan/14 12:28
• Updated: 08/Jan/16 10:57
• Resolved: 04/Feb/15 13:14

Description

If an application using proton-c receives a detach frame where the closed field is not set to true, then the state of the link doesn't change and the application is essentially unaware that anything has been received (and consequently can't respond).

From transport.c (line 882):

  if (closed)
  {
    PN_SET_REMOTE(link->endpoint.state, PN_REMOTE_CLOSED);
  } else {
    // TODO: implement
  }

Issue Links

• duplicates: PROTON-677 proton-c: transport incorrectly detaches all links with closed=true by default
• is related to: QPID-5439 [AMQP 1.0 JMS client] Client hangs during connection.close()