[jira] [Assigned] (AMQ-9414) Remove masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9414: --- Assignee: Matt Pavlovich > Remove masterslave network connector uri > > > Key: AMQ-9414 > URL: https://issues.apache.org/jira/browse/AMQ-9414 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Minor > Fix For: 7.0.0 > > > 6.x added @Deprecated for removal, finish removing in 7.0.0 > ref: [AMQ-8593] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9414) Remove masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9414: Fix Version/s: 7.0.0 > Remove masterslave network connector uri > > > Key: AMQ-9414 > URL: https://issues.apache.org/jira/browse/AMQ-9414 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Priority: Minor > Fix For: 7.0.0 > > > 6.x added @Deprecated for removal, finish removing in 7.0.0 > ref: [AMQ-8593] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9414) Remove masterslave network connector uri
Matt Pavlovich created AMQ-9414: --- Summary: Remove masterslave network connector uri Key: AMQ-9414 URL: https://issues.apache.org/jira/browse/AMQ-9414 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich 6.x added @Deprecated for removal, finish removing in 7.0.0 ref: [AMQ-8593] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-8593) Add a new staticfailover and deprecate masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-8593: --- Assignee: Matt Pavlovich (was: Jean-Baptiste Onofré) > Add a new staticfailover and deprecate masterslave network connector uri > - > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the > [IETF|https://tools.ietf.org/id/draft-knodel-terminology-02.html] and > [inclusivenaming.org|https://inclusivenaming.org/word-lists/tier-1/] which is > supported by companies such as Cisco, Intel, and RedHat. > If we can't come to an agreement on Leader/Follower or some other > nomenclature I will, at the very least, create a follow up PR to remove the > masterslave transport since it is just a convenience method to use > static+failover with ?randomize=false=0. > This change leaves the masterslave: transport in place but provides a new > alias leaderfollower: for now but we can easily remove it in 5.18.0. > PR: https://github.com/apache/activemq/pull/835 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-8593) Add a new staticfailover and deprecate masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8593: Fix Version/s: 6.1.0 > Add a new staticfailover and deprecate masterslave network connector uri > - > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Matt Pavlovich >Priority: Major > Fix For: 6.1.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the > [IETF|https://tools.ietf.org/id/draft-knodel-terminology-02.html] and > [inclusivenaming.org|https://inclusivenaming.org/word-lists/tier-1/] which is > supported by companies such as Cisco, Intel, and RedHat. > If we can't come to an agreement on Leader/Follower or some other > nomenclature I will, at the very least, create a follow up PR to remove the > masterslave transport since it is just a convenience method to use > static+failover with ?randomize=false=0. > This change leaves the masterslave: transport in place but provides a new > alias leaderfollower: for now but we can easily remove it in 5.18.0. > PR: https://github.com/apache/activemq/pull/835 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (AMQ-8593) Add a new staticfailover and deprecate masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reopened AMQ-8593: - This can be added without having to wait for other major breaking changes (aka v7.0.0) > Add a new staticfailover and deprecate masterslave network connector uri > - > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the > [IETF|https://tools.ietf.org/id/draft-knodel-terminology-02.html] and > [inclusivenaming.org|https://inclusivenaming.org/word-lists/tier-1/] which is > supported by companies such as Cisco, Intel, and RedHat. > If we can't come to an agreement on Leader/Follower or some other > nomenclature I will, at the very least, create a follow up PR to remove the > masterslave transport since it is just a convenience method to use > static+failover with ?randomize=false=0. > This change leaves the masterslave: transport in place but provides a new > alias leaderfollower: for now but we can easily remove it in 5.18.0. > PR: https://github.com/apache/activemq/pull/835 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-8593) Add a new staticfailover and deprecate masterslave network connector uri
[ https://issues.apache.org/jira/browse/AMQ-8593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-8593: Summary: Add a new staticfailover and deprecate masterslave network connector uri (was: Deprecate masterslave discovery agent and add a new leaderfollower discovery agent) > Add a new staticfailover and deprecate masterslave network connector uri > - > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Jean-Baptiste Onofré >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the > [IETF|https://tools.ietf.org/id/draft-knodel-terminology-02.html] and > [inclusivenaming.org|https://inclusivenaming.org/word-lists/tier-1/] which is > supported by companies such as Cisco, Intel, and RedHat. > If we can't come to an agreement on Leader/Follower or some other > nomenclature I will, at the very least, create a follow up PR to remove the > masterslave transport since it is just a convenience method to use > static+failover with ?randomize=false=0. > This change leaves the masterslave: transport in place but provides a new > alias leaderfollower: for now but we can easily remove it in 5.18.0. > PR: https://github.com/apache/activemq/pull/835 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-8593) Deprecate masterslave discovery agent and add a new leaderfollower discovery agent
[ https://issues.apache.org/jira/browse/AMQ-8593?focusedWorklogId=895256=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895256 ] ASF GitHub Bot logged work on AMQ-8593: --- Author: ASF GitHub Bot Created on: 12/Dec/23 15:56 Start Date: 12/Dec/23 15:56 Worklog Time Spent: 10m Work Description: lucastetreault opened a new pull request, #835: URL: https://github.com/apache/activemq/pull/835 This [tweet](https://twitter.com/owenblacker/status/1517156221207212032) raised the issue of non-inclusive terminology in the [AWS docs](https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors) and suggested that we should replace masterslave with an more inclusive name for the network connector transport. The AWS docs refer to a feature of ActiveMQ that is a convenience discovery agent: https://activemq.apache.org/networks-of-brokers#masterslave-discovery Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 [AMQ-7514](https://issues.apache.org/jira/browse/AMQ-7514) and there have been some attempts at making some changes (https://github.com/apache/activemq/pull/679, https://github.com/apache/activemq/pull/714, https://github.com/apache/activemq/pull/788) however we have not been able to come to an agreement on nomenclature so these efforts seem to have stalled out. If we are able to come to an agreement on nomenclature in this PR, we can move forward with removing more non-inclusive terminology on the website (I will follow up with some PRs to the website), in discussions with the community and of course in this codebase. This will remove adoption barriers and make ActiveMQ a more approachable and inclusive project for everyone! Other Apache projects such as Solr and Kafka have moved from master/slave to leader/follower. Leader/follower is also recommended by the [IETF](https://tools.ietf.org/id/draft-knodel-terminology-02.html) and [inclusivenaming.org](https://inclusivenaming.org/word-lists/tier-1/) which is supported by companies such as Cisco, Intel, and RedHat. If we can't come to an agreement on Leader/Follower or some other nomenclature I will, at the very least, create a follow up PR to remove the masterslave transport since it is just a convenience method to use static+failover with ?randomize=false=0. This change leaves the masterslave: transport in place but provides a new alias leaderfollower: for now but we can easily remove it in 5.18.0. Issue Time Tracking --- Worklog Id: (was: 895256) Time Spent: 3h 20m (was: 3h 10m) > Deprecate masterslave discovery agent and add a new leaderfollower discovery > agent > -- > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Jean-Baptiste Onofré >Priority: Major > Time Spent: 3h 20m > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the >
[jira] [Work logged] (AMQ-8593) Deprecate masterslave discovery agent and add a new leaderfollower discovery agent
[ https://issues.apache.org/jira/browse/AMQ-8593?focusedWorklogId=895257=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895257 ] ASF GitHub Bot logged work on AMQ-8593: --- Author: ASF GitHub Bot Created on: 12/Dec/23 15:56 Start Date: 12/Dec/23 15:56 Worklog Time Spent: 10m Work Description: mattrpav commented on PR #835: URL: https://github.com/apache/activemq/pull/835#issuecomment-1852321975 Re-opening Issue Time Tracking --- Worklog Id: (was: 895257) Time Spent: 3.5h (was: 3h 20m) > Deprecate masterslave discovery agent and add a new leaderfollower discovery > agent > -- > > Key: AMQ-8593 > URL: https://issues.apache.org/jira/browse/AMQ-8593 > Project: ActiveMQ > Issue Type: Task > Components: Network of Brokers >Affects Versions: 5.17.2 >Reporter: Lucas Tétreault >Assignee: Jean-Baptiste Onofré >Priority: Major > Time Spent: 3.5h > Remaining Estimate: 0h > > This [tweet|https://twitter.com/owenblacker/status/1517156221207212032] > raised the issue of non-inclusive terminology in the [AWS > docs|https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-creating-configuring-network-of-brokers.html#creating-configuring-network-of-brokers-configure-network-connectors] > and suggested that we should replace masterslave with an more inclusive name > for the network connector transport. The AWS docs refer to a feature of > ActiveMQ that is a convenience discovery agent: > [https://activemq.apache.org/networks-of-brokers#masterslave-discovery] > Replacing master/slave nomenclature in ActiveMQ was raised in July 2020 > AMQ-7514 and there have been some attempts at making some changes > ([#679|https://github.com/apache/activemq/pull/679], > [#714|https://github.com/apache/activemq/pull/714], > [#788|https://github.com/apache/activemq/pull/788]) however we have not been > able to come to an agreement on nomenclature so these efforts seem to have > stalled out. > If we are able to come to an agreement on nomenclature in this PR, we can > move forward with removing more non-inclusive terminology on the website (I > will follow up with some PRs to the website), in discussions with the > community and of course in this codebase. This will remove adoption barriers > and make ActiveMQ a more approachable and inclusive project for everyone! > Other Apache projects such as Solr and Kafka have moved from master/slave to > leader/follower. Leader/follower is also recommended by the > [IETF|https://tools.ietf.org/id/draft-knodel-terminology-02.html] and > [inclusivenaming.org|https://inclusivenaming.org/word-lists/tier-1/] which is > supported by companies such as Cisco, Intel, and RedHat. > If we can't come to an agreement on Leader/Follower or some other > nomenclature I will, at the very least, create a follow up PR to remove the > masterslave transport since it is just a convenience method to use > static+failover with ?randomize=false=0. > This change leaves the masterslave: transport in place but provides a new > alias leaderfollower: for now but we can easily remove it in 5.18.0. > PR: https://github.com/apache/activemq/pull/835 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (OPENWIRE-73) Add tests for all commands to verify universal marshaller byte equivalency with all versions
Christopher L. Shannon created OPENWIRE-73: -- Summary: Add tests for all commands to verify universal marshaller byte equivalency with all versions Key: OPENWIRE-73 URL: https://issues.apache.org/jira/browse/OPENWIRE-73 Project: ActiveMQ OpenWire Issue Type: Task Reporter: Christopher L. Shannon Fix For: 1.0.0 Right now the OpenWire interop tests try and check that the new commands and marshallers produce the same bytes as the existing marshallers that are in activemq-client and currently used. This is done indirectly by using the new marshallers to send commands to an embedded broker which reads them. This works but it doesn't cover all cases and requires running a broker. Instead, a better approach would be to simply check the resulting bytes produced are exactly equivalent and just test the different marshallers without a broker. We should create tests for every single OpenWire command and version that will check that the marshalled bytes are exactly equivalent as the existing verison in use today with activemq-client. In theory these tests could be generated automatically so we can explore that but we may not need to as we really only need to create the tests once for the legacy versions today because going forward with the universal marshaller being used there won't be any new legacy versions and we will keep the new tests up to date. Also note that this project includes a legacy module with copies of the legacy marshallers but still a bit refactored and repackaged. So we should likely run the tests to verify the universal marshaller output matches both the re-packaged legacy module as well as the legacy marshallers that are packaged currently with activemq-client. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (AMQNET-664) No IConnectionFactory implementation found
[
https://issues.apache.org/jira/browse/AMQNET-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795711#comment-17795711
]
Seyyed Soroosh Hosseinalipour edited comment on AMQNET-664 at 12/12/23 12:16 PM:
-
ITNOA
I have same problem for tcp connection, in 2.1.0 version.
Which version fix this problem?
was (Author: soroshsabz):
ITNOA
I have same problem for tcp connection, in 2.1.0 version.
> No IConnectionFactory implementation found
> --
>
> Key: AMQNET-664
> URL: https://issues.apache.org/jira/browse/AMQNET-664
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
>Affects Versions: OpenWire-1.8.0
>Reporter: Vagelis
>Priority: Major
>
> When I try to create the connection factory I get the error "No
> IConnectionFactory implementation found".
> I followed this example:
>
> [https://activemq.apache.org/components/nms/examples/nms-simple-asynchronous-consumer-example]
> I also tried with "new ActiveMQ.ConnectionFactory(uri)" with the same result.
> I use the below packages:
> Apache.NMS -Version 2.0.0
> Apache.NMS.ActiveMQ -Version 1.8.0
> Is this required? Is there a sample config file?
>
> {{// NOTE: ensure the nmsprovider-activemq.config file exists in the
> executable folder.}}
> {{Edit: I use nuget packages}}
> {{The full message:}}
> {{Apache.NMS.NMSConnectionException: 'Could not create the IConnectionFactory
> implementation: Method 'CreateConnectionAsync' in type
> 'Apache.NMS.ActiveMQ.ConnectionFactory' from assembly 'Apache.NMS.ActiveMQ,
> Version=1.8.0.0, Culture=neutral, PublicKeyToken=82756feee3957618' does not
> have an implementation.'}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (AMQNET-664) No IConnectionFactory implementation found
[
https://issues.apache.org/jira/browse/AMQNET-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795711#comment-17795711
]
Seyyed Soroosh Hosseinalipour commented on AMQNET-664:
--
ITNOA
I have same problem for tcp connection, in 2.1.0 version.
> No IConnectionFactory implementation found
> --
>
> Key: AMQNET-664
> URL: https://issues.apache.org/jira/browse/AMQNET-664
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
>Affects Versions: OpenWire-1.8.0
>Reporter: Vagelis
>Priority: Major
>
> When I try to create the connection factory I get the error "No
> IConnectionFactory implementation found".
> I followed this example:
>
> [https://activemq.apache.org/components/nms/examples/nms-simple-asynchronous-consumer-example]
> I also tried with "new ActiveMQ.ConnectionFactory(uri)" with the same result.
> I use the below packages:
> Apache.NMS -Version 2.0.0
> Apache.NMS.ActiveMQ -Version 1.8.0
> Is this required? Is there a sample config file?
>
> {{// NOTE: ensure the nmsprovider-activemq.config file exists in the
> executable folder.}}
> {{Edit: I use nuget packages}}
> {{The full message:}}
> {{Apache.NMS.NMSConnectionException: 'Could not create the IConnectionFactory
> implementation: Method 'CreateConnectionAsync' in type
> 'Apache.NMS.ActiveMQ.ConnectionFactory' from assembly 'Apache.NMS.ActiveMQ,
> Version=1.8.0.0, Culture=neutral, PublicKeyToken=82756feee3957618' does not
> have an implementation.'}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
