[
https://issues.apache.org/jira/browse/PROTON-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2278:
-----------------------------------
Summary: [c] Raw connection API trying to give back buffers after emitting
the PN_RAW_CONNECTION_DISCONNECTED event (was: [proton-c] Raw connection API
trying to give back buffers after emitting the PN_RAW_CONNECTION_DISCONNECTED
event)
> [c] Raw connection API trying to give back buffers after emitting the
> PN_RAW_CONNECTION_DISCONNECTED event
> ----------------------------------------------------------------------------------------------------------
>
> Key: PROTON-2278
> URL: https://issues.apache.org/jira/browse/PROTON-2278
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.32.0
> Reporter: Ganesh Murthy
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.33.0
>
>
> The router tries to make a raw socket connection to an nginx server on port
> 80 but that nginx server is not running. The raw socket connection fails (as
> expected). I see a PN_RAW_CONNECTION_DISCONNECTED event (also expected). But
> I see PN_RAW_CONNECTION_NEED_WRITE_BUFFERS and
> PN_RAW_CONNECTION_NEED_READ_BUFFERS events *after* the
> PN_RAW_CONNECTION_DISCONNECTED event as seen below in the log -
>
> {noformat}
> 2020-09-23 11:22:40.006736 -0400 HTTP_ADAPTOR (trace) [C1]
> PN_RAW_CONNECTION_DISCONNECTED
> 2020-09-23 11:22:40.006792 -0400 HTTP_ADAPTOR (trace) [C1]
> PN_RAW_CONNECTION_NEED_WRITE_BUFFERS Need write buffers
> 2020-09-23 11:22:40.006802 -0400 HTTP_ADAPTOR (trace) [C1]
> PN_RAW_CONNECTION_NEED_READ_BUFFERS Need read buffers {noformat}
>
> The documentation on pn_raw_connection_close() seems to suggest that
> PN_RAW_CONNECTION_DISCONNECTED will be the very last event emitted on a
> connection.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
