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

[Deployers on JBoss (Deployers/JBoss)] - BaseClassLoader attachement makes DeploymentUnit non-seriali

by dimitris＠jboss.org

Somehow an org.jboss.classloader.spi.base.BaseClassLoader ends-up being a non-transient attachment to a DeploymentUnit, causing a series of deployment tests to fail, just because the client cannot query the DeploymentUnit from the server. How can we locate this classloader addition? | Testsuite: org.jboss.test.deployers.ejb.test.EJBDeploymentUnitTestCase | Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 6.75 sec | | Testcase: testEJBDeployment took 0.109 sec | Caused an ERROR | org.jboss.classloader.spi.base.BaseClassLoader | java.io.NotSerializableException: org.jboss.classloader.spi.base.BaseClassLoader | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1380) | at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.deployers.plugins.attachments.AttachmentsImpl.writeExternal(AttachmentsImpl.java:145) | at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.deployers.spi.attachments.helpers.ManagedObjectAttachmentsImpl.writeExternal(ManagedObjectAttachmentsImpl.java:65) | at org.jboss.deployers.spi.attachments.helpers.ManagedObjectsWithTransientAttachmentsImpl.writeExternal(ManagedObjectsWithTransientAttachmentsImpl.java:70) | at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.writeExternal(AbstractDeploymentContext.java:836) | at org.jboss.deployers.vfs.plugins.structure.AbstractVFSDeploymentContext.writeExternal(AbstractVFSDeploymentContext.java:406) | at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.writeExternal(AbstractDeploymentUnit.java:509) | at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at java.rmi.MarshalledObject.<init>(MarshalledObject.java:92) | at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) | at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) | at sun.rmi.transport.Transport$1.run(Transport.java:153) | at java.security.AccessController.doPrivileged(Native Method) | at sun.rmi.transport.Transport.serviceCall(Transport.java:149) | at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) | at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) | at java.lang.Thread.run(Thread.java:595) | at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) | at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) | at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) | at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) | at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) | at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:244) | at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:181) | at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) | at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:87) | at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) | at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) | at $Proxy1.invoke(Unknown Source) | at org.jboss.test.deployers.AbstractDeploymentTest.invokeMainDeployer(AbstractDeploymentTest.java:83) | at org.jboss.test.deployers.AbstractDeploymentTest.getDeploymentUnit(AbstractDeploymentTest.java:114) | at org.jboss.test.deployers.AbstractDeploymentTest.assertDeployed(AbstractDeploymentTest.java:89) | at org.jboss.test.deployers.AbstractDeploymentTest.assertDeployed(AbstractDeploymentTest.java:96) | at org.jboss.test.deployers.ejb.test.EJBDeploymentUnitTestCase.testEJBDeployment(EJBDeploymentUnitTestCase.java:44) | at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) | at junit.extensions.TestSetup$1.protect(TestSetup.java:19) | at junit.extensions.TestSetup.run(TestSetup.java:23) | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156871#4156871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156871

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

After that, this one: FileHandler(a)781346814[path=jbossws.sar context=file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.CR1/server/default/deploy/ real=file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.CR1/server/default/deploy/jbossws.sar/] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156868#4156868 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156868

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

The dude that is causing the NPE is this: | sun.net.www.protocol.file.FileURLConnection:file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.CR1/server/default/deploy/management/console-mgr.sar/ | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156867#4156867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156867

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by emuckenhuber

Hmm - i tried that at home again and maybe it's just for 64Bit machines? I used an older Linux machine at home and it does not seem to be a problem there... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156857#4156857 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156857

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

So basically the following call | Arrays.asList(file.list()) | is failing inside Sun VM. For JBossVFS, the call is just getLastModified. So we need to figure out for which directory, this NPE is happening. | ArrayList(E[] array) { | if (array==null) | throw new NullPointerException(); | a = array; | } | This is the NPE we are seeing. IMO, we need to see why file.list() is returning null? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156856#4156856 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156856

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

| /* | * Note: the semantics of FileURLConnection object is that the | * results of the various URLConnection calls, such as | * getContentType, getInputStream or getContentLength reflect | * whatever was true when connect was called. | */ | public void connect() throws IOException { | if (!connected) { | try { | filename = file.toString(); | isDirectory = file.isDirectory(); | if (isDirectory) { | files = (List) Arrays.asList(file.list()); | } else { | | Scott, the last line....... Every method in FileURLConnection apparently calls initializeHeaders() internally which always calls connect(). So maybe as a start, we need to see which file in question leads to this NPE???? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156855#4156855 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156855

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

It is happening in default also. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156854#4156854 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156854

16 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bounding the number of threads created by the MDB contai

by timfox

Ok, you could give this a shot on Branch_Stable. Take a look at how we used the OrderedExecutorFactory in JBM 2.0. If you allow each session to maintain one of these child executors, then they could be backed by a single pool like you suggest. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156853#4156853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156853

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by scott.stark＠jboss.org

>From Emanuel's lsof I see he is running the all config. I have problems with that starting up cleanly for some reason due to jboss messaging config issues. I'll start it up to see if its showing this problem over time as well. I see duplicate files open in his trace though from the all/deploy/cluster directory, for example the cluster-beans.xml: | [522][valkyrie: /home/svn/JBossAS]$ grep cluster-beans.xml /tmp/lsof.output | java 4422 emuckenh 98r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 114r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 153r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 185r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 217r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 249r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 281r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 313r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 345r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 377r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 409r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 441r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 473r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 505r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 537r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 569r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 601r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 633r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 665r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 697r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 729r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 761r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 793r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 827r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 859r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 891r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 923r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 955r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 987r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | java 4422 emuckenh 1019r REG 253,0 3202 124143 /home/emuckenh/workspace/as/trunk/build/output/jboss-5.0.0.CR1/server/all/deploy/cluster/cluster-beans.xml | [523][valkyrie: /home/svn/JBossAS]$ | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156851#4156851 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156851

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : "anil.saldhana(a)jboss.com" wrote : All you have to do is start AS5 and wait a minute or so.... So it is only in F9? | | Apparently. I have a default AS5 instance that has been running for ~6 hours under osx without any change in descriptor/port counts. | No Scott. Emmanuel answered my Query. I was wondering about Fedora7/8 etc. So it is probably a bug in Sun JDK. OSX has its own impl. Let me try locate the class where the NPE is happening in JDK. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156850#4156850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156850

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008