You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2008/10/27 21:30:52 UTC

[jira] Resolved: (AMQNET-118) TransportFactory fails to connect to any service due to exception

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

Jim Gomes resolved AMQNET-118.
------------------------------

      Assignee: Jim Gomes  (was: James Strachan)
    Resolution: Fixed

> TransportFactory fails to connect to any service due to exception
> -----------------------------------------------------------------
>
>                 Key: AMQNET-118
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-118
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>    Affects Versions: 1.1
>         Environment: Windows XP .NET 2.0
>            Reporter: Allan Schrum
>            Assignee: Jim Gomes
>            Priority: Blocker
>             Fix For: 1.1
>
>         Attachments: Apache.NMS.ActiveMQ.707803.diff
>
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> The TransportFactory delays instantiating the underlying TransportFactories until they are used. The current logic checks the dictionary factoryCache to see if the TransportFactory exists. Failing that it adds the TransportFactory and continues on. Unfortunately, the System.Collections.Generic.Dictionary class throws an exception when an item that does not exist is selected. This causes all connections to abort during the top-level CreateConnection() call.
> Attached is a patch to TransportFactory.cs that fixes this problem.
> I grant ASF license to this patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.