directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-607) Geronimo unit test hangs while running Apache DS on BEA VM
Date Wed, 19 Apr 2006 16:59:34 GMT
    [ ] 

Alexei Zakharov commented on DIRSERVER-607:


I have good news: I realize that I have mistakenly downloaded incorrect VM version last time
- jrockit-j2re1.4.2_08 is not the most recent one. The most recent is jrockit-R26.3.0-jdk1.4.2_10.
Below is the result for this VM:

1. MyApacheDSTest (ApacheDS 0.9.2) hangs with 16% probability (37:7) 
2. MyApacheDSTest (ApacheDS 0.9.3) works well 
3. MyApacheDS10Test (ApacheDS 1.0 RC1) works well (!)

So BEA guys have done all work for us :)
However, I still need a solution to fix (1) since Geronimo unit test still hangs with some
probability. Emmanuel, how big is the difference between ApacheDS 0.9.2 API and ADS 0.9.3
API, and between ADS 0.9.2 and ADS 1.0 RC 1? It can probably be some sense to made an intermediate
step and initially port Geronimo to 0.9.3 and then (when ADS 1.0 release is ready) finally
to ADS 1.0.
Can you recommend something?

> Geronimo unit test hangs while running Apache DS on BEA VM
> ----------------------------------------------------------
>          Key: DIRSERVER-607
>          URL:
>      Project: Directory ApacheDS
>         Type: Bug

>     Versions: 1.0-RC1, pre-1.0
>  Environment: CPU 3Ghz Pentium 4, 2 GB RAM, Win XP professional SP 2 
>     Reporter: Alexei Zakharov
>  Attachments:,, bea142.log, bea142_08.log,
> This bug is the result of the investigation performed on Geronimo unit test failure on
BEA VMs.  Geronimo uses Apache DS for its internal needs. And one of the unit tests on Geronimo's
"directory" module hangs on BEA VM due the strange behaviour of ApacheDS on BEA VMs. See the
attached testcases. To simplify things all Geronimo stuff was removed from the code.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message