[
https://issues.apache.org/jira/browse/AMQNET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Winograd closed AMQNET-389.
---------------------------------
Resolution: Not A Problem
This was an issue in 1.5 branch but is not an issue in the current trunk.
> Implementing a catch for an empty catch clause in the Connection.cs
> CheckConnected() method at line 777.
> -----------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-389
> URL: https://issues.apache.org/jira/browse/AMQNET-389
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ, NMS
> Affects Versions: 1.5.5
> Environment: .net 3.5 on win 7 in a vbox vm.
> Reporter: Ethan Winograd
> Assignee: Jim Gomes
> Labels: newbie, patch
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> This catch seems to work. I know its hacky matching on string but there is
> not an exception Id.
> catch (Exception ex1)
> {
>
> if(ex1.Message.Equals("java.lang.SecurityException : User name or password is
> invalid.\n"))
> {
> throw new
> ConnectionFailedException("java.lang.SecurityException : User name or
> password is invalid.", ex1);
> }
> }
> would love to get involved - will modify approach to suit, re patches, etc...
> just wanted to get this in to get ball rolling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
