[
https://issues.apache.org/jira/browse/PROTON-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed PROTON-2173.
---
Resolution: Not A Bug
> [c, cpp] Idle connections closed with TCP FIN cause framing errors
>
[
https://issues.apache.org/jira/browse/PROTON-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097647#comment-17097647
]
Justin Ross commented on PROTON-2173:
-
Proton is behaving as intended here. If the remote peer
Justin Ross created PROTON-2205:
---
Summary: [c] Use a descriptive, legal error condition for abruptly
closed connections
Key: PROTON-2205
URL: https://issues.apache.org/jira/browse/PROTON-2205
Project:
[
https://issues.apache.org/jira/browse/PROTON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097646#comment-17097646
]
Justin Ross commented on PROTON-2205:
-
See PROTON-2173 for the origin of this.
> [c] Use a
[
https://issues.apache.org/jira/browse/PROTON-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed PROTON-2193.
---
Resolution: Incomplete
> Python MessagingHandler does not call on_connection_error on error
>
[
https://issues.apache.org/jira/browse/PROTON-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097634#comment-17097634
]
Justin Ross commented on PROTON-2193:
-
This is not in general the case. The Python client does call
Justin Ross created PROTON-2204:
---
Summary: [python] Document that receiving connection:forced dos
not fire on_connection_error
Key: PROTON-2204
URL: https://issues.apache.org/jira/browse/PROTON-2204
[
https://issues.apache.org/jira/browse/PROTON-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2204:
Summary: [python] Document that receiving connection:forced does not fire
on_connection_error
[
https://issues.apache.org/jira/browse/DISPATCH-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1391:
Description:
When the following program is run against the router, it crashes -
[
https://issues.apache.org/jira/browse/PROTON-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2203:
---
Fix Version/s: proton-c-0.31.0
> Assertion error in new proactor code
>
[
https://issues.apache.org/jira/browse/PROTON-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097482#comment-17097482
]
ASF subversion and git services commented on PROTON-2201:
-
Commit
[
https://issues.apache.org/jira/browse/PROTON-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097483#comment-17097483
]
ASF subversion and git services commented on PROTON-2154:
-
Commit
[
https://issues.apache.org/jira/browse/PROTON-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097481#comment-17097481
]
ASF subversion and git services commented on PROTON-2154:
-
Commit
[
https://issues.apache.org/jira/browse/DISPATCH-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1637:
Description:
Steps to reproduce -
# Start the router with a default config file,
14 matches
Mail list logo