@JMX beans fail to deploy WAS: Ready to go Re: [jboss-dev] WARNING: Update to new deployers

Brian Stansberry brian.stansberry at redhat.com
Fri Jun 29 10:57:09 EDT 2007


No worries.  Been going through tedious testsuite fixes all week; this 
gave me a badly needed excuse to go do something else. :-)

Kabir, with your changes my build looks good.  Thanks for sorting it so 
quickly.  Well, maybe no thanks -- now I've gotta go back to sorting 
testsuite failures. ;)

Adrian wrote:
> Yep, sorry. I saw this also in the connectors,
> 
> I just commented out the annotation I need to find out what
> the problem is here, its in some new code in the MC.
> 
> But I wanted to get code in before somebody else
> made me have to do yet another merge. :-)
> 
> On Thu, 2007-06-28 at 15:15 -0500, Brian Stansberry wrote:
>> Updated my trunk copy and now any bean annotated with @JMX fails to deploy:
>>
>> 2007-06-28 14:29:20,561 ERROR 
>> [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error 
>> installing to Configured: name=JRMPInvokerHA state=Configured
>> java.lang.Exception: Error calling callback JMXAdvice for target context 
>> JRMPInvokerHA
>> 	at 
>> org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:86)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1191)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1172)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:694)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:813)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:735)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:525)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:361)
>> 	at 
>> org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:69)
>> 	at 
>> org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42)
>> 	at 
>> org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:164)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:657)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:672)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployersImpl.doInstall(DeployersImpl.java:623)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:587)
>> 	at 
>> org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:304)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1257)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:685)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:813)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:735)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:573)
>> 	at 
>> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:374)
>> 	at 
>> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:426)
>> 	at 
>> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:340)
>> 	at 
>> org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:379)
>> 	at 
>> org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:247)
>> 	at 
>> org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
>> 	at 
>> org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403)
>> 	at 
>> org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342)
>> 	at org.jboss.Main.boot(Main.java:210)
>> 	at org.jboss.Main$1.run(Main.java:523)
>> 	at java.lang.Thread.run(Thread.java:595)
>> Caused by: org.jboss.joinpoint.spi.JoinpointException: Method not found 
>> install[org.jboss.dependency.spi.ControllerContext] for class 
>> org.jboss.aop.microcontainer.aspects.jmx.JMXIntroduction
>> 	at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:396)
>> 	at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:365)
>> 	at org.jboss.joinpoint.plugins.Config.findMethodInfo(Config.java:334)
>> 	at org.jboss.joinpoint.plugins.Config.getMethodJoinpoint(Config.java:222)
>> 	at 
>> org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:254)
>> 	at 
>> org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:268)
>> 	at 
>> org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:82)
>> 	... 32 more
>>
>> Adrian wrote:
>>> All the changes are in now.
>>>
>>> Or at least I think they are??
>>> The eclipse svn support is so flakey, I can't be sure.
>>>
>>> It didn't help that my internet connection crashed half way
>>> through the commit, eclipse still thinks there are changes
>>> to commit even though an svn diff clearly shows the files
>>> are the same????
>>>
>>> Talk about a bad day. :-)
>>>
>>> On Thu, 2007-06-28 at 12:33 +0200, Adrian wrote:
>>>> Hopefully, today I'm going to update jboss-head
>>>> to the new deployers, this means the build might be broken
>>>> for a bit.
>>>>
>>>> I'd appreciate it if you don't commit anything around the
>>>> deployers (that includes the ejb containers, etc.)
>>>> so I can do a final merge and standup tests
>>>> before committing.
>>>>
>>>> I'll let you know when the commits are in.
>>>>
>>>> NOTE: I'll be disabling webservices for a couple of days
>>>> since its deployers are in the webservices project
>>>> which I haven't updated to the new deployers yet
>>>> and they'll also require a new release of webservices
>>>> to be updated.
>>>> Apologies for the inconvience. :-(
>>


-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com




More information about the jboss-development mailing list