[jira] Created: (GERONIMO-2014) Geronimo uses outdated version of ApacheDS
Geronimo uses outdated version of ApacheDS -- Key: GERONIMO-2014 URL: http://issues.apache.org/jira/browse/GERONIMO-2014 Project: Geronimo Type: Improvement Security: public (Regular issues) Components: naming Versions: 1.2 Environment: P4 3.0Ghz 2Gb WinXP Reporter: Alexei Zakharov Outdated version of Apache Directory Server is currently used by Geronimo. This is a cause of GERONIMO-1805 bug and probably some other issues. Attached patches port Geronimo directory module to ApachedDS 1.0 RC2. It is applicable to maven2 version of config files since ADS 1.0 RCx jars available for m2 repo only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2014) Geronimo uses outdated version of ApacheDS
[ http://issues.apache.org/jira/browse/GERONIMO-2014?page=all ] Alexei Zakharov updated GERONIMO-2014: -- Attachment: geronimo-1.2_to_apacheds-1.0-RC2.patch Geronimo uses outdated version of ApacheDS -- Key: GERONIMO-2014 URL: http://issues.apache.org/jira/browse/GERONIMO-2014 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: naming Versions: 1.2 Environment: P4 3.0Ghz 2Gb WinXP Reporter: Alexei Zakharov Attachments: geronimo-1.2_to_apacheds-1.0-RC2.patch Outdated version of Apache Directory Server is currently used by Geronimo. This is a cause of GERONIMO-1805 bug and probably some other issues. Attached patches port Geronimo directory module to ApachedDS 1.0 RC2. It is applicable to maven2 version of config files since ADS 1.0 RCx jars available for m2 repo only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2014) Geronimo uses outdated version of ApacheDS
[ http://issues.apache.org/jira/browse/GERONIMO-2014?page=all ] Alexei Zakharov updated GERONIMO-2014: -- Attachment: geronimo-1.2_to_apacheds-1.0-RC2_modules_directory_pom_xml.patch Both patches should be applied. Geronimo uses outdated version of ApacheDS -- Key: GERONIMO-2014 URL: http://issues.apache.org/jira/browse/GERONIMO-2014 Project: Geronimo Type: Improvement Security: public(Regular issues) Components: naming Versions: 1.2 Environment: P4 3.0Ghz 2Gb WinXP Reporter: Alexei Zakharov Attachments: geronimo-1.2_to_apacheds-1.0-RC2.patch, geronimo-1.2_to_apacheds-1.0-RC2_modules_directory_pom_xml.patch Outdated version of Apache Directory Server is currently used by Geronimo. This is a cause of GERONIMO-1805 bug and probably some other issues. Attached patches port Geronimo directory module to ApachedDS 1.0 RC2. It is applicable to maven2 version of config files since ADS 1.0 RCx jars available for m2 repo only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Directory Update (Jeff?)
Ok. The patch to port maven2 version of G directory module to ApacheDS 1.0 RC2 is available here: http://issues.apache.org/jira/browse/GERONIMO-2014 It patches pom.xml's as well as java source code and the test. Thanks, 2006/5/11, Alex Karasulu [EMAIL PROTECTED]: Alexei, Sorry but we have not looked back after the M2 conversion. Our poms have changed much since then because of transitive deps so it would take a significant effort to produce the M1 poms again. Really wish we had a tool for this. Regards, Alex Alexei Zakharov wrote: BTW, Alex, are there plans to propagate ADS jars to maven1 repo? Geronimo 1.1 currently supports maven1 only. Thanks, 2006/5/6, Alexei Zakharov [EMAIL PROTECTED]: Alex, Oh, I've been searching in old directory and directory-network groups rather than org/apache/directory/server/apacheds-core. Thank you for pointing the right group id. 2006/5/5, Alex Karasulu [EMAIL PROTECTED]: Alexei Zakharov wrote: Hi, I have created a patch to move the G directory module to ApacheDS 1.0 RC2. But I didn't find necessary 1.0 RCx jars at ibiblio neither at /maven nor at /maven2. The most recent version is 0.9.3. The same situation for MINA. So I can't post the patch right now since it will not work without these jars. Alex, I just want to let you know about this situation. Hmmm I'm seeing the RC2 jars just fine. Take a look here at the core jar for example: http://www.ibiblio.org/maven2/org/apache/directory/server/apacheds-core/1.0-RC2/ Also MINA stuff is here: http://www.ibiblio.org/maven2/org/apache/directory/mina/mina-core/0.9.4/ HTH, Alex 2006/4/24, Alex Karasulu [EMAIL PROTECTED]: Aaron Mulder wrote: I know 0.9.3 is there (in the /maven2 repo). Not sure about the RC's. Ya all including RC1 should be in the M2 repo if not let me know. Alex Thanks, Aaron On 4/24/06, Jeff Genender [EMAIL PROTECTED] wrote: Alex, Can you get the jars in ibiblio and I can get the integration going? I am only seeing 0.9.2 in ibiblio at the moment. Thanks, Jeff Alex Karasulu wrote: Jeff Genender wrote: If the changes are not huge, I can probably do it. Alex, are the updates significant? Since 0.9.2 I'd say RC1 is a significant update. There are package name changes to comply with Directory's TLP domain name which are perhaps the most significant changes. There are changes to a couple dependencies. For the most part the code has been cleaned up and several *severe* bugs have been corrected and tested. RC1 is also an order of magnitude faster. We plan to get another 1.0 release candidate (RC2) out soon perhaps by the end of this week coming week or week there after. But looking at emails out there from Dain and Aaron it sounds to me like the update to G can take place any time after the 1.1 release. Let us know if you have any problems or need a hand while performing an upgrade either to RC1 or RC2 when it comes out. Regards, Alex -- Alexei Zakharov, Intel Middleware Product Division
Re: Directory Update (Jeff?)
BTW, Alex, are there plans to propagate ADS jars to maven1 repo? Geronimo 1.1 currently supports maven1 only. Thanks, 2006/5/6, Alexei Zakharov [EMAIL PROTECTED]: Alex, Oh, I've been searching in old directory and directory-network groups rather than org/apache/directory/server/apacheds-core. Thank you for pointing the right group id. 2006/5/5, Alex Karasulu [EMAIL PROTECTED]: Alexei Zakharov wrote: Hi, I have created a patch to move the G directory module to ApacheDS 1.0 RC2. But I didn't find necessary 1.0 RCx jars at ibiblio neither at /maven nor at /maven2. The most recent version is 0.9.3. The same situation for MINA. So I can't post the patch right now since it will not work without these jars. Alex, I just want to let you know about this situation. Hmmm I'm seeing the RC2 jars just fine. Take a look here at the core jar for example: http://www.ibiblio.org/maven2/org/apache/directory/server/apacheds-core/1.0-RC2/ Also MINA stuff is here: http://www.ibiblio.org/maven2/org/apache/directory/mina/mina-core/0.9.4/ HTH, Alex 2006/4/24, Alex Karasulu [EMAIL PROTECTED]: Aaron Mulder wrote: I know 0.9.3 is there (in the /maven2 repo). Not sure about the RC's. Ya all including RC1 should be in the M2 repo if not let me know. Alex Thanks, Aaron On 4/24/06, Jeff Genender [EMAIL PROTECTED] wrote: Alex, Can you get the jars in ibiblio and I can get the integration going? I am only seeing 0.9.2 in ibiblio at the moment. Thanks, Jeff Alex Karasulu wrote: Jeff Genender wrote: If the changes are not huge, I can probably do it. Alex, are the updates significant? Since 0.9.2 I'd say RC1 is a significant update. There are package name changes to comply with Directory's TLP domain name which are perhaps the most significant changes. There are changes to a couple dependencies. For the most part the code has been cleaned up and several *severe* bugs have been corrected and tested. RC1 is also an order of magnitude faster. We plan to get another 1.0 release candidate (RC2) out soon perhaps by the end of this week coming week or week there after. But looking at emails out there from Dain and Aaron it sounds to me like the update to G can take place any time after the 1.1 release. Let us know if you have any problems or need a hand while performing an upgrade either to RC1 or RC2 when it comes out. Regards, Alex -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom [EMAIL PROTECTED]: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: 1.1 Package Upgrade List
FYI: ADS API has changed significantly since 0.9.2. 2006/5/10, Aaron Mulder [EMAIL PROTECTED]: I'd rather handle the ApacheDS integration separately from the 1.1 release. Fortunately, the plugins work with the Maven 2 repository, so that issue should be easier. The main question is how to do the build and packaging. If the API is unchanged, we can build our integration module using our Maven 1 packaging plugin against ADS 0.9.2 and just have it apply the 1.0.x JARs at installation time. If the API is different, it may make the most sense to try to split out our directory integration and do the build and packaging under Maven 2 (I'm assuming that Geronimo HEAD has a Maven 2 packaging plugin, but if not, I guess we can work on one). Thanks, Aaron On 5/10/06, Alexei Zakharov [EMAIL PROTECTED] wrote: ApacheDS0.9.2 to 1.0-RC2 ? I have a patch to port the Geronimo part to 1.0-RC2. However, currently ADS 1.0 jars propagated to maven2 repo only. 2006/5/9, Matt Hogstrom [EMAIL PROTECTED]: Consolidated list so far is: Axis from 1.4-356167 to 1.4 commons-fileupload 1.1-dev to 1.1 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 Tomcat 5.5.9 to 5.5.15 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT Keep 'em coming. Matt Aaron Mulder wrote: That issue has a great list. We definitely need to try updating commons-fileupload (from 1.1-dev to 1.1). I think there may even be a separate Jira for that. But the old one occasionally hangs, so it's definitely worth trying the new one. Thanks, Aaron On 5/9/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Here are the packages I'm recommending for 1.1. If I missed one please chime in. Axis from 1.4-356167 to 1.4 jasper from 5.5.9 to 5.5.15 Jetty from 5.1.9 to 5.1.10 stax from 1.1.1-dev to 1.1.2 tranql from1.2.1 to 1.3-SNAPSHOT tranql-connector from 1.1 to 1.2-SNAPSHOT This is the list so far...I've updated http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Geronimo+Package+Tracking with this information. Was mentioned on the list: Howl- Researching this -- Alexei Zakharov, Intel Middleware Product Division
Re: Directory Update (Jeff?)
Alex, Oh, I've been searching in old directory and directory-network groups rather than org/apache/directory/server/apacheds-core. Thank you for pointing the right group id. 2006/5/5, Alex Karasulu [EMAIL PROTECTED]: Alexei Zakharov wrote: Hi, I have created a patch to move the G directory module to ApacheDS 1.0 RC2. But I didn't find necessary 1.0 RCx jars at ibiblio neither at /maven nor at /maven2. The most recent version is 0.9.3. The same situation for MINA. So I can't post the patch right now since it will not work without these jars. Alex, I just want to let you know about this situation. Hmmm I'm seeing the RC2 jars just fine. Take a look here at the core jar for example: http://www.ibiblio.org/maven2/org/apache/directory/server/apacheds-core/1.0-RC2/ Also MINA stuff is here: http://www.ibiblio.org/maven2/org/apache/directory/mina/mina-core/0.9.4/ HTH, Alex 2006/4/24, Alex Karasulu [EMAIL PROTECTED]: Aaron Mulder wrote: I know 0.9.3 is there (in the /maven2 repo). Not sure about the RC's. Ya all including RC1 should be in the M2 repo if not let me know. Alex Thanks, Aaron On 4/24/06, Jeff Genender [EMAIL PROTECTED] wrote: Alex, Can you get the jars in ibiblio and I can get the integration going? I am only seeing 0.9.2 in ibiblio at the moment. Thanks, Jeff Alex Karasulu wrote: Jeff Genender wrote: If the changes are not huge, I can probably do it. Alex, are the updates significant? Since 0.9.2 I'd say RC1 is a significant update. There are package name changes to comply with Directory's TLP domain name which are perhaps the most significant changes. There are changes to a couple dependencies. For the most part the code has been cleaned up and several *severe* bugs have been corrected and tested. RC1 is also an order of magnitude faster. We plan to get another 1.0 release candidate (RC2) out soon perhaps by the end of this week coming week or week there after. But looking at emails out there from Dain and Aaron it sounds to me like the update to G can take place any time after the 1.1 release. Let us know if you have any problems or need a hand while performing an upgrade either to RC1 or RC2 when it comes out. Regards, Alex -- Alexei Zakharov, Intel Middleware Product Division
Re: Directory Update (Jeff?)
Hi, I have created a patch to move the G directory module to ApacheDS 1.0 RC2. But I didn't find necessary 1.0 RCx jars at ibiblio neither at /maven nor at /maven2. The most recent version is 0.9.3. The same situation for MINA. So I can't post the patch right now since it will not work without these jars. Alex, I just want to let you know about this situation. 2006/4/24, Alex Karasulu [EMAIL PROTECTED]: Aaron Mulder wrote: I know 0.9.3 is there (in the /maven2 repo). Not sure about the RC's. Ya all including RC1 should be in the M2 repo if not let me know. Alex Thanks, Aaron On 4/24/06, Jeff Genender [EMAIL PROTECTED] wrote: Alex, Can you get the jars in ibiblio and I can get the integration going? I am only seeing 0.9.2 in ibiblio at the moment. Thanks, Jeff Alex Karasulu wrote: Jeff Genender wrote: If the changes are not huge, I can probably do it. Alex, are the updates significant? Since 0.9.2 I'd say RC1 is a significant update. There are package name changes to comply with Directory's TLP domain name which are perhaps the most significant changes. There are changes to a couple dependencies. For the most part the code has been cleaned up and several *severe* bugs have been corrected and tested. RC1 is also an order of magnitude faster. We plan to get another 1.0 release candidate (RC2) out soon perhaps by the end of this week coming week or week there after. But looking at emails out there from Dain and Aaron it sounds to me like the update to G can take place any time after the 1.1 release. Let us know if you have any problems or need a hand while performing an upgrade either to RC1 or RC2 when it comes out. Regards, Alex -- Alexei Zakharov, Intel Middleware Product Division
Re: Directory Update (Jeff?)
Hi, Just want to add that the version 0.9.2 is the reason of the org.apache.geronimo.directory.RunningTest hang on BEA Jrockit. I've been playing with different versions of ApacheDS and Jrockit for the last couple of weeks - you may see GERONIMO-1805 and DIRSERVER-607 for details of my activity. In case big guys are currently busy with fixing other important issues I'd like to volunteer for this. I simply can continue my efforts and try to handle the porting to ApacheDS 1.0 RCx. Thanks, 2006/4/24, Alex Karasulu [EMAIL PROTECTED]: Jeff Genender wrote: If the changes are not huge, I can probably do it. Alex, are the updates significant? Since 0.9.2 I'd say RC1 is a significant update. There are package name changes to comply with Directory's TLP domain name which are perhaps the most significant changes. There are changes to a couple dependencies. For the most part the code has been cleaned up and several *severe* bugs have been corrected and tested. RC1 is also an order of magnitude faster. We plan to get another 1.0 release candidate (RC2) out soon perhaps by the end of this week coming week or week there after. But looking at emails out there from Dain and Aaron it sounds to me like the update to G can take place any time after the 1.1 release. Let us know if you have any problems or need a hand while performing an upgrade either to RC1 or RC2 when it comes out. Regards, Alex -- Alexei Zakharov, Intel Middleware Product Division
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
[jira] Commented: (GERONIMO-1805) org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs
[ http://issues.apache.org/jira/browse/GERONIMO-1805?page=comments#action_12374056 ] Alexei Zakharov commented on GERONIMO-1805: --- I have tried thier recent stable build ApacheDS 1.0 RC1 (as well as previous stable builds). The bug is still reproducable but the stack trace is different. See http://issues.apache.org/jira/browse/DIRSERVER-607 org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs -- Key: GERONIMO-1805 URL: http://issues.apache.org/jira/browse/GERONIMO-1805 Project: Geronimo Type: Bug Security: public(Regular issues) Components: naming Versions: 1.0 Environment: 3Ghz Pentium 4 CPU, 2 GB RAM, Win XP professional SP 2 Reporter: Alexei Zakharov Attachments: MyDirectoryTest.java The unit test from directory module - org.apache.geronimo.directory.RunningTest - hangs while running on BEA JRockit VMs. I have localized the problem. It seems the problem is in built-in LDAP server from the apacheds-core package. See the attached test case. The code of this test case has been extracted from org.apache.geronimo.directory.RunnigTest and from org.apache.geronimo.directory.DirectoryGBean. You may need to set a correct classpath to be able to run this test. This bug may result in overall instability while running in BEA VMs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
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 and 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 ought 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:!-- Login Page -- but was:null 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 bea-1.5_geronimo-1.0.html -- Alexei Zakharov, Intel Middleware Product Division -- Alexei Zakharov, Intel Middleware Product Division -- Alexei Zakharov, Intel Middleware Product Division
[jira] Created: (GERONIMO-1805) org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs
org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs -- Key: GERONIMO-1805 URL: http://issues.apache.org/jira/browse/GERONIMO-1805 Project: Geronimo Type: Bug Security: public (Regular issues) Components: naming Versions: 1.0 Environment: 3Ghz Pentium 4 CPU, 2 GB RAM, Win XP professional SP 2 Reporter: Alexei Zakharov The unit test from directory module - org.apache.geronimo.directory.RunningTest - hangs while running on BEA JRockit VMs. I have localized the problem. It seems the problem is in built-in LDAP server from the apacheds-core package. See the attached test case. The code of this test case has been extracted from org.apache.geronimo.directory.RunnigTest and from org.apache.geronimo.directory.DirectoryGBean. You may need to set a correct classpath to be able to run this test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1805) org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs
[ http://issues.apache.org/jira/browse/GERONIMO-1805?page=all ] Alexei Zakharov updated GERONIMO-1805: -- Description: The unit test from directory module - org.apache.geronimo.directory.RunningTest - hangs while running on BEA JRockit VMs. I have localized the problem. It seems the problem is in built-in LDAP server from the apacheds-core package. See the attached test case. The code of this test case has been extracted from org.apache.geronimo.directory.RunnigTest and from org.apache.geronimo.directory.DirectoryGBean. You may need to set a correct classpath to be able to run this test. This bug may result in overall instability while running in BEA VMs. was:The unit test from directory module - org.apache.geronimo.directory.RunningTest - hangs while running on BEA JRockit VMs. I have localized the problem. It seems the problem is in built-in LDAP server from the apacheds-core package. See the attached test case. The code of this test case has been extracted from org.apache.geronimo.directory.RunnigTest and from org.apache.geronimo.directory.DirectoryGBean. You may need to set a correct classpath to be able to run this test. org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs -- Key: GERONIMO-1805 URL: http://issues.apache.org/jira/browse/GERONIMO-1805 Project: Geronimo Type: Bug Security: public(Regular issues) Components: naming Versions: 1.0 Environment: 3Ghz Pentium 4 CPU, 2 GB RAM, Win XP professional SP 2 Reporter: Alexei Zakharov The unit test from directory module - org.apache.geronimo.directory.RunningTest - hangs while running on BEA JRockit VMs. I have localized the problem. It seems the problem is in built-in LDAP server from the apacheds-core package. See the attached test case. The code of this test case has been extracted from org.apache.geronimo.directory.RunnigTest and from org.apache.geronimo.directory.DirectoryGBean. You may need to set a correct classpath to be able to run this test. This bug may result in overall instability while running in BEA VMs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1805) org.apache.geronimo.directory.RunningTest hangs on BEA Jrockit VMs
[ http://issues.apache.org/jira/browse/GERONIMO-1805?page=all ] Alexei Zakharov updated GERONIMO-1805: -- Attachment: MyDirectoryTest.java Below is the running statistics for this test on various JVMs. Running on Sun 1.4.2 and Sun 1.5.0 -- Starting LDAP Directory service LDAP Directory service started. in testMe() exiting testMe Test PASSED Sometimes the following exception is also visible: org.apache.ldap.common.NotImplementedException: N O T I M P L E M E N T E D Y E T ! don't know how to do this just yet at org.apache.ldap.server.protocol.AbandonHandler.messageReceived(Abando nHandler.java:44) at org.apache.mina.protocol.handler.DemuxingProtocolHandler.messageRecei ved(DemuxingProtocolHandler.java:70) at org.apache.mina.protocol.AbstractProtocolFilterChain$2.messageReceive d(AbstractProtocolFilterChain.java:149) at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageR eceived(AbstractProtocolFilterChain.java:365) at org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(Abst ractProtocolFilterChain.java:50) at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageR eceived(AbstractProtocolFilterChain.java:524) at org.apache.mina.protocol.AbstractProtocolFilterChain$1.messageReceive d(AbstractProtocolFilterChain.java:99) at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageR eceived(AbstractProtocolFilterChain.java:365) at org.apache.mina.protocol.AbstractProtocolFilterChain.messageReceived( AbstractProtocolFilterChain.java:356) at org.apache.mina.protocol.ProtocolSessionManagerFilterChain$1.messageR eceived(ProtocolSessionManagerFilterChain.java:77) at org.apache.mina.protocol.AbstractProtocolFilterChain.callNextMessageR eceived(AbstractProtocolFilterChain.java:365) at org.apache.mina.protocol.AbstractProtocolFilterChain.access$1000(Abst ractProtocolFilterChain.java:50) at org.apache.mina.protocol.AbstractProtocolFilterChain$Entry$1.messageR eceived(AbstractProtocolFilterChain.java:524) at org.apache.mina.protocol.filter.ProtocolThreadPoolFilter.processEvent (ProtocolThreadPoolFilter.java:96) at org.apache.mina.util.BaseThreadPool$Worker.processEvents(BaseThreadPo ol.java:341) at org.apache.mina.util.BaseThreadPool$Worker.run(BaseThreadPool.java:28 0) But the VM exits normally in any case. Running on BEA Jrockit 1.4.2 The test hangs with the following output: Starting LDAP Directory service LDAP Directory service started. in testMe() java.lang.IllegalArgumentException: cannot match with empty pattern at org.apache.commons.lang.Validate.isTrue(ZLjava.lang.String;)V(Validat e.java:191) at org.apache.asn1.ber.digester.TagTree.getNormalNode(Lorg.apache.common s.collections.primitives.IntStack;)Lorg.apache.asn1.ber.digester.TagNode;(TagTre e.java:448) at org.apache.asn1.ber.digester.TagTree.getNode(Lorg.apache.commons.coll ections.primitives.IntStack;)Lorg.apache.asn1.ber.digester.TagNode;(TagTree.java :405) at org.apache.asn1.ber.digester.TagTree.match(Lorg.apache.commons.collec tions.primitives.IntStack;)Ljava.util.List;(TagTree.java:392) at org.apache.asn1.ber.digester.RulesBase.match(Lorg.apache.commons.coll ections.primitives.IntStack;)Ljava.util.List;(RulesBase.java:105) at org.apache.asn1.ber.digester.BERDigester$DigesterCallback.decodeOccur red(Lorg.apache.asn1.codec.stateful.StatefulDecoder;Ljava.lang.Object;)V(BERDige ster.java:199) at org.apache.asn1.ber.BERDecoder.fireDecodeOccurred(Lorg.apache.asn1.be r.Tuple;)V(BERDecoder.java:399) at org.apache.asn1.ber.BERDecoder.decodeValue(Ljava.nio.ByteBuffer;)V(BE RDecoder.java:226) at org.apache.asn1.ber.BERDecoder.decode(Ljava.lang.Object;)V(BERDecoder .java:159) at org.apache.asn1.ber.digester.BERDigester.decode(Ljava.lang.Object;)V( BERDigester.java:145) at org.apache.ldap.common.berlib.asn1.SnickersDecoder.decode(Ljava.lang. Object;)V(SnickersDecoder.java:98) at org.apache.ldap.common.message.MessageDecoder.decode(Ljava.lang.Objec t;)V(MessageDecoder.java:141) at org.apache.asn1.codec.mina.Asn1CodecDecoder.decode(Lorg.apache.mina.p rotocol.ProtocolSession;Lorg.apache.mina.common.ByteBuffer;Lorg.apache.mina.prot ocol.ProtocolDecoderOutput;)V(Asn1CodecDecoder.java:41) at org.apache.mina.protocol.io.IoAdapter$SessionHandlerAdapter.dataRead( Lorg.apache.mina.io.IoSession;Lorg.apache.mina.common.ByteBuffer;)V(IoAdapter.ja va:136) at org.apache.mina.io.AbstractIoFilterChain$2.dataRead(Lorg.apache.mina. io.IoFilter$NextFilter;Lorg.apache.mina.io.IoSession;Lorg.apache.mina.common.Byt eBuffer;)V(AbstractIoFilterChain.java:150) at org.apache.mina.io.AbstractIoFilterChain.callNextDataRead(Lorg.apache .mina.io.AbstractIoFilterChain
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 and 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 ought 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:!-- Login Page -- but was:null 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 bea-1.5_geronimo-1.0.html -- 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 and 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 ought 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:!-- Login Page -- but was:null 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 bea-1.5_geronimo-1.0.html -- Alexei Zakharov, Intel Middleware Product Division -- Alexei Zakharov, Intel Middleware Product Division
javadoc issue
Hi, I am trying to build javadocs for Geronimo 1.0 code. In general it works fine except for several modules. For example, /modules/kernel contains two set of packages: org.apache.geronimo.kernel.* org.apache.geronimo.gbean.* But I was unable to build javadocs for the last one (org.apache.geronimo.gbean.*). Neither maven javadoc:generate from the /modules/kernel nor maven javadoc from the root src folder works. Javadoc is generated for org.apache.geronimo.kernel.* only. And I didn't find any mention of specific package names in nearby xmls. Did I do something wrong? Thanks! -- 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:!-- Login Page -- but was:null 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
