Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5085

[Migration operation] If connector has set factory-class org.hornetq.core.remoting.impl.netty.NettyConnectorFactory then migration operation does not translate it to Artemis equivalent

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.Beta2
    • 10.0.0.Alpha6
    • JMS
    • None

    Description

      We should migrate configuration like:

      <connector name="myconnector">
...
                <factory-class&gt;org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class&gt;
            </connector>

      to:

                      <connector name="myconnector" factory-class="org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnector">
...

      and not to:

                                <connector name="myconnector" factory-class="org.hornetq.core.remoting.impl.netty.NettyConnectorFactory">
...

      The same holds for InVMConnector.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-638 [Migration operation] If connector has set factory-class org.hornetq.core.remoting.impl.netty.NettyConnectorFactory then migration operation does not translate it to Artemis equivalent

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jmesnil1@redhat.com Jeff Mesnil
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: