It might be again due to lack of info on which ctor to use. And since the ctor order is pretty much random, it looks like you get the wrong one - which still matches the no-info info. :-) See if you can add extra info to ctor in -jboss-beans.xml in which this bean is specified. Dimitris Andreadis wrote: > It fails for me in Branch_5_x: > > 14:19:20,343 INFO [JMXKernel] Legacy JMX core initialized > 14:19:23,296 ERROR [AbstractKernelController] Error installing to > Instantiated: > name=ClusteredDeploymentRepositoryMetadataPersister state=Described > java.lang.IllegalArgumentException: Wrong arguments. new for target > java.lang.re > flect.Constructor expected=[java.net.URI] > actual=[org.jboss.bootstrap.microconta > iner.ServerImpl] > at > org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors( > ReflectionUtils.java:395) > at > org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(R > eflectionUtils.java:153) > at > org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.ne > wInstance(ReflectConstructorInfoImpl.java:106) > at > org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicC > onstructorJoinPoint.java:80) > at > org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.crea > teTarget(AOPConstructorJoinpoint.java:276) > at > org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.disp > atch(AOPConstructorJoinpoint.java:97) > at > org.jboss.kernel.plugins.dependency.KernelControllerContextAction$Joi > npointDispatchWrapper.execute(KernelControllerContextAction.java:241) > at > org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(Executio > nWrapper.java:47) > at > org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis > patchExecutionWrapper(KernelControllerContextAction.java:109) > at > org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis > patchJoinPoint(KernelControllerContextAction.java:70) > at > org.jboss.kernel.plugins.dependency.InstantiateAction.installActionIn > ternal(InstantiateAction.java:66) > at > org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction > (InstallsAwareAction.java:54) > at > org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction > (InstallsAwareAction.java:42) > at > org.jboss.dependency.plugins.action.SimpleControllerContextAction.sim > pleInstallAction(SimpleControllerContextAction.java:62) > at > org.jboss.dependency.plugins.action.AccessControllerContextAction.ins > tall(AccessControllerContextAction.java:71) > at > org.jboss.dependency.plugins.AbstractControllerContextActions.install > (AbstractControllerContextActions.java:51) > at > org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra > ctControllerContext.java:348) > at > org.jboss.dependency.plugins.AbstractController.install(AbstractContr > oller.java:1631) > at > org.jboss.dependency.plugins.AbstractController.incrementState(Abstra > ctController.java:934) > at > org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr > actController.java:1082) > at > org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr > actController.java:984) > at > org.jboss.dependency.plugins.AbstractController.install(AbstractContr > oller.java:774) > at > org.jboss.dependency.plugins.AbstractController.install(AbstractContr > oller.java:540) > at > org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean > (AbstractKernelDeployer.java:319) > at > org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean > s(AbstractKernelDeployer.java:297) > at > org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(Abs > tractKernelDeployer.java:130) > at > org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicK > ernelDeployer.java:76) > at > org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa > sicXMLDeployer.java:91) > at > org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa > sicXMLDeployer.java:161) > at > org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java > :138) > at > org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java: > 450) > at org.jboss.Main.boot(Main.java:216) > at org.jboss.Main$1.run(Main.java:546) > at java.lang.Thread.run(Thread.java:595) > Failed to boot JBoss: > java.lang.IllegalStateException: Incompletely deployed: > > DEPLOYMENTS IN ERROR: > Deployment "ClusteredDeploymentRepositoryMetadataPersister" is in > error due to > : java.lang.IllegalArgumentException: Wrong arguments. new for target > java.lang. > reflect.Constructor expected=[java.net.URI] > actual=[org.jboss.bootstrap.microcon > tainer.ServerImpl] > > DEPLOYMENTS MISSING DEPENDENCIES: > Deployment "FilesystemLocalContentManagerFactory" is missing the > following dep > endencies: > Dependency "ClusteredDeploymentRepositoryMetadataPersister" > (should be in st > ate "Installed", but is actually in state "**ERROR**") > > at > org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalVa > lidate(AbstractKernelDeployer.java:278) > at > org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(A > bstractKernelDeployer.java:174) > at > org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java > :142) > at > org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java: > 450) > at org.jboss.Main.boot(Main.java:216) > at org.jboss.Main$1.run(Main.java:546) > at java.lang.Thread.run(Thread.java:595) > 14:19:24,437 INFO [ServerImpl] Runtime shutdown hook called, > forceHalt: true > 14:19:24,453 INFO [ServerImpl] Shutdown complete > Shutdown complete > Halting VM > Press any key to continue . . . > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >

> It must be this? Yes. I've added more info + committed. > server/all/conf/bootstrap/profile.xml > ... > <!-- Handles persistence of metadata about clustered > DeploymentRepository content --> > <bean name="ClusteredDeploymentRepositoryMetadataPersister" > > class="org.jboss.system.server.profileservice.repository.clustered.local.JAXBRepositoryContentMetadataPersister"> > > <constructor> > <!-- Here we use the constructor version that takes the > Server impl and > uses it to find the data dir. You could alternatively > use a version > that takes a URI or a File. --> > <parameter><inject bean="JBossServer"/></parameter> > </constructor> > </bean> > > Ales Justin wrote: >> It might be again due to lack of info on which ctor to use. >> And since the ctor order is pretty much random, >> it looks like you get the wrong one - which still matches the no-info >> info. :-) >> >> See if you can add extra info to ctor in -jboss-beans.xml in which >> this bean is specified.

Shouldn't be able to derive the the injected paramemeter implements org.jboss.bootstrap.spi.Server and use that CTOR? public JAXBRepositoryContentMetadataPersister(Server server) { this(server.getConfig().getServerDataDir()); } public JAXBRepositoryContentMetadataPersister(URI uri) { this(new File(uri)); } public JAXBRepositoryContentMetadataPersister(File dir) { super(dir); } Ales Justin wrote: >> It must be this? > > Yes. > I've added more info + committed. > >> server/all/conf/bootstrap/profile.xml >> ... >> <!-- Handles persistence of metadata about clustered >> DeploymentRepository content --> >> <bean name="ClusteredDeploymentRepositoryMetadataPersister" >> >> class="org.jboss.system.server.profileservice.repository.clustered.local.JAXBRepositoryContentMetadataPersister"> >> >> <constructor> >> <!-- Here we use the constructor version that takes the >> Server impl and >> uses it to find the data dir. You could alternatively >> use a version >> that takes a URI or a File. --> >> <parameter><inject bean="JBossServer"/></parameter> >> </constructor> >> </bean> >> >> Ales Justin wrote: >>> It might be again due to lack of info on which ctor to use. >>> And since the ctor order is pretty much random, >>> it looks like you get the wrong one - which still matches the >>> no-info info. :-) >>> >>> See if you can add extra info to ctor in -jboss-beans.xml in which >>> this bean is specified.

Is there no mechanism to use reasonable defaults if something is not specified? ====================================== - <parameter><inject bean="JBossServer"/></parameter> + <parameter class="org.jboss.bootstrap.spi.Server"><inject bean="JBossServer"/></parameter> =================================== Why should we be configuration freaks to make everything explicit? <anilShutUp/> Ales Justin wrote: > Search for this (never ending) discussion on our MC dev fourm. :-) > > Dimitris Andreadis wrote: >> Shouldn't be able to derive the the injected paramemeter implements >> org.jboss.bootstrap.spi.Server and use that CTOR? >> >> >> public JAXBRepositoryContentMetadataPersister(Server server) >> { >> this(server.getConfig().getServerDataDir()); >> } >> >> public JAXBRepositoryContentMetadataPersister(URI uri) >> { >> this(new File(uri)); >> } >> >> public JAXBRepositoryContentMetadataPersister(File dir) >> { >> super(dir); >> } >> >> Ales Justin wrote: >>>> It must be this? >>> >>> Yes. >>> I've added more info + committed. >>> >>>> server/all/conf/bootstrap/profile.xml >>>> ... >>>> <!-- Handles persistence of metadata about clustered >>>> DeploymentRepository content --> >>>> <bean name="ClusteredDeploymentRepositoryMetadataPersister" >>>> >>>> class="org.jboss.system.server.profileservice.repository.clustered.local.JAXBRepositoryContentMetadataPersister"> >>>> >>>> <constructor> >>>> <!-- Here we use the constructor version that takes the >>>> Server impl and >>>> uses it to find the data dir. You could alternatively >>>> use a version >>>> that takes a URI or a File. --> >>>> <parameter><inject bean="JBossServer"/></parameter> >>>> </constructor> >>>> </bean> >>>> >>>> Ales Justin wrote: >>>>> It might be again due to lack of info on which ctor to use. >>>>> And since the ctor order is pretty much random, >>>>> it looks like you get the wrong one - which still matches the >>>>> no-info info. :-) >>>>> >>>>> See if you can add extra info to ctor in -jboss-beans.xml in which >>>>> this bean is specified. _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

> It must be this? Yes. I've added more info + committed. > server/all/conf/bootstrap/profile.xml > ... > <!-- Handles persistence of metadata about clustered > DeploymentRepository content --> > <bean name="ClusteredDeploymentRepositoryMetadataPersister" > > class="org.jboss.system.server.profileservice.repository.clustered.local.JAXBRepositoryContentMetadataPersister"> > > <constructor> > <!-- Here we use the constructor version that takes the > Server impl and > uses it to find the data dir. You could alternatively > use a version > that takes a URI or a File. --> > <parameter><inject bean="JBossServer"/></parameter> > </constructor> > </bean> > > Ales Justin wrote: >> It might be again due to lack of info on which ctor to use. >> And since the ctor order is pretty much random, >> it looks like you get the wrong one - which still matches the no-info >> info. :-) >> >> See if you can add extra info to ctor in -jboss-beans.xml in which >> this bean is specified. _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development