org.forgerock / org.forgerock.opendj

30 Jul, 2009

3 commits

29 Jul, 2009

6 commits

  • fc05a196   Fix for issue 4156. ... Browse Code » 
    - 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 Code » 
    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 Code » 
    
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 Code » 
    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 Code » 
    
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 Code » 
    …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

4 commits

  • b930340d   Fix for issue 4148 (setup fails : The import LDIF tool returned error code 1) ... Browse Code » 
    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
     
  • 51491f2b   Today if a user makes a mistake in DynamicConstants and introduces a coding styl… ... Browse Code » 
    …e error, this error will not be spotted on the first run of the precommit target (but it will on the second and so on).

This fix guarantees that the checkstyle will be executed AFTER DynamicConstants is generated.  There is a change of behavior that I consider harmless but maybe I am missing something:  the clean of the build package is made before the checkstyle is executed.  This adds an extra second or so to spot errors on checkstyle, but it seems to me cleaner to do a clean and then do the checkstyle (to be sure that no error were introduced in the dynamically generated java files). 


git-svn-id: https://svn.forgerock.org/opendj/trunk@5609 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • ae1b0188   Fix tabs in DynamicConstants. ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@5607 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 66a2a263   Fix for issue 4150 (DynamicConstants class loading of ReleaseDefinition breaks Java Web Start). ... Browse Code » 
    The fix checks whether WebStart is being run.  If it is the case use a URLClassLoader to check whether ReleaseDefinition class is defined or not in quicksetup.jar.


git-svn-id: https://svn.forgerock.org/opendj/trunk@5606 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

23 Jul, 2009

3 commits

22 Jul, 2009

7 commits

21 Jul, 2009

1 commit

20 Jul, 2009

1 commit

17 Jul, 2009

2 commits

15 Jul, 2009

2 commits