[ https://issues.apache.org/jira/browse/PROTON-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Stitcher resolved PROTON-635. ------------------------------------ Resolution: Fixed Fix Version/s: 0.9 I think the problems that are mentioned in this bug have now been fixed. If not we can reopen this bug. [Or create a linked bug if an new issue is related] > PN_TRANSPORT events not generated in enough places > -------------------------------------------------- > > Key: PROTON-635 > URL: https://issues.apache.org/jira/browse/PROTON-635 > Project: Qpid Proton > Issue Type: Bug > Affects Versions: 0.8 > Reporter: Andrew Stitcher > Assignee: Andrew Stitcher > Fix For: 0.9 > > > In writing a custom driver for Proton I noticed thatthe new events code does > not raise a PN_TRANSPORT event after it receives the incoming AMQP protocol > header. > So a purely event driven driver is not going to send the outgoing protocol > header immediately, but is going to wait until it replies to the next frame > (open). > Also in error scenarios no PN_TRANSPORT is generated after the open/close > frames are generated. > This is going to end badly if the peer is waiting for the protocol header > before sending the open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)