qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuck Rolke (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-4426) C++ Messaging Client .NET Binding callback server example fails to relay exceptions to main loop
Date Wed, 07 Nov 2012 17:27:18 GMT

     [ https://issues.apache.org/jira/browse/QPID-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chuck Rolke resolved QPID-4426.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.19

Fixed in r1406713
                
> C++ Messaging Client .NET Binding callback server example fails to relay exceptions to
main loop
> ------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4426
>                 URL: https://issues.apache.org/jira/browse/QPID-4426
>             Project: Qpid
>          Issue Type: Bug
>          Components: Dot Net Client
>    Affects Versions: 0.18
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>             Fix For: 0.19
>
>
> The Messaging Client .NET Binding provides an example callback server called sessionreceiver.
It creates a thread and calls a session's NextReceiver function. If NextReceiver encounters
any kind of exception then that exception goes unhandled.
> The proposed fix is to add a SessionException() callback to the interface. Then the NextReceiver
is placed in a try-catch block and caught exceptions are sent through the new callback.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message