[Design of POJO Server] - Uninstall issue with @JMX beans
by bstansberry@jboss.com
Seeing the following in the logs during shutdown for all the beans I've annotated with @JMX. Just a DEBUG, so may be harmless, but wanted to point it out.
2006-11-16 16:01:49,609 DEBUG [org.jboss.kernel.plugins.dependency.InstantiateAction] Ignored error unsetting context
| java.lang.IllegalArgumentException: Wrong target. class org.jboss.invocation.jrmp.server.JRMPInvokerHA for public abstract void org.jboss.kernel.spi.dependency.KernelControllerContextAware.unsetKernelControllerContext(org.jboss.kernel.spi.dependency.KernelControllerContext) throws java.lang.Exception
| at org.jboss.aop.joinpoint.MethodInvocation.handleErrors(MethodInvocation.java:150)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:125)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:110)
| at AOPContainerProxy$2.unsetKernelControllerContext(AOPContainerProxy$2.java)
| at org.jboss.kernel.plugins.dependency.InstantiateAction.uninstallAction(InstantiateAction.java:92)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.uninstall(KernelControllerContextAction.java:140)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.uninstall(AbstractControllerContextActions.java:58)
| at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:236)
| at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:723)
| at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:685)
| at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:613)
| at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:223)
| at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:77)
| at org.jboss.deployers.plugins.deployers.kernel.BeanMetaDataDeployer.undeploy(BeanMetaDataDeployer.java:42)
| at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.undeploy(AbstractSimpleRealDeployer.java:60)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.prepareUndeploy(AbstractSimpleDeployer.java:42)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.prepareUndeploy(DeployerWrapper.java:105)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:419)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.prepareUndeploy(MainDeployerImpl.java:428)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:357)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.shutdown(MainDeployerImpl.java:482)
| at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:739)
| at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:721)
| at org.jboss.system.server.profileservice.ServerImpl$ShutdownHook.run(ServerImpl.java:706)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986695#3986695
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986695
19 years, 4 months
[Design of JBoss Web Services] - ws tests in jbossas
by scott.stark@jboss.org
I ported the jbossws org.jboss.test.ws.jaxws.webserviceref.WebServiceRefServletTestCase to the jbossas testsuite to validate the injection integration. Two tests pass, and the testDynamicProxy test fails because of a variable expression that is not getting replaced. I'm just running from within eclipse, and the current testsuite/build.xml is not filtering the ws resources like the jbossws test setup is:
| javax.xml.ws.soap.SOAPFaultException: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
| ...
| Caused by: java.net.UnknownHostException: jbosstest.host.name@
| at java.net.PlainSocketImpl.connect(Unknown Source)
| at java.net.Socket.connect(Unknown Source)
| at java.net.Socket.connect(Unknown Source)
| at sun.net.NetworkClient.doConnect(Unknown Source)
| at sun.net.www.http.HttpClient.openServer(Unknown Source)
| at sun.net.www.http.HttpClient.openServer(Unknown Source)
| at sun.net.www.http.HttpClient.<init>(Unknown Source)
| at sun.net.www.http.HttpClient.New(Unknown Source)
| at sun.net.www.http.HttpClient.New(Unknown Source)
| at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
| at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
| at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
| at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:192)
| ... 34 more
|
|
|
What are we going to define as an integration testsuite for jbossws?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986679#3986679
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986679
19 years, 4 months
[Design of POJO Server] - Re: Problem with javassist + RepositoryClassLoader
by scott.stark@jboss.org
"jason.greene(a)jboss.com" wrote : Doesn't this just fix visibility of the classloader from other loaders in the repository?
|
>From the perspective that a dynamic class loader should be seen as indexed to any package, yes.
"jason.greene(a)jboss.com" wrote :
| I checked the AOP implementation, and it is currently doing the same process of manually flushing the blacklists.
|
Ok, this looking under the covers, past the ClassLoader api was supposed to be eliminated by the dynamic class loader notion. The dynamic url notion was not well published or tested so I can't complain. We should have the ability to configure caching behavior for a given deployment, but we should not have to step outside of the class loading api to do this. At least the code doing the class loading should not. This is not to say that we better expose the caching and indexing behavior for injection and integration with lifecycle ops via kernel beans.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986633#3986633
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986633
19 years, 4 months
[Design of JBossCache] - Re: PojoCache implementation class AOP instrumentation depen
by kabir.khan@jboss.com
"ben.wang(a)jboss.com" wrote : So what we need to do is during the copying of the JBC library from 3d party dir to build, we need to do an "aopc" on the jar.
|
| But in this way, Kabir, I will need to unjar pojocache.jar first and then jar it again after instrumentation, is it correct?
|
Yes
"ben.wang(a)jboss.com" wrote :
| One other issue is for future upgrade. User can not simply drop the jar from the JBC released version.
|
Hence the "install" script I mentioned. I think jboss messaging does this as well.
"ben.wang(a)jboss.com" wrote :
| Now why can't JBoss Aop try to maintain some binary compatability between releases?
|
Now that this has become a requirement, we will attempt to do this. I have always seen the woven code as an internal implementation detail, and so have not really thought about this part before. Now that we have run into a real need for this we will attempt to keep this in sync between minor versions. However, before we go final with 2.0.0.GA we *might* still need to make adjustments to what is being woven in.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986623#3986623
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986623
19 years, 4 months