org.forgerock / org.forgerock.opendj

17 Aug, 2009

1 commit

14 Aug, 2009

3 commits

13 Aug, 2009

3 commits

12 Aug, 2009

2 commits

  • ea4b5427   Remove the boolean member isClientBootstrapped. Originally it was used to only … ... Browse Dir » 
    …execute the code of the method bootstrapClient once, however this is not ideal for some client codes.  Some methods, such as initializeConfiguration, require the DirectoryServer object to be 'clean' (freshly bootstrapped), this can only be achieved by executing all the code of bootstrapClient.

The changes are actually just cosmetic, the logic in the code remains intact (simply the member isClientBootstrapped has been removed).


git-svn-id: https://svn.forgerock.org/opendj/trunk@5660 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 4b251523   Fix for issue 4172 (dsreplication: disable + enable causes SSL connection error) ... Browse Dir » 
    The code assumed that if the two registries were equal, then they were replicated.  This was wrong, if we disabled replication for one server, only the disabled server was unregistered from the ADS and this caused the problem (since the certificate of the previously unregistered server was not seeded).  The fix consists of two parts (even though just one of them would be enough to fix the issue, I think that having both will help the code to handle more scenarios):

1. Check that if the registries are equal, they actually are replicated (in terms of configuration of the replication).
2. Unregister ALL the servers from the ADS of the server where replication is being disabled if we have to unregister the server itself.  


git-svn-id: https://svn.forgerock.org/opendj/trunk@5654 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

11 Aug, 2009

3 commits

10 Aug, 2009

1 commit

07 Aug, 2009

1 commit

  • 09b22969   Fix for 4165 : Replica can be slow to replay changes when using large window size ... Browse Dir » 
    When checking dependencies during replay of operations on the consumer
the replication go through the list of pending changes while holding the
pending changes lock.
When using large values for the window size, the list can be large
and this can therefore cause large replication delay on the replica. 

The solution is to limit the parsing to the list of changes that are older than the current change. 

git-svn-id: https://svn.forgerock.org/opendj/trunk@5636 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

06 Aug, 2009

1 commit

05 Aug, 2009

1 commit

  • 06e479d2   fix for ... Browse Dir » 
    4161 some mistranslations in german
and
4162 french: exception in setup


git-svn-id: https://svn.forgerock.org/opendj/trunk@5631 41b1ffd8-f28e-4786-ab96-9950f0a78031
    hajma
     

04 Aug, 2009

1 commit

31 Jul, 2009

2 commits

30 Jul, 2009

3 commits

29 Jul, 2009

6 commits

  • fc05a196   Fix for issue 4156. ... Browse Dir » 
    - Disconnect notifications are no longer sent when IO errors or client disconnects are encountered. 
- TLSByteChannel now  throws SSLException if SSLEngine.wrap did not produce any bytes.

git-svn-id: https://svn.forgerock.org/opendj/trunk@5617 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 3f87e9c7   Fix for issue 4155 (UI keystore does not handle properly certificates from the same host) ... Browse Dir » 
    If the provided certificate to be accepted in the key store is not already there, use a unique alias for the certificate.


git-svn-id: https://svn.forgerock.org/opendj/trunk@5616 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • ab853a3f   Fix typo. ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@5615 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 8c8d2b99   Fix for issue 4151 (Default java heap not enough to launch import) ... Browse Dir » 
    The idea is to improve what we currently have, which is relying on java ergonomics and only setting the '-client' and '-server' arguments as default java arguments.  As far as I can see with the new import code, the java ergonomics (this has been reproduced in Solaris and Mac OS X) are not enough to guarantee that the server will be able to make a small import (around 2000 entries) out of the box.

The proposed fix tries to set the following arguments to the server command-lines (start-ds and import-ldif in particular):

-Xms128m -Xmx256m

These arguments will be set if and only if:

They can be used while the setup is being run (and so the JVM supports them and the system where we are running is able to launch a JVM using them).

The ergonomics of the JVM where the setup is being run does not allocate a maximum heap that is higher than those values.  With this check we guarantee that we are not going to allocate less memory than what the JVM already does by default. 


git-svn-id: https://svn.forgerock.org/opendj/trunk@5614 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 408bf0ac   Revert to previous version (committed inadvertently). ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@5612 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • c3902e4c   Fix for issue 4152 (Graphical utilities should be consistent with command-line (… ... Browse Dir » 
    …admin connector certificate)
Load the admin-truststore when creating the keystore to be used by the graphical utilities.


git-svn-id: https://svn.forgerock.org/opendj/trunk@5611 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

28 Jul, 2009

1 commit

  • b930340d   Fix for issue 4148 (setup fails : The import LDIF tool returned error code 1) ... Browse Dir » 
    Since the import-ldif utility does not support any more (temporarily) the append option the setup (and the control-panel) were broken.

Temporarily the following modifications have been made in the control panel:
If the user decides to create data in the new base DN and there was already data in the backend, a confirmation dialog will be displayed informing that all the data will be overwritten.
The appending options in the Import LDIF panel have been hidden.

Concerning the setup, the modifications made are permanent.  What basically has been done is:
Use a single template LDIF file when the user decides to import automatically generated data.  Before this, one file per base DN was generated, which required the option 'append' to be used.  With a single file, no append is required.  This is a clearer solution, since I think that appending data affects to performance.
I have found some memory issues with the default ergonomics of the new import (see issue 4151).  Since some ergonomics issues may occur, the import is now launched in a separate process.  If we manage to improve the code that determines the default java arguments to be used for the import, this will help avoiding problems with the import.


git-svn-id: https://svn.forgerock.org/opendj/trunk@5610 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

27 Jul, 2009

5 commits

26 Jul, 2009

2 commits

25 Jul, 2009

1 commit

24 Jul, 2009

3 commits