[
https://issues.apache.org/jira/browse/DISPATCH-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764667#comment-15764667
]
ASF GitHub Bot commented on DISPATCH-598:
-----------------------------------------
GitHub user ganeshmurthy opened a pull request:
https://github.com/apache/qpid-dispatch/pull/131
DISPATCH-598 - Added code to temporarily fix the crash that is being …
…caused when PN_LINK_REMOTE_CLOSE and PN_SESSION_REMOTE_CLOSE events come
in on the same collector loop. A more comprehensive fix is being worked on for
the 0.9 release
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-598
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-dispatch/pull/131.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #131
----
commit 052b508d13724b09e3d33ba135aa0daee1f9ad68
Author: Ganesh Murthy <[email protected]>
Date: 2016-12-20T16:55:52Z
DISPATCH-598 - Added code to temporarily fix the crash that is being caused
when PN_LINK_REMOTE_CLOSE and PN_SESSION_REMOTE_CLOSE events come in on the
same collector loop. A more comprehensive fix is being worked on for the 0.9
release
----
> Router crash when calling sender and session close methods in onLinkFLow()
> --------------------------------------------------------------------------
>
> Key: DISPATCH-598
> URL: https://issues.apache.org/jira/browse/DISPATCH-598
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 0.7.0
> Environment: Centos 7. Java 1.8
> Reporter: Rohan Mars
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: test-app-reactor-core.tar.gz
>
>
> Closing session/connection in sender onLinkFlow() causes router to crash
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
