February 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Registering a bean as an aspect in the bootstrap

by kabir.khan＠jboss.com

This requirement has been removed from the AOP/MC integration layer. Meaning the AspectManager bootstrap-beans.xml does not need to explicitly include classes that bean proxies should be created for: | <bean name="AspectManager" class="org.jboss.aop.deployers.AspectManagerJDK5"> | ... | <property name="include">org.jboss.test., org.jboss.injbossaop.</property> | <property name="exclude">org.jboss.</property> | include/exclude now only have an effect for what classes to inspect if doing loadtime weaving. A side effect of this is this error: | 15:59:54,234 INFO [JMXIntroduction] Registered MBean jboss.ha:service=HASingletonDeployer,type=BarrierController | 15:59:54,234 ERROR [AbstractKernelController] Error installing to Create: name=jboss.ha:service=HASingletonDeployer,type=BarrierController state=Configured | javax.management.MBeanException | at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:184) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:165) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:186) | at AOPContainerProxy$7.create(AOPContainerProxy$7.java) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:55) | at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:108) | at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103) | at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:145) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:233) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:430) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:540) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:474) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:274) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:67) | at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:56) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:603) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:367) | 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:508) | at java.lang.Thread.run(Thread.java:595) | Caused by: org.jboss.deployment.DeploymentException: Error during register: jboss.ha:service=HASingletonDeployer,type=BarrierController | at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52) | at org.jboss.system.ServiceController.register(ServiceController.java:352) | at org.jboss.system.ServiceController.create(ServiceController.java:375) | at org.jboss.system.ServiceController.create(ServiceController.java:358) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | ... 42 more | Caused by: java.lang.IllegalStateException: jboss.ha:service=HASingletonDeployer,type=BarrierController is already installed. | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:249) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:177) | at org.jboss.system.ServiceController.doInstall(ServiceController.java:638) | at org.jboss.system.ServiceController.register(ServiceController.java:344) | ... 49 more | I assume that this bean was not one of the "included" ones earlier, so that the JMXIntroduction was never called for this bean. Now it does get called, so it pukes up when the ServiceMBeanSupport.create() method tries to call ServiceController.start() View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010429#4010429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010429

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by timfox

Looks good. But when you make changes don't just comment things out, get rid of them if they are not needed. | if (rows != 1) | { | // http://jira.jboss.com/jira/browse/JBMESSAGING-808 | log.warn("Failed to remove row for: " + ref); | return; | //throw new IllegalStateException("Failed to remove row for: " + ref); | } | Otherwise we end up with the code scattered with rubbish. If we want to retrieve the previous version, it's in version control. I'm not sure if the log.warn is really necessary either. log.warn would imply there is probably something wrong. Is this the case? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010404#4010404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010404

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Backport to 1_0_1_SP1 has broken the test suite

by timfox

Stop making fucking excuses and remember to run the test suite before committing. ;) That is the system. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010397#4010397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010397

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Jbpm task management in seperate application

by heiko.zehner

Hi Ronald, sorry for that. I posted first into this forum and found the jbpm user forum more appropriate. Regards Heiko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010393#4010393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010393

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Backport to 1_0_1_SP1 has broken the test suite

by ovidiu.feodorov＠jboss.com

Yeah, I ported it. And I checked that in, fully assured that cruisecontrol will do its job. But wait, we don't have cruisecontrol running on 1_0_1_SP! Ooops. However, willl we release SP4 without a full testsuite? No. Relax, guys, the system works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010332#4010332 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010332

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by clebert.suconic＠jboss.com

I have just committed a fix for this. Please Tim and Ovidiu.. if you could take a look... Especially on JDBCPersistenceManager... MultiThreadFailoverTest was failling on the changed line. If you think this change is not ok I can investigate why this was happening. I have used SVN comment as "ttp://jira.jboss.com/jira/browse/JBMESSAGING-808 - fix". You could locate the changes with this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010325#4010325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010325

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by clebert.suconic＠jboss.com

As part of this discussion I'm also adding testFailureRightBeforeSend and testFailureRightAfterSend View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010302#4010302 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010302

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: default server in /trunk doesn't start when using profil

by scott.stark＠jboss.org

I updated the bootstrap-repo.xml for the AspectManager changes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010291#4010291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010291

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: default server in /trunk doesn't start when using profil

by kabir.khan＠jboss.com

I was unaware of this file, it should be fixed now View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010289#4010289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010289

19 years, 2 months

1
0
0 / 0

[Design of JBoss Admin Console] - Re: Viewing admin console

by PeterJ

Remove server/default/deploy/jbossweb-tomcat55.sar/ROOT.war. That directory contains the default web page. Or replace the index.html file with another one that contains a link to your app. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010288#4010288 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010288

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2007