]
Michal Babacek closed MODCLUSTER-116.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
Microcontainer does not always choose the right constructor when
creating ModClusterService
-------------------------------------------------------------------------------------------
Key: MODCLUSTER-116
URL:
https://issues.jboss.org/browse/MODCLUSTER-116
Project: mod_cluster
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.1.0.Beta1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 1.1.0.CR1
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.