RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
2004-01-22 12:15:06,862 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException: java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:354) at org.jboss.tm.TransactionImpl.associateCurrentThread(TransactionImpl.java :760) at org.jboss.tm.TxManager.associateThread(TxManager.java:369) at org.jboss.tm.TxManager.resume(TxManager.java:217) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor CMT.java:417) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java: 127) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor .java:92) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFact oryFinderInterceptor.java:93) at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:48 3) at org.jboss.ejb.Container.invoke(Container.java:726) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.jav a:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:184) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:480) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:9 0) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav a:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:173) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85) at $Proxy46.findByPrimaryKey(Unknown Source) at org.jboss.test.deadlock.bean.StatelessSessionBean.callAB(StatelessSessio nBean.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stat elessSessionContainer.java:683) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke( CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Statele ssSessionInstanceInterceptor.java:72) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce ptor.java:84) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor CMT.java:313) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:147) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav a:118) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryF inderInterceptor.java:122) at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionC ontainer.java:331) at org.jboss.ejb.Container.invoke(Container.java:706) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja va:701) at java.lang.Thread.run(Thread.java:534) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Wednesday, January 21, 2004 4:41 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja va:701) at java.lang.Thread.run(Thread.java:534) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Thursday, January 22, 2004 7:29 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 2004-01-22 12:15:06,862 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException: java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:354) at org.jboss.tm.TransactionImpl.associateCurrentThread(Transactio nImpl.java :760) at org.jboss.tm.TxManager.associateThread(TxManager.java:369) at org.jboss.tm.TxManager.resume(TxManager.java:217) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI nterceptor CMT.java:417) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxIntercepto rCMT.java: 127) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityI nterceptor .java:92) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor .java:120) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome (ProxyFact oryFinderInterceptor.java:93) at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContain er.java:48 3) at org.jboss.ejb.Container.invoke(Container.java:726) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDisp atcher.jav a:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:45) at org.jboss.mx.server.Invocation.invoke(Invocation.java:70) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanI nvoker.jav a:184) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:480) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerIntercep tor.java:9 0) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInter ceptor.jav a:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor .java:45) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:173) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85) at $Proxy46.findByPrimaryKey(Unknown Source) at org.jboss.test.deadlock.bean.StatelessSessionBean.callAB(State lessSessio nBean.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.i nvoke(Stat elessSessionContainer.java:683) at org.jboss.resource.connectionmanager.CachedConnectionIntercept or.invoke( CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invo ke(Statele ssSessionInstanceInterceptor.java:72) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(Abstrac tTxInterce ptor.java:84) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxI nterceptor CMT.java:313) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT .java:147) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInter ceptor.jav a:118) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(Pro xyFactoryF inderInterceptor.java:122) at org.jboss.ejb.StatelessSessionContainer.internalInvoke(Statele ssSessionC ontainer.java:331) at org.jboss.ejb.Container.invoke(Container.java:706) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
Hi alls! I am working on org.jboss.test.jmx.test.EarDeploymentUnitTestCase: the test is not falling but the current implementation on EjbModule can give ClassLoader leak (WebClassLoader does not removed). I am also working to minimize the ClassLoaders leak, but this is another story. I try to explain this in another email. I have little patches on security and EJBSpecUnitTestCase: the security Provider must no be removed if it is not added. I'll commit shortly these patches. This is the report which I have when I run the testsuite in WindowsNT j2sdk 1.4.2_03 (single jboss, no cluster). I try to understand why I some errors that I don't have in linux. Claudio -- DETAILS OF ERRORS Suite: org.jboss.test.cache.test.replicated.AsyncUnitTestCase Test:testStateTransfer Type:failure Exception: junit.framework.AssertionFailedError Message: expected:2 but was:3 - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNoTx_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNoTx_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.jca.test.BaseConnectionManagerStressTestCase Test:testShortBlockingAggressiveRemoval Type:failure Exception: junit.framework.AssertionFailedError Message: Wrong number of connections counted: 2 - Suite: org.jboss.test.jmx.test.DeployServiceUnitTestCase Test:testSpaceInClasspath Type:error Exception: org.jboss.deployment.DeploymentException Message: create operation failed for package file:/D:/java/repositories/jboss/jboss-3.2-clean/testsuite/output/lib/archiv estest-service.xml; - nested throwable: (org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.test.jmx.mbean.TestDeployer; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.test.jmx.mbean.TestDeployer)) - Suite: org.jboss.test.management.test.JSR77SpecUnitTestCase Test:testNotificationDeliver Type:failure Exception: junit.framework.AssertionFailedError Message: Not enough notifications received: 0 - Suite: org.jboss.test.management.test.JSR77SpecUnitTestCase Test:testNavigation Type:error Exception: java.lang.reflect.UndeclaredThrowableException Message: - Suite: org.jboss.test.naming.test.SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: org.jboss.test.naming.test.SimpleUnitTestCase Test:testNameChanges Type:failure Exception: junit.framework.AssertionFailedError Message: name.equals(copy), name=jmx - Suite: org.jboss.test.naming.test.SimpleUnitTestCase Test:testHaParitionName Type:error Exception: javax.naming.CommunicationException Message: Receive timed out - Suite: org.jboss.test.naming.test.SimpleUnitTestCase Test:testDiscoveryPort
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
Out of these failures, the following need to be resolved before the 3.2.4RC1 release: Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase Test:testStrictPooling Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Suite: org.jboss.test.security.test.EJBSpecUnitTestCase Test:testMDBRunAs Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testDeadLock Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFail Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailNotSupportedReentrant Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailCMR Suite: org.jboss.test.jca.test.CachedConnectionBankStressTestCase Test:testCachedConnectionBank Suite: org.jboss.test.lock.test.EnterpriseEntityStressTestCase Test:unknown The remainder are known issues. I'm working on the DeployXMBeanUnitTestCase and EJBSpecUnitTestCase failures. I need to know who is looking into the others. Scott Stark Chief Technology Officer JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Sunday, January 18, 2004 12:50 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 JBoss daily test results SUMMARY Number of tests run: 1639 Successful tests: 1620 Errors:9 Failures: 10 [time of test: 2004-01-18.20-08 GMT] [java.version: 1.4.2_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2004-01-18.20-08 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
I am looking into deadlock. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, January 20, 2004 11:34 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Out of these failures, the following need to be resolved before the 3.2.4RC1 release: Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase Test:testStrictPooling Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Suite: org.jboss.test.security.test.EJBSpecUnitTestCase Test:testMDBRunAs Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testDeadLock Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFail Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailNotSupportedReentrant Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailCMR Suite: org.jboss.test.jca.test.CachedConnectionBankStressTestCase Test:testCachedConnectionBank Suite: org.jboss.test.lock.test.EnterpriseEntityStressTestCase Test:unknown The remainder are known issues. I'm working on the DeployXMBeanUnitTestCase and EJBSpecUnitTestCase failures. I need to know who is looking into the others. Scott Stark Chief Technology Officer JBoss Group, LLC --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
Sometimes, running deadlock test I see java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:354) at org.jboss.tm.TransactionImpl.associateCurrentThread(TransactionImpl.java :760) isn't it a bug in ArrayList impl? [EMAIL PROTECTED] testsuite]$ java -version java version 1.4.2_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, January 20, 2004 11:34 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Out of these failures, the following need to be resolved before the 3.2.4RC1 release: Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase Test:testStrictPooling Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Suite: org.jboss.test.security.test.EJBSpecUnitTestCase Test:testMDBRunAs Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testDeadLock Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFail Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailNotSupportedReentrant Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailCMR Suite: org.jboss.test.jca.test.CachedConnectionBankStressTestCase Test:testCachedConnectionBank Suite: org.jboss.test.lock.test.EnterpriseEntityStressTestCase Test:unknown The remainder are known issues. I'm working on the DeployXMBeanUnitTestCase and EJBSpecUnitTestCase failures. I need to know who is looking into the others. Scott Stark Chief Technology Officer JBoss Group, LLC --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
In java.lang.System.arraycopy... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Wednesday, January 21, 2004 3:44 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Sometimes, running deadlock test I see java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:354) at org.jboss.tm.TransactionImpl.associateCurrentThread(Transactio nImpl.java :760) isn't it a bug in ArrayList impl? [EMAIL PROTECTED] testsuite]$ java -version java version 1.4.2_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
Not likely. I would guess this is due to concurrent access to the unsynchronized threads ArrayList. What is the full stack that producing this error? Scott Stark Chief Technology Officer JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: Tuesday, January 20, 2004 5:44 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 Sometimes, running deadlock test I see java.lang.ArrayIndexOutOfBoundsException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.ensureCapacity(ArrayList.java:170) at java.util.ArrayList.add(ArrayList.java:354) at org.jboss.tm.TransactionImpl.associateCurrentThread(TransactionImpl.java :760) isn't it a bug in ArrayList impl? [EMAIL PROTECTED] testsuite]$ java -version java version 1.4.2_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004
Automated JBoss(Branch_3_2 WonderLand) Testsuite Results: 18-January-2004 JBoss daily test results SUMMARY Number of tests run: 1639 Successful tests: 1620 Errors:9 Failures: 10 [time of test: 2004-01-18.20-08 GMT] [java.version: 1.4.2_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_03-b02] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.20-9smp] Useful resources: - http://jboss.sourceforge.net//junit-results/32/2004-01-18.20-08 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: org.jboss.test.cts.test.StatefulSessionUnitTestCase Test:testStrictPooling Type:failure Exception: junit.framework.AssertionFailedError Message: SessionInvoker.runEx != null - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_remote Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionInTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.exception.EntityExceptionUnitTestCase Test:testNotDiscardedApplicationExceptionNewTxMarkRollback_local Type:error Exception: net.sourceforge.junitejb.RemoteTestException Message: Error, bean instance was discarded! - Suite: org.jboss.test.jmx.test.DeployXMBeanUnitTestCase Test:testUserXMBeanPersistentValues Type:failure Exception: junit.framework.AssertionFailedError Message: value == UpdatedAttr1Value, value=Att1InitialValue - Suite: org.jboss.test.naming.test.SimpleUnitTestCase Test:testNameChanges Type:failure Exception: junit.framework.AssertionFailedError Message: name.equals(copy), name=jmx - Suite: org.jboss.test.webservice.external.ExternalUnitTestCase Test:testFederated Type:failure Exception: junit.framework.ComparisonFailure Message: got the translation right expected:JBoss ist ein M�rderbediener und Herr Fleury ist ein verdammtes Genie but was:This service is currently disabled. - Suite: org.jboss.test.naming.test.SecurityUnitTestCase Test:testSecureHttpInvoker Type:failure Exception: junit.framework.AssertionFailedError Message: Should not have been able to lookup(invokers) - Suite: org.jboss.test.security.test.EJBSpecUnitTestCase Test:testMDBRunAs Type:error Exception: java.lang.NullPointerException Message: - Suite: org.jboss.test.security.test.HttpsUnitTestCase Test:testHttpsURL Type:error Exception: java.io.IOException Message: Failed to readURL, ex=null - Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testDeadLock Type:failure Exception: junit.framework.AssertionFailedError Message: testing of deadlock AB BA scenario failed - Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFail Type:failure Exception: junit.framework.AssertionFailedError Message: Unexpected exception - Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailNotSupportedReentrant Type:failure Exception: junit.framework.AssertionFailedError Message: Unexpected exception - Suite: org.jboss.test.deadlock.test.BeanStressTestCase Test:testAllCompleteOrFailCMR Type:failure Exception: junit.framework.AssertionFailedError Message: Unexpected
