activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Jackson (JIRA)" <>
Subject [jira] [Commented] (AMQNET-337) Creating ConnectionFactory fails if ActiveMQ assembly has long path
Date Wed, 20 Jul 2011 09:10:58 GMT


Simon Jackson commented on AMQNET-337:

The path which is being tested is generated by the library, and it uses a config file if it
exists in that place.  If not then other places are tried.

So any path which is too long can just be ignored when searching for config.

Config can still be applied, and it will stop crashing.

> Creating ConnectionFactory fails if ActiveMQ assembly has long path
> -------------------------------------------------------------------
>                 Key: AMQNET-337
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>            Reporter: Simon Jackson
>            Assignee: Jim Gomes
>            Priority: Trivial
> If the path of the directory containing Apache.NMS.DLL is long then creating the NMSConnectionFactory
can fail with
> PathTooLongException.
> ProviderUri:
> "tcp://"
> Path to the NMS dll was:
> C:\Users\simon.HQ\AppData\Local\Temp\4e913663-806b-4885-a6a0-14568b865815\4e913663-806b-4885-a6a0-14568b865815\assembly\dl3\8719cfea\776f9635_4f3dcc01\Apache.NMS.DLL
> Looks like the config document is being looked for when it would be too long.
> Path was generated by Resharper's xunit test runner.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message