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

[Design of JBoss ESB] - Re: Removing hypersonic support

by mark.little＠jboss.com

Derby (aka Cloudscape) is fine and has the advantage of being around for many years. I'd trust it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126680#4126680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126680

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Container Proxy serialization issue

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : What I don't understand is why the objects in the test have a proxy anyway? | | | | This is a mystery to me as well... | I'd concentrate on fixing this problem, since it is the real reason why the test is failing (when it shouldn't). For the MetaData serialization, just add a default implementation of something like: if (metadata instanceof Serializable) // serialize else // no metadata on the client View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126676#4126676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126676

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Container Proxy serialization issue

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : | I could do the same for the MetaData. How would I get all the present MetaData though? | That's my point. You can't in general. Only if the MetaData is specifically designed for serialization to the client would this possible. i.e. the proxy has been specifically setup for client side usage. e.g. One use case of the MetaData in future is be able to have an AspectManager in the application scope or subsystem scope of the metadata. That's not something you're going to want to serialize to the client. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126675#4126675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126675

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Facelets scanning for .taglib.xml is broken in trunk

by charles.crouch＠jboss.com

do we have a jira for this yet? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126674#4126674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126674

18 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Callbacks and new classloader changes

by adrian＠jboss.org

If you are seeing ServiceController.shutdown() then it means there are MBeans not getting undeployed in the proper way, i.e. uninstalled by the deployment or service that constructed them. The ServiceController.shutdown() is only really a hack to fix broken stuff in the case where the JVM is not really shutdown and would cause leaks otherwise. The same goes for the BasicKernelDeployer.shutdown() In this case, it looks like the issue is in system-jmx/src/main/org/jboss/system/microcontainer/jmx/ServiceControllerLifecycleCallback.java which implements the @JMX handling. It is only invoking the destroy() on the MBean. It is not removing the reference from the ServiceController, etc. via remove() | public void uninstall(ControllerContext context) throws Exception | { | JMX jmx = readJmxAnnotation(context); | ObjectName objectName = createObjectName(context, jmx); | | log.debug("Unregistering MBean " + objectName); | serviceController.destroy(objectName); | + serviceController.remove(objectName); | } | So the JMXKernel.shutdown() is trying to clean this up and failing. But rather than just fix this, I want to understand why the callbacks are being invoked on a context that doesn't exist (something wrong with dependencies?) and what those callbacks might be? I'd have more information if this was a better error message. Why is there no contextual information? | // let's make sure we suppress any exceptions | catch (Throwable t) | { | - log.warn("Cannot resolve callbacks.", t); | + log.warn("Cannot resolve callbacks state=" + state + " isInstall=" + isInstallPhase + + " context="context + , t); | } | | 23:36:28,187 WARN [AbstractKernelController] Cannot resolve callbacks. | javax.management.InstanceNotFoundException: jboss.jca:service=JCAMetaDataRepository,name=DefaultJCAM | etaDataRepository is not registered. | at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) | at org.jboss.mx.server.MBeanServerImpl.getClassLoaderFor(MBeanServerImpl.java:1062) | at org.jboss.system.microcontainer.ServiceControllerContext.getClassLoader(ServiceController | Context.java:167) | at org.jboss.dependency.plugins.SecurityActions.setContextClassLoader(SecurityActions.java:4 | 6) | at org.jboss.dependency.plugins.AbstractController.resolveCallbacks(AbstractController.java: | 1174) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java: | 1006) | 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) | Who, where, what, why, when? :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126672#4126672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126672

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Container Proxy serialization issue

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : What I don't understand is why the objects in the test have a proxy anyway? | This is a mystery to me as well... Regarding the serialization, as it works now (without MetaData), is I serialize some extra information for use when unserializing on a client. I could do the same for the MetaData. How would I get all the present MetaData though? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126663#4126663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126663

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP Container Proxy serialization issue

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : I have largely implemented this locally. Adrian's test still fails since the MetaDataRetrievalToMetaDataBridge is not serializable That could never be properly serializable. e.g. the bridge could link to a MetaDataRetrieval that loads data from a database or it may link to scopes that depend upon the server or cluster you are running in. What I don't understand is why the objects in the test have a proxy anyway? Your point creates another issue. The mechanism of "serialization" should depend upon the use case. 1) The proxy is for server side aspects and should be removed when given to the client, i.e. we serialize it as the plain class. Although this use case doesn't make much sense. 2) The proxy is intended for client side use and should contain a MetaData object that is serializable and contains the client side metadata (or knows how to link to it on deserialization). 3) The proxy should be replaced with a client side stub that does remote requests on the server side object. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126659#4126659 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126659

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Classloader problem with NamingRestartUnitTestCase

by adrian＠jboss.org

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

18 years, 2 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - AOP ClassLoader problem

by adrian＠jboss.org

This looks like incorrect caching of the classloader within AOP? http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126651#4126651 can you investigate to see if my guess is correct, or if it is something else? Also we need to revisit the scope issue mentioned on that thread. We probably want to look at adding a getScopeKey() to the MetaData interface for you to use as the definitive value? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126653#4126653 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126653

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Classloader problem with NamingRestartUnitTestCase

by adrian＠jboss.org

Additionally, what this code is doing with the annotations looks wrong to me. The annotations are only a potential source of the scope, the scope could be determined in a different way. e.g. The deployers generate a scope for each deployment which comes from the deployment names not annotations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126651#4126651 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126651

18 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 2008