[
https://issues.apache.org/jira/browse/AMQNET-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991677#comment-12991677
]
Jim Gomes commented on AMQNET-130:
----------------------------------
I reviewed the exception handlers NmsInputChannelListener::OnExceptionThrown()
and NmsInputSessionChannelListener::OnExceptionThrown(). Both of these
exception handlers have filters set on them to only handle NMSException types.
All other exception types are re-thrown up the exception handler chain. Based
on that review, the recommended behavior is what appears to be coded, therefore
I am closing this bug.
> WCF provider is catching exceptions thrown by WCF service implementation
> ------------------------------------------------------------------------
>
> Key: AMQNET-130
> URL: https://issues.apache.org/jira/browse/AMQNET-130
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: WCF
> Affects Versions: 1.1.0
> Environment: Windows Server 2003 SP1, ActiveMQ 5.2.0, latest
> Apache.NMS and Apache.NMS.ActiveMQ
> Reporter: David Keaveny
> Assignee: Jim Gomes
> Original Estimate: 10h
> Remaining Estimate: 10h
>
> Exceptions that occur within WCF service implementations are being caught by
> the WCF provider and swallowed, so that the service never sees the exception.
> The exceptions *are* logged to the WCF trace log though, if the
> <system.diagnostics /> configuration section is defined.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
