Re: Anyone else seing J2EE Schema unit test failures?
I wiped my .m2 repo and rebuilt from a clean checkout and everything worked. Thanks. -Donald David Jencks wrote: My guess would be that you don't have the most recent xmlbeans schema compilation jars, compiled with xmlbeans 2.3.0. Have you tried mvn -U? thanks david jencks On Jul 22, 2007, at 7:37 PM, Donald Woods wrote: I'm seeing a unit test failure on Linux in J2EE Schema on the latest trunk - --- Test set: org.apache.geronimo.schema.SchemaConversionUtilsTest --- Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.7 sec <<< FAILURE! testGetNestedObjectAsType(org.apache.geronimo.schema.SchemaConversionUtilsTest) Time elapsed: 0.013 sec <<< ERROR! java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) message="org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem;">java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.&clinit&(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) -Donald [EMAIL PROTECTED] wrote: OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO] smime.p7s Description: S/MIME Cryptographic Signature
Re: Anyone else seing J2EE Schema unit test failures?
On 7/23/07, Peter Petersson <[EMAIL PROTECTED]> wrote: I also have this problem sins last night CET. I will try davids suggestion. Hehe, I couldn't resist to comment it once I had seen CET mentioned - at last someone who works (CET) when others sleep (PST) ;-) Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Anyone else seing J2EE Schema unit test failures?
I also have this problem sins last night CET. I will try davids suggestion. thanks Peter Donald Woods wrote: I'm seeing a unit test failure on Linux in J2EE Schema on the latest trunk - --- Test set: org.apache.geronimo.schema.SchemaConversionUtilsTest --- Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.7 sec <<< FAILURE! testGetNestedObjectAsType(org.apache.geronimo.schema.SchemaConversionUtilsTest) Time elapsed: 0.013 sec <<< ERROR! java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) message="org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem;">java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.&clinit&(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) -Donald [EMAIL PROTECTED] wrote: OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO]
Re: Anyone else seing J2EE Schema unit test failures?
My guess would be that you don't have the most recent xmlbeans schema compilation jars, compiled with xmlbeans 2.3.0. Have you tried mvn -U? thanks david jencks On Jul 22, 2007, at 7:37 PM, Donald Woods wrote: I'm seeing a unit test failure on Linux in J2EE Schema on the latest trunk - -- - Test set: org.apache.geronimo.schema.SchemaConversionUtilsTest -- - Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.7 sec <<< FAILURE! testGetNestedObjectAsType (org.apache.geronimo.schema.SchemaConversionUtilsTest) Time elapsed: 0.013 sec <<< ERROR! java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType. (Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObje ctAsType(SchemaConversionUtilsTest.java:150) message="org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader (Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/ SchemaTypeSystem;">java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.&clinit& (Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObje ctAsType(SchemaConversionUtilsTest.java:150) -Donald [EMAIL PROTECTED] wrote: OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/ ~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] - --- [ERROR] BUILD FAILURE [INFO] - --- [INFO] You must specify at least one goal. Try 'install' [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: < 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO] - ---
Anyone else seing J2EE Schema unit test failures?
I'm seeing a unit test failure on Linux in J2EE Schema on the latest trunk - --- Test set: org.apache.geronimo.schema.SchemaConversionUtilsTest --- Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.7 sec <<< FAILURE! testGetNestedObjectAsType(org.apache.geronimo.schema.SchemaConversionUtilsTest) Time elapsed: 0.013 sec <<< ERROR! java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) message="org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem;">java.lang.NoSuchMethodError: org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; at org.apache.geronimo.xbeans.javaee.EjbJarType.&clinit&(Unknown Source) at org.apache.geronimo.schema.SchemaConversionUtilsTest.testGetNestedObjectAsType(SchemaConversionUtilsTest.java:150) -Donald [EMAIL PROTECTED] wrote: OpenEJB trunk at 558558 Geronimo Revision: 558562 built with tests skipped See the full build-1800.log file at http://people.apache.org/~prasad/binaries/20070722/build-1800.log Building Geronimo trunk at Revision: 558562 Building OpenEJB trunk at 558558 [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Sun Jul 22 20:36:18 EDT 2007 [INFO] Final Memory: 2M/504M [INFO] smime.p7s Description: S/MIME Cryptographic Signature
Re: unit test failures
Hi Jacek & all, I've discovered that the most recent Jrockit VM + ApacheDS 1.0 RC1 will completely solve the problem with the org.apache.geronimo.directory.RunningTest hang on Jrockit (see the discussion at DIRECTORY-607 for details). Moreover, I've seen some other posts with signs of dissatisfaction with the outdated version of Apache DS currently being used. So it seems that we need to move Geronimo to ApacheDS 1.0 anyway. I can start working on the corresponding patch. Any comments & objections? 2006/4/14, Alexei Zakharov <[EMAIL PROTECTED]>: > Hi Jacek, > > > It seems not to be a problem any more since we can be ensured you'll > > back up our efforts, won't you? ;) > > Ok, I will try. :) > Currently, ApacheDS guys argue about this bug: does it really ApacheDS > bug? You may see the discussion at > http://issues.apache.org/jira/browse/DIRSERVER-607 > > > 2006/4/11, Jacek Laskowski <[EMAIL PROTECTED]>: > > On 4/11/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > > > However, they use different API since ApacheDS 1.0 > > > RC1, some packages are renamed. Some efforts will be required to > > > rewrite the Geronimo portion of the code. > > > > Hi Alexei, > > > > It seems not to be a problem any more since we can be ensured you'll > > back up our efforts, won't you? ;) > > > > Do you happen to know when they're going to release the fixed version? > > Any estimates? -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
Hi Jacek, > It seems not to be a problem any more since we can be ensured you'll > back up our efforts, won't you? ;) Ok, I will try. :) Currently, ApacheDS guys argue about this bug: does it really ApacheDS bug? You may see the discussion at http://issues.apache.org/jira/browse/DIRSERVER-607 2006/4/11, Jacek Laskowski <[EMAIL PROTECTED]>: > On 4/11/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > > > However, they use different API since ApacheDS 1.0 > > RC1, some packages are renamed. Some efforts will be required to > > rewrite the Geronimo portion of the code. > > Hi Alexei, > > It seems not to be a problem any more since we can be ensured you'll > back up our efforts, won't you? ;) > > Do you happen to know when they're going to release the fixed version? > Any estimates? > > Jacek -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
On 4/11/06, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > However, they use different API since ApacheDS 1.0 > RC1, some packages are renamed. Some efforts will be required to > rewrite the Geronimo portion of the code. Hi Alexei, It seems not to be a problem any more since we can be ensured you'll back up our efforts, won't you? ;) Do you happen to know when they're going to release the fixed version? Any estimates? Jacek -- Jacek Laskowski http://www.laskowski.org.pl
Re: unit test failures
Hi Kevan, > FYI: Apache DS is here -- http://directory.apache.org/subprojects/ > apacheds/index.html The bug is reproducible on their latest stable build also. I think it is best to wait until ApacheDS team fix the bug and incorporate their patched build then. However, they use different API since ApacheDS 1.0 RC1, some packages are renamed. Some efforts will be required to rewrite the Geronimo portion of the code. 2006/4/5, Alexei Zakharov <[EMAIL PROTECTED]>: > Kevan, > > > FYI: Apache DS is here -- http://directory.apache.org/subprojects/ > > Thanks! I will try their recent builds. > > 2006/4/5, Kevan Miller <[EMAIL PROTECTED]>: > > > > On Apr 5, 2006, at 7:58 AM, Alexei Zakharov wrote: > > > > > Hi Kevan, > > > > > > This is follow-up to the story about BEA VMs. I have analyzed > > > org.apache.geronimo.directory.RunningTest (modules/directory) failure > > > on BEA JRockit. I've raised the JIRA issue #1805 > > > (http://issues.apache.org/jira/browse/GERONIMO-1805) with the detailed > > > result of my investigation. In brief, IMHO there is some problem with > > > LDAP server built in Geronimo. As far as I understand LDAP server is > > > not part of Geronimo itself but is an independent component. It is > > > part of some "apacheds-core" package. Therefore, it seems the problem > > > is not a "pure" Geronimo problem. Do anybody knows from where apacheds > > > comes from? Is it a separate Apache project? > > > > Hi Alexei, > > Thanks! I haven't looked at the Jira, yet, but will soon... > > > > FYI: Apache DS is here -- http://directory.apache.org/subprojects/ > > apacheds/index.html > > > > --kevan > > > > > > > > > > This is follow-up to the story about BEA VMs. I have analized > > > > > > 2006/3/21, Kevan Miller <[EMAIL PROTECTED]>: > > >> > > >> > > >> On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote: > > >> > > >> Hi Kevan, > > >> > > >> I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. > > >> Therefore, > > >> this was a "pure JRockit" experiment. > > >> > > >> As for dependencies from Sun, AFAIK there are a few non-CORBA > > >> places in > > >> code with "com.sun" hardcoded. This issue has been rised recently > > >> in the > > >> list. You may check "Using non-Sun JNDI/RMI service provider" > > >> thread for > > >> details. > > >> > > >> Ok, I will continue investigation of these failures. BTW, if you are > > >> interested in BEA 1.5 I attach the JRockit 1.5 failure log. > > >> Messages are > > >> direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven > > >> 1.0.2 to > > >> obtain these results. > > >> > > >> > > >> Hi Alexei, > > >> Thanks. Let us know what you find. > > >> > > >> Looks like the majority of the 1.5 problems are "environmental" > > >> something to > > >> do with the junit environment on JRockit 1.5. The "kernel is > > >> already running > > >> this kernel name: geronimo.test" and "runFinalizer" messages seem > > >> to imply > > >> that you're seeing collisions between Junit tests on different > > >> components... > > >> > > >> --kevan > > >> > > >> > > >> Regards, > > >> Alexei > > >> > > >> 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: > > >>> > > >>> Hi Alexei, > > >>> Thanks for the information. Are you both building running > > >>> tests with > > >> JRockit? Or are you building w/ Sun and only running tests under > > >> JRockit? > > >> Would be good to isolate the two. Good chance, however, that it > > >> won't make > > >> any difference... > > >>> > > >>> > > >>> Geronimo currently has direct ties to the Sun 1.4 corba > > >>> implementation. > > >> That's the only JRE restriction that I'm aware of. People have run > > >> Geronimo > > >> on Sun 1.5 and also on IBM's 1.4 JRE. > > >>> > > >>> > > >>> It seems that the tests you describe to work. There's a > > >>> reasonable > > >> chance that these are Geronimo bugs that are masked by our current > > >> runtime. > > >> So, it would be great if you could help us uncover the causes of > > >> these > > >> failures. > > >>> > > >>> > > >>> I don't know why JRockit 1.5 would be worse. > > >>> > > >>> > > >>> --kevan > > >>> > > >>> > > >>> > > >>> On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: > > >>> > > >>> > > >>> > > >>> Hi, community! > > >>> > > >>> I experiment with running Geronimo on various JVM's. The > > >>> interesting thing > > >> I've encountered is that some of unit tests fail on BEA Jrockit > > >> VM. I've got > > >> at least three failures unique to BEA Jrockit 1.4.2_04 VM: > > >>> > > >>> Module: modules/directory > > >>> Test: org.apache.geronimo.directory.RunningTest > > >>> Result: VM hangs > > >>> > > >>> Module: modules/timer > > >>> Test: > > >> org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testT > > >> asksInUnspecifiedTxContext > > >>> Output: expected:<20> but was:<19> > > >>> > > >>> Module: modules/tomcat > > >>> Test: > > >> org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized > > >>> Output: expected:<> but was: > > >>> > > >>> These tests pa
Re: unit test failures [Directory Problem]
Genender might have an idea. Alexei Zakharov wrote: Hi Kevan, This is follow-up to the story about BEA VMs. I have analyzed org.apache.geronimo.directory.RunningTest (modules/directory) failure on BEA JRockit. I've raised the JIRA issue #1805 (http://issues.apache.org/jira/browse/GERONIMO-1805) with the detailed result of my investigation. In brief, IMHO there is some problem with LDAP server built in Geronimo. As far as I understand LDAP server is not part of Geronimo itself but is an independent component. It is part of some "apacheds-core" package. Therefore, it seems the problem is not a "pure" Geronimo problem. Do anybody knows from where apacheds comes from? Is it a separate Apache project? This is follow-up to the story about BEA VMs. I have analized 2006/3/21, Kevan Miller <[EMAIL PROTECTED]>: On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote: Hi Kevan, I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. Therefore, this was a "pure JRockit" experiment. As for dependencies from Sun, AFAIK there are a few non-CORBA places in code with "com.sun" hardcoded. This issue has been rised recently in the list. You may check "Using non-Sun JNDI/RMI service provider" thread for details. Ok, I will continue investigation of these failures. BTW, if you are interested in BEA 1.5 I attach the JRockit 1.5 failure log. Messages are direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven 1.0.2 to obtain these results. Hi Alexei, Thanks. Let us know what you find. Looks like the majority of the 1.5 problems are "environmental" something to do with the junit environment on JRockit 1.5. The "kernel is already running this kernel name: geronimo.test" and "runFinalizer" messages seem to imply that you're seeing collisions between Junit tests on different components... --kevan Regards, Alexei 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: Hi Alexei, Thanks for the information. Are you both building running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. It seems that the tests you describe to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures. I don't know why JRockit 1.5 would be worse. --kevan On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: Hi, community! I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM: Module: modules/directory Test: org.apache.geronimo.directory.RunningTest Result: VM hangs Module: modules/timer Test: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContext Output: expected:<20> but was:<19> Module: modules/tomcat Test: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized Output: expected:<> but was: These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA. Any comments & suggestions? Alexei Zakharov, Intel Middleware Product Division -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
Kevan, > FYI: Apache DS is here -- http://directory.apache.org/subprojects/ Thanks! I will try their recent builds. 2006/4/5, Kevan Miller <[EMAIL PROTECTED]>: > > On Apr 5, 2006, at 7:58 AM, Alexei Zakharov wrote: > > > Hi Kevan, > > > > This is follow-up to the story about BEA VMs. I have analyzed > > org.apache.geronimo.directory.RunningTest (modules/directory) failure > > on BEA JRockit. I've raised the JIRA issue #1805 > > (http://issues.apache.org/jira/browse/GERONIMO-1805) with the detailed > > result of my investigation. In brief, IMHO there is some problem with > > LDAP server built in Geronimo. As far as I understand LDAP server is > > not part of Geronimo itself but is an independent component. It is > > part of some "apacheds-core" package. Therefore, it seems the problem > > is not a "pure" Geronimo problem. Do anybody knows from where apacheds > > comes from? Is it a separate Apache project? > > Hi Alexei, > Thanks! I haven't looked at the Jira, yet, but will soon... > > FYI: Apache DS is here -- http://directory.apache.org/subprojects/ > apacheds/index.html > > --kevan > > > > > > This is follow-up to the story about BEA VMs. I have analized > > > > 2006/3/21, Kevan Miller <[EMAIL PROTECTED]>: > >> > >> > >> On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote: > >> > >> Hi Kevan, > >> > >> I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. > >> Therefore, > >> this was a "pure JRockit" experiment. > >> > >> As for dependencies from Sun, AFAIK there are a few non-CORBA > >> places in > >> code with "com.sun" hardcoded. This issue has been rised recently > >> in the > >> list. You may check "Using non-Sun JNDI/RMI service provider" > >> thread for > >> details. > >> > >> Ok, I will continue investigation of these failures. BTW, if you are > >> interested in BEA 1.5 I attach the JRockit 1.5 failure log. > >> Messages are > >> direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven > >> 1.0.2 to > >> obtain these results. > >> > >> > >> Hi Alexei, > >> Thanks. Let us know what you find. > >> > >> Looks like the majority of the 1.5 problems are "environmental" > >> something to > >> do with the junit environment on JRockit 1.5. The "kernel is > >> already running > >> this kernel name: geronimo.test" and "runFinalizer" messages seem > >> to imply > >> that you're seeing collisions between Junit tests on different > >> components... > >> > >> --kevan > >> > >> > >> Regards, > >> Alexei > >> > >> 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: > >>> > >>> Hi Alexei, > >>> Thanks for the information. Are you both building running > >>> tests with > >> JRockit? Or are you building w/ Sun and only running tests under > >> JRockit? > >> Would be good to isolate the two. Good chance, however, that it > >> won't make > >> any difference... > >>> > >>> > >>> Geronimo currently has direct ties to the Sun 1.4 corba > >>> implementation. > >> That's the only JRE restriction that I'm aware of. People have run > >> Geronimo > >> on Sun 1.5 and also on IBM's 1.4 JRE. > >>> > >>> > >>> It seems that the tests you describe to work. There's a > >>> reasonable > >> chance that these are Geronimo bugs that are masked by our current > >> runtime. > >> So, it would be great if you could help us uncover the causes of > >> these > >> failures. > >>> > >>> > >>> I don't know why JRockit 1.5 would be worse. > >>> > >>> > >>> --kevan > >>> > >>> > >>> > >>> On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: > >>> > >>> > >>> > >>> Hi, community! > >>> > >>> I experiment with running Geronimo on various JVM's. The > >>> interesting thing > >> I've encountered is that some of unit tests fail on BEA Jrockit > >> VM. I've got > >> at least three failures unique to BEA Jrockit 1.4.2_04 VM: > >>> > >>> Module: modules/directory > >>> Test: org.apache.geronimo.directory.RunningTest > >>> Result: VM hangs > >>> > >>> Module: modules/timer > >>> Test: > >> org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testT > >> asksInUnspecifiedTxContext > >>> Output: expected:<20> but was:<19> > >>> > >>> Module: modules/tomcat > >>> Test: > >> org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized > >>> Output: expected:<> but was: > >>> > >>> These tests pass on all Sun VMs. Situation with Jrockit 1.5 is > >>> much worse > >> - more than 60 failures. It may result in overall instability > >> while running > >> Geronimo on BEA. > >>> Any comments & suggestions? > >>> > >>> Alexei Zakharov, > >>> Intel Middleware Product Division > >>> > >>> > >> > >> > >> > >> > >> > > > > > > -- > > Alexei Zakharov, > > Intel Middleware Product Division > > -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
On Apr 5, 2006, at 7:58 AM, Alexei Zakharov wrote: Hi Kevan, This is follow-up to the story about BEA VMs. I have analyzed org.apache.geronimo.directory.RunningTest (modules/directory) failure on BEA JRockit. I've raised the JIRA issue #1805 (http://issues.apache.org/jira/browse/GERONIMO-1805) with the detailed result of my investigation. In brief, IMHO there is some problem with LDAP server built in Geronimo. As far as I understand LDAP server is not part of Geronimo itself but is an independent component. It is part of some "apacheds-core" package. Therefore, it seems the problem is not a "pure" Geronimo problem. Do anybody knows from where apacheds comes from? Is it a separate Apache project? Hi Alexei, Thanks! I haven't looked at the Jira, yet, but will soon... FYI: Apache DS is here -- http://directory.apache.org/subprojects/ apacheds/index.html --kevan This is follow-up to the story about BEA VMs. I have analized 2006/3/21, Kevan Miller <[EMAIL PROTECTED]>: On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote: Hi Kevan, I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. Therefore, this was a "pure JRockit" experiment. As for dependencies from Sun, AFAIK there are a few non-CORBA places in code with "com.sun" hardcoded. This issue has been rised recently in the list. You may check "Using non-Sun JNDI/RMI service provider" thread for details. Ok, I will continue investigation of these failures. BTW, if you are interested in BEA 1.5 I attach the JRockit 1.5 failure log. Messages are direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven 1.0.2 to obtain these results. Hi Alexei, Thanks. Let us know what you find. Looks like the majority of the 1.5 problems are "environmental" something to do with the junit environment on JRockit 1.5. The "kernel is already running this kernel name: geronimo.test" and "runFinalizer" messages seem to imply that you're seeing collisions between Junit tests on different components... --kevan Regards, Alexei 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: Hi Alexei, Thanks for the information. Are you both building running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. It seems that the tests you describe to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures. I don't know why JRockit 1.5 would be worse. --kevan On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: Hi, community! I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM: Module: modules/directory Test: org.apache.geronimo.directory.RunningTest Result: VM hangs Module: modules/timer Test: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testT asksInUnspecifiedTxContext Output: expected:<20> but was:<19> Module: modules/tomcat Test: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized Output: expected:<> but was: These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA. Any comments & suggestions? Alexei Zakharov, Intel Middleware Product Division -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
Hi Kevan, This is follow-up to the story about BEA VMs. I have analyzed org.apache.geronimo.directory.RunningTest (modules/directory) failure on BEA JRockit. I've raised the JIRA issue #1805 (http://issues.apache.org/jira/browse/GERONIMO-1805) with the detailed result of my investigation. In brief, IMHO there is some problem with LDAP server built in Geronimo. As far as I understand LDAP server is not part of Geronimo itself but is an independent component. It is part of some "apacheds-core" package. Therefore, it seems the problem is not a "pure" Geronimo problem. Do anybody knows from where apacheds comes from? Is it a separate Apache project? This is follow-up to the story about BEA VMs. I have analized 2006/3/21, Kevan Miller <[EMAIL PROTECTED]>: > > > On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote: > > Hi Kevan, > > I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. Therefore, > this was a "pure JRockit" experiment. > > As for dependencies from Sun, AFAIK there are a few non-CORBA places in > code with "com.sun" hardcoded. This issue has been rised recently in the > list. You may check "Using non-Sun JNDI/RMI service provider" thread for > details. > > Ok, I will continue investigation of these failures. BTW, if you are > interested in BEA 1.5 I attach the JRockit 1.5 failure log. Messages are > direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven 1.0.2 to > obtain these results. > > > Hi Alexei, > Thanks. Let us know what you find. > > Looks like the majority of the 1.5 problems are "environmental" something to > do with the junit environment on JRockit 1.5. The "kernel is already running > this kernel name: geronimo.test" and "runFinalizer" messages seem to imply > that you're seeing collisions between Junit tests on different components... > > --kevan > > > Regards, > Alexei > > 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: > > > > Hi Alexei, > > Thanks for the information. Are you both building running tests with > JRockit? Or are you building w/ Sun and only running tests under JRockit? > Would be good to isolate the two. Good chance, however, that it won't make > any difference... > > > > > > Geronimo currently has direct ties to the Sun 1.4 corba implementation. > That's the only JRE restriction that I'm aware of. People have run Geronimo > on Sun 1.5 and also on IBM's 1.4 JRE. > > > > > > It seems that the tests you describe to work. There's a reasonable > chance that these are Geronimo bugs that are masked by our current runtime. > So, it would be great if you could help us uncover the causes of these > failures. > > > > > > I don't know why JRockit 1.5 would be worse. > > > > > > --kevan > > > > > > > > On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: > > > > > > > > Hi, community! > > > > I experiment with running Geronimo on various JVM's. The interesting thing > I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got > at least three failures unique to BEA Jrockit 1.4.2_04 VM: > > > > Module: modules/directory > > Test: org.apache.geronimo.directory.RunningTest > > Result: VM hangs > > > > Module: modules/timer > > Test: > org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContext > > Output: expected:<20> but was:<19> > > > > Module: modules/tomcat > > Test: > org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized > > Output: expected:<> but was: > > > > These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse > - more than 60 failures. It may result in overall instability while running > Geronimo on BEA. > > Any comments & suggestions? > > > > Alexei Zakharov, > > Intel Middleware Product Division > > > > > > > > > -- Alexei Zakharov, Intel Middleware Product Division
Re: unit test failures
On Mar 20, 2006, at 1:19 PM, Alexei Zakharov wrote:Hi Kevan, I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. Therefore, this was a "pure JRockit" experiment. As for dependencies from Sun, AFAIK there are a few non-CORBA places in code with "com.sun" hardcoded. This issue has been rised recently in the list. You may check "Using non-Sun JNDI/RMI service provider" thread for details. Ok, I will continue investigation of these failures. BTW, if you are interested in BEA 1.5 I attach the JRockit 1.5 failure log. Messages are direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven 1.0.2 to obtain these results. Hi Alexei,Thanks. Let us know what you find. Looks like the majority of the 1.5 problems are "environmental" something to do with the junit environment on JRockit 1.5. The "kernel is already running this kernel name: geronimo.test" and "runFinalizer" messages seem to imply that you're seeing collisions between Junit tests on different components...--kevan Regards, Alexei 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: Hi Alexei, Thanks for the information. Are you both building running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. It seems that the tests you describe to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures. I don't know why JRockit 1.5 would be worse. --kevan On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: Hi, community!I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM:Module: modules/directoryTest: org.apache.geronimo.directory.RunningTest Result: VM hangsModule: modules/timerTest: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContextOutput: expected:<20> but was:<19>Module: modules/tomcatTest: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorizedOutput: expected:<> but was:These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA.Any comments & suggestions?Alexei Zakharov,Intel Middleware Product Division
Re: unit test failures
Hi Kevan, I was lucky to build it using JRockit 1.4.2 + Maven 1.1 Beta. Therefore, this was a "pure JRockit" experiment. As for dependencies from Sun, AFAIK there are a few non-CORBA places in code with "com.sun" hardcoded. This issue has been rised recently in the list. You may check "Using non-Sun JNDI/RMI service provider" thread for details. Ok, I will continue investigation of these failures. BTW, if you are interested in BEA 1.5 I attach the JRockit 1.5 failure log. Messages are direct JUnit messages. I was using JRockit 1.5.0-b64 win32 + maven 1.0.2 to obtain these results. Regards, Alexei 2006/3/18, Kevan Miller <[EMAIL PROTECTED]>: Hi Alexei, Thanks for the information. Are you both building running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. It seems that the tests you describe to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures. I don't know why JRockit 1.5 would be worse. --kevan On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote: Hi, community! I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM: Module: modules/directoryTest: org.apache.geronimo.directory.RunningTest Result: VM hangs Module: modules/timerTest: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContextOutput: expected:<20> but was:<19> Module: modules/tomcatTest: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorizedOutput: expected:<> but was: These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA.Any comments & suggestions? Alexei Zakharov,Intel Middleware Product Division Failed tests C:/Java/geronimo-1.0-src/modules/common org.apache.geronimo.common.propertyeditor.PropertyEditorsTest testDefaultEditorSearchPathMessage: 1 C:/Java/geronimo-1.0-src/modules/connector org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapperTest testSerializationMessage: 2 testProxyMessage: 3 C:/Java/geronimo-1.0-src/modules/connector-builder org.apache.geronimo.connector.deployment.ConnectorModuleBuilderTest testBuildPackedModule15Message: 4 testBuildUnpackedModule15Message: 5 testBuildPackedModuleMessage: 6 testBuildUnpackedAltSpecVendorDDModuleMessage: 7 testBuildUnpackedAltVendorDDModuleMessage: 8 testBuildUnpackedAltSpecDDModuleMessage: 9 testBuildUnpackedModuleMessage: 10 testBuildEarMessage: 11 C:/Java/geronimo-1.0-src/modules/directory org.apache.geronimo.directory.RunningTest testRunningMessage: 12 C:/Java/geronimo-1.0-src/modules/j2ee org.apache.geronimo.j2ee.management.DomainTest testStandardAttributesMessage: 13 testStandardInterfaceMessage: 14 org.apache.geronimo.j2ee.management.JVMTest testStatisticsMessage: 15 testGeronimoAttributesMessage: 16 testGeronimoInterfaceMessage: 17 testStandardAttributesMessage: 18 testStandardInterfaceMessage: 19 org.apache.geronimo.j2ee.management.ServerTest testStandardAttributesMessage: 20 testStandardInterfaceMessage: 21 C:/Java/geronimo-1.0-src/modules/j2ee-builder org.apache.geronimo.j2ee.deployment.EARConfigBuilderTest testBuildConfigurationMessage: 22 testBuildConfigurationMessage: 23 testBuildConfigurationMessage: 24 testBuildConfigurationMessage: 25 testBuildConfigurationMessage: 26 testBuildConfigurationMessage: 27 testBuildConfigurationMessage: 28 testBuildConfigurationMessage: 29 C:/Java/geronimo-1.0-src/modules/jetty org.apache.geronimo.jetty.ApplicationTest testApplicationMessage: 30 testDummyMessage: 31 org.apache.geronimo.jetty.ContainerTest testWebServiceHandlerMessage: 32 testHTTPConnectorMessage: 33 org.apache.geronimo.jetty.SecurityTest testExplicitMappingMessage: 34 testDummyMessage: 35 C:/Java/geronimo-1.0-src/modules/jetty-builder org.apache.geronimo.jetty.deployment.JettyModuleBuilderTest testDeployWar4Message: 36 C:/Java/geronimo-1.0-src/modules/kernel org.apache.geronimo.kernel.ConfigTest testAddToConfigMessage: 37 testOnlineConfigMessage: 38 org.apache.geronimo.kernel.GBeanTest testProxiesInterfacesMessage: 39 testEndpointMessage: 40 C:/Java/geronimo-1.0-src/modules/security org.apache.geronimo.security.jaas.ConfigurationEntryTest testMessage: 41 org.apache.geronimo.security.jaas.LoginKerberosNonGeronimoTest testLoginMessage: 42 org.apache.geronimo.security.jaas.LoginKerberosTest testLoginMessage: 43 org.apache.ger
Re: unit test failures
Hi Alexei,Thanks for the information. Are you both building running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. It seems that the tests you describe to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures.I don't know why JRockit 1.5 would be worse. --kevan On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote:Hi, community!I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM:Module: modules/directoryTest: org.apache.geronimo.directory.RunningTest Result: VM hangsModule: modules/timerTest: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContextOutput: expected:<20> but was:<19>Module: modules/tomcatTest: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorizedOutput: expected:<> but was:These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA.Any comments & suggestions?Alexei Zakharov,Intel Middleware Product Division
unit test failures
Hi, community! I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM: Module: modules/directoryTest: org.apache.geronimo.directory.RunningTest Result: VM hangs Module: modules/timerTest: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContextOutput: expected:<20> but was:<19> Module: modules/tomcatTest: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorizedOutput: expected:<> but was: These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA.Any comments & suggestions? Alexei Zakharov,Intel Middleware Product Division
