March 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: InterruptedException not being cleared?

by david.lloyd＠jboss.com

I didn't mean ignore it, just defer it - after all the thread could be asynchronously interrupted and I don't think that the best thing to do would be to blow up in that case. Anyway, consuming the InterruptedException is definitely the wrong thing to do regarless of where the status is being set (and that's really what it's doing now, looking at ClassLoaderManager.java:169). It should catch the exception, set a flag, continue what it's doing, then reset the interrupt status on exit; that or rethrow InterruptedException (which it cannot do in this case, since loadClass doesn't throw that exception). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214959#4214959 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214959

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Smooks DB->XML

by ama1

Hi, does anyone have an example or a link to some documentation for the db-enrichment features in smooks? Unfortunately I could not find anything :-( View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214958#4214958 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214958

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: InterruptedException not being cleared?

by scott.stark＠jboss.org

Not without the caller clearing the state as its the concurrent layer that will throw the exception. We aren't going to ignore that in the class loading layer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214957#4214957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214957

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: InterruptedException not being cleared?

by david.lloyd＠jboss.com

I'm not very familiar with the classloader guts here, but shouldn't it be possible to load a class even if the current thread's interrupt status is set? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214951#4214951 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214951

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: InterruptedException not being cleared?

by smcgowan＠redhat.com

https://jira.jboss.org/jira/browse/JBAS-6546 filed as this is seen when running the automated tests. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214945#4214945 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214945

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: InterruptedException not being cleared?

by scott.stark＠jboss.org

Actually, I'm seeing this even after a restart of the server, so I don't know what is setting the interrupted state. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214944#4214944 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214944

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - InterruptedException not being cleared?

by scott.stark＠jboss.org

It looks like an InterruptedException may not be getting cleared. I was debugging an admin console issue and it timed out, presumably setting the interrupted state on a thread and now it keeps hanging with a class load failure due to an InterruptedException. | 07:45:02,097 WARN [ClassLoaderManager] Unexpected error during load of:org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryDeployer | java.lang.InterruptedException | at java.lang.Object.wait(Native Method) | at java.lang.Object.wait(Object.java:474) | at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:211) | at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:152) | at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:259) | at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1102) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:772) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:415) | at java.lang.ClassLoader.loadClass(ClassLoader.java:306) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getManagedObjectClass(BeanMetaDataICF.java:135) | at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getManagedObjectClass(BeanMetaDataICF.java:48) | at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:342) | at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) | at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) | at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) | at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:204) | at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) | at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:367) | at org.jboss.deployers.spi.deployer.helpers.DefaultManagedObjectCreator.build(DefaultManagedObjectCreator.java:81) | at org.jboss.deployers.plugins.deployers.DeployersImpl.getManagedObjects(DeployersImpl.java:463) | at org.jboss.deployers.plugins.main.MainDeployerImpl.getManagedObjects(MainDeployerImpl.java:928) | at org.jboss.deployers.plugins.main.MainDeployerImpl.getManagedDeployment(MainDeployerImpl.java:905) | at org.jboss.profileservice.management.ManagementViewImpl.getManagedDeployment(ManagementViewImpl.java:1300) | at org.jboss.profileservice.management.ManagementViewImpl.loadProfile(ManagementViewImpl.java:212) | at sun.reflect.GeneratedMethodAccessor317.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:99) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) | at org.jboss.remoting.Client.invoke(Client.java:1708) | at org.jboss.remoting.Client.invoke(Client.java:612) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at AOPProxy$1.loadProfile(AOPProxy$1.java) | at org.rhq.plugins.jbossas5.factory.ProfileServiceFactory.refreshCurrentProfileView(ProfileServiceFactory.java:113) | at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.getManagedDeployment(ManagedDeploymentComponent.java:335) | at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.getAvailability(ManagedDeploymentComponent.java:133) | at sun.reflect.GeneratedMethodAccessor330.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:466) | at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) | at java.util.concurrent.FutureTask.run(FutureTask.java:123) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | at java.lang.Thread.run(Thread.java:613) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214943#4214943 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214943

17 years, 1 month

1
0
0 / 0

[Design of PVM (Process Virtual Machine)] - Re: fork problem in pvm

by galanfish

"hardest" wrote : hi.i read the manual and the source of pvm these days,and i think maybe i should implement the fork and join using "activity" in pvm.is that a correct and recommended way? can anyone please explain for us that why this way is better? what's the advantage? thx! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214913#4214913 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214913

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why have you reversed my changes on replication?

by clebert.suconic＠jboss.com

"clebert.suconic(a)jboss.com" wrote : "timfox" wrote : Order is definitely guaranteed. | | | | Even among different producers? Please ignore this question :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214910#4214910 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214910

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why have you reversed my changes on replication?

by clebert.suconic＠jboss.com

"timfox" wrote : Order is definitely guaranteed. | Even among different producers? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214904#4214904 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214904

17 years, 1 month

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 March 2009