Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-116

Microcontainer does not always choose the right constructor when creating ModClusterService

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.1.0.CR1
    • 1.1.0.Beta1
    • None
    • None
    • Workaround Exists
    • Hide

      Edit mod_cluster-jboss-beans.xml and add type attributes to the constructor parameters to explicitly control which constructor the microcontainer will use.

      Show
      Edit mod_cluster-jboss-beans.xml and add type attributes to the constructor parameters to explicitly control which constructor the microcontainer will use.

      A user encountered the following error when attempting to start EAP 5.0.0 w/mod_cluster 1.1.0.Beta1:

      09:25:15,078 ERROR [AbstractKernelController] Error installing to Instantiated: name=ModClusterService state=Described mode=On Demand requiredState=Installed
      java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.modcluster.config.ModClusterConfig, org.jboss.modcluster.load.LoadBalanceFactorProviderFactory] actual=[org.jboss.modcluster.config.ha.HAModClusterConfig, org.jboss.modcluster.load.impl.DynamicLoadBalanceFactorProvider]
      at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395)

      The microcontainer is trying to instantiate ModClusterService using the wrong constructor. The mod_cluster-jboss-beans.xml should be updated to explicitly define the parameter types to remove this ambiguity.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: