September 2007 - jboss-dev-forums

[Design of POJO Server] - Unifying metadata

by scott.stark＠jboss.org

A problem showing up in 1.4 container to 5 container interop, as well as merging duplicate behavior into common deployers is the lack of a unified metadata view. The metadata view is also not authoritative. For example, the jndi name under which home proxies are bound is not simply the org.jboss.ejb3.metamodel.EnterpriseBean.getJndiName or transport derived variation like the org.jboss.metadata.BeanMetaData.getInvokerBinding. We have to have a consistent and complete metadata view so that proxy factory x obtains the name to bind the proxy under is a simple lookup against the metadata. There cannot be container specific logic if this is the be manageable and refactorable. In terms of the unified metadata work: https://svn.jboss.org/repos/common/jbossxb-builder/trunk/src/test/java/or... what exists in terms of backward compatibility with the old models? I thought Adrian said he had something that would allow coding using the old models to write through to the new model. The metadata model should also be in a separate project. I suppose this should be under the https://svn.jboss.org/repos/jbossas/projects/integration/trunk/ as a jboss-metadata project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083940#4083940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083940

18 years, 6 months

2
1
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by alex.loubyansky＠jboss.com

The metadata project was created by Carlo some time ago and initially included the current EJB3 metadata, AFAIK. Recently, I moved the metadata from the jbossxb-builder to this project as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083967#4083967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083967

18 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - aspect library config for jbossas

by adrian＠jboss.org

Related to this: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083964#4083964 and JBAS-4717 I wanted to change the config for the @JMX aspect, but currently this config is defined in the aop project, so it would need a new release of aop to change it???? I've moved it to the aspects project in the appserver codebase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083966#4083966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083966

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by scott.stark＠jboss.org

Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083965#4083965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083965

18 years, 6 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - JBAS-4717 - Problem with @JMX for clustering

by adrian＠jboss.org

Currently clustering's use of @JMX is causing spurious errors at shutdown: e.g. | 15:32:50,651 WARN [AbstractLifecycleCallbackItem] Ignored error uninstalling context JChannelFactoryJMXWrapper; callback=JMXAdvice | javax.management.InstanceNotFoundException: jboss.jgroups:service=MultiplexerChannelFactory is not registered. | at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) | at org.jboss.mx.server.MBeanServerImpl.unregisterMBean(MBeanServerImpl.java:383) | at org.jboss.aop.microcontainer.aspects.jmx.JMXLifecycleCallback.uninstall(JMXLifecycleCallback.java:73) | at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source) | 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.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:255) | at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:234) | at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.uninstall(AbstractLifecycleCallbackItem.java:107) | at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1245) | at org.jboss.dependency.plugins.AbstractController.handleUninstallLifecycleCallbacks(AbstractController.java:1231) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1007) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:936) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:986) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:936) | at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:463) | at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:426) | at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:79) | at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:42) | at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.undeploy(AbstractSimpleRealDeployer.java:73) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:187) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:947) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:940) | at org.jboss.deployers.plugins.deployers.DeployersImpl.uninstall(DeployersImpl.java:902) | at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:333) | at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1323) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1009) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:627) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:420) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354) | at org.jboss.deployers.plugins.main.MainDeployerImpl.shutdown(MainDeployerImpl.java:382) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.shutdown(ProfileServiceBootstrap.java:151) | at org.jboss.bootstrap.AbstractServerImpl.shutdownServer(AbstractServerImpl.java:482) | at org.jboss.bootstrap.AbstractServerImpl$ShutdownHook.run(AbstractServerImpl.java:778) | This is because the MBeans implement ServiceMBeanSupport which means they will be lazily registered with the ServiceController and thus unregistered twice (once by the JMXLifecycle callback and once when the ServiceController shuts down). What I want to do is change the lifecycle to use the ServiceController instead of the MBeanServer directly. That way it will be removed from the ServiceController only (which also removes it from the MBeanServer) unlike now where there is no unregisteration from the ServiceController unless you shutdown the server. This has another advantage that you can have proper dependencies on the JMX name as well which will give some backwards compatibilty. But the dual lifecycle (bean and jmx) is causing start() to be invoked twice. | 15:26:45,657 ERROR [AbstractKernelController] Error installing to Create: name=HAPartition state=Configured | java.lang.RuntimeException: Failure creating multiplexed Channel | at org.jboss.ha.framework.server.ClusterPartition.createMuxChannel(ClusterPartition.java:225) | at org.jboss.ha.framework.server.ClusterPartition.createService(ClusterPartition.java:253) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188) | at AOPContainerProxy$18.create(AOPContainerProxy$18.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:221) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:143) | at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:53) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.system.ServiceController.doInstall(ServiceController.java:641) | at org.jboss.system.ServiceController.register(ServiceController.java:344) | at org.jboss.system.ServiceController.start(ServiceController.java:415) | at org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback.install(ServiceControllerLifecycleCallback.java:93) | 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.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:255) | at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:234) | at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:82) | at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1243) | at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1224) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:743) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.system.ServiceController.doInstall(ServiceController.java:641) | at org.jboss.system.ServiceController.register(ServiceController.java:344) | at org.jboss.system.ServiceController.start(ServiceController.java:415) | at org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback.install(ServiceControllerLifecycleCallback.java:93) | 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.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:255) | at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:234) | at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:82) | at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1243) | at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1224) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:743) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.system.ServiceController.doInstall(ServiceController.java:641) | at org.jboss.system.ServiceController.register(ServiceController.java:344) | at org.jboss.system.ServiceController.start(ServiceController.java:415) | at org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback.install(ServiceControllerLifecycleCallback.java:93) | 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.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:255) | at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:234) | at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:82) | at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1243) | at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1224) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:743) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:574) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) | at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:68) | 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:169) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:529) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.Exception: service ID "DefaultPartition" is already registered, cannot register duplicate ID | at org.jgroups.mux.Multiplexer.createMuxChannel(Multiplexer.java:403) | at org.jgroups.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:297) | at org.jboss.ha.framework.server.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:68) | at org.jboss.ha.framework.server.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:82) | at org.jboss.ha.framework.server.ClusterPartition.createMuxChannel(ClusterPartition.java:217) | ... 110 more | What would fix the problem would to change the name from the none automatic name "start()" to one that only the MC recognises such that the method is invoked only for the bean view. e.g. | @org.jboss.beans.metadata.plugins.annotations.Start | public void startPartition() | and the same for stop. You can try the new ServiceController based version if you change the config in deployers/jboss-aop-jboss5.deployer/META-INF/jboss-aspect-library-beans.xml swap this config |  |  | | <aop:lifecycle-configure xmlns:aop="urn:jboss:aop-beans:1.0" | name="JMXAdvice" | class="org.jboss.aop.microcontainer.aspects.jmx.JMXLifecycleCallback" | classes="@org.jboss.aop.microcontainer.aspects.jmx.JMX" | manager-bean="AspectManager" | manager-property="aspectManager"> | <property name="mbeanServer"><inject bean="JMXKernel" property="mbeanServer"/></property> | </aop:lifecycle-configure> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083964#4083964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083964

18 years, 6 months

1
0
0 / 0

[QA of JBoss Portal] - Configurable Test Server

by mwringe

The sso test cases need for the server to have certain configurations in order for it to work (specifically setting up ssl and certificates). SSL is not the default configuration for JBossAS or Tomcat, so it would be wise to be able to setup a configurable server test setting that the test can setup itself. Cargo currently does this, but I am running into the following issues: 1) embedded tomcat: incompatible with the jars we currently have in /thirdparty, needs an older version of tomcat to work (tomcat5.0 not tomcat5.5), needs to download all the catalina jars for the tests to work. Another issue is that the embedded tomcat runs within the same jvm, so extra care has to be setup to run these tests from ant/maven to ensure a proper endorsed dirs. 2) installed JBossAS: configures the application server and not JBossWeb, so many of the features that we need are not available. With this option we wouldn't need to download extra jars to run the tests. 3) installed tomcat: I have not looked into this situation that much, would require that the user downloads and installs tomcat themselves. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083961#4083961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083961

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by sacha.labourey＠jboss.com

AFAICT this is the work Alexey is currently doing, right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083960#4083960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083960

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by anil.saldhana＠jboss.com

http://jira.jboss.com/jira/browse/EJBTHREE-1048 is the EJB3 JACC alignment issue with unified metamodel. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083951#4083951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083951

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by scott.stark＠jboss.org

Related threads and issues: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111567 http://jira.jboss.com/jira/browse/JBAS-4506 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083943#4083943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083943

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Unifying metadata

by anil.saldhana＠jboss.com

Scott, what is the JIRA issue associated with the unified metamodel? I want to link the ejb3 jacc work that needs to be done after that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083942#4083942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083942

18 years, 6 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 September 2007