08 Jun, 2009

1 commit


05 Jun, 2009

3 commits


04 Jun, 2009

1 commit


03 Jun, 2009

1 commit

  • When replication is configured and when the connection between the Directory Server
    and the Replication Server fails the Directory Server is reconnecting to a Replication Server.
    However currently the error 53 (DSA is unwilling to perform) is returned to application
    during the time of the reconnection.
    This is wrong because at this time the DS is not on error.
    
    With this change the update threads now waits for the new connection to
    be established (which is fast) before being processed. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5408 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

28 May, 2009

1 commit

  • When the replication heart-beat fails, the replication disconnects from the
    replication server and reconnect to another one.
    
    In such case the error messages are too verbose and may lead to false conclusion.
    This change reduce the error messages logged in those case. 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5397 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

27 May, 2009

1 commit


26 May, 2009

1 commit


25 May, 2009

3 commits


21 May, 2009

1 commit


19 May, 2009

2 commits


18 May, 2009

2 commits


15 May, 2009

1 commit


14 May, 2009

1 commit


13 May, 2009

1 commit

  • Partial Fix for issue #3938 : dsconfig is really too slow in non-interactive mode, almost unusable on Niagara systems
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5353 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jcambon
     

12 May, 2009

6 commits


11 May, 2009

2 commits


07 May, 2009

3 commits


06 May, 2009

8 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5324 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • The fix will improve the user experience in Windows when installing from a ZIP file.  When the JVM is installed, the java.exe is contained in the PATH environment variable.  The fix consists on trying to see if java.exe is on the PATH by calling java.exe -version if no OPENDS_JAVA_HOME nor JAVA_HOME environment variables are defined..
    
    Note that even though this is an expensive operation in term of resources, this will only be called when the setup is launched for the first time.  The setup will update the environment of execution of OpenDS and this call will no longer be made.  The exception to this is the case where the user removes all the environment by deleting the files generated by the setup (or dsjavaproperties), this is done usually when the java environment has changed and the user has been told to do so (and also told to call dsjavaproperties).  Once dsjavaproperties is called again (the normal procedure to configure the execution environment) this 'extra' call to java.exe will not be made in the scripts.
    
    In other words, the fix will only have a performance penalty when the user calls 'setup' for the first time (and no OPENDS_JAVA_HOME or JAVA_HOME env variables are defined) and when the user resets the execution environment (and so is supposed to call dsjavaproperties).  This small penalty (some extra tenths of a second) is acceptable because with the fix in most of the cases the user will not have to set OPENDS_JAVA_HOME (dealing with environment variables is a rare procedure for Windows users).  As a result of this the user experience will be much smoother than what is today.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5323 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Update JE to version 3.3.81.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5322 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • * avoid creating ClientConnectionMonitorProviders for each new connection
    
    * separate construction of ClientConnectionMonitorProviders and LDAPStatistics
    
    * push registration of ClientConnectionMonitorProviders and LDAPStatistics in LDAPConnectionHandler initialization
    
    * ensure that ClientConnectionMonitorProviders and LDAPStatistics are deregistered when the LDAPConnectionHandler is finalized.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5321 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@5320 41b1ffd8-f28e-4786-ab96-9950f0a78031
    sin
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5319 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Instead of doing a direct String comparison, split the hostname and check for wildcards.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5318 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • are dependent on timing and block forever if they fail which can cause the daily build
    to hang forever randomly.
    
    This change attempt to fix the problem by :
    - don't depend on timeout in the test
    - don't wait forever if the test does not finish 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@5317 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

05 May, 2009

1 commit