04 Dec, 2009

6 commits


03 Dec, 2009

7 commits


30 Nov, 2009

14 commits


27 Nov, 2009

3 commits


26 Nov, 2009

3 commits


25 Nov, 2009

5 commits

  • Handle the case where the user provides a certificate without an alias.  The code in CertificateManager has been updated to detect this situation.
    The code in ConfigureDS has also been updated to handle the case where the user does not provide a certificate nickname.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6198 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6195 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludovicp
     
  • Sometimes a message like this appears in the logs:
    
    "Monitor data of remote servers are missing due to an error in the 
    retrieval process. Potentially a server is too slow to provide its 
    monitoring data over the protocol"
    
    This seems to be introduced by the monitoring publisher thread which may 
    call the ReplicationServerDomain.completeMonitorData method at the same 
    time a MonitoringRequest message is being treated and is also in the 
    same method.
    
    These 2 threads are concurrently running the 
    ReplicationServerDomain.completeMonitorData method as one of the thread 
    wants to execute wrkMonitorData.completeComputing() which is outside of 
    the syncronized section, the other thread may reset wrkMonitorData to 
    null just before and this leads to a NPE. So another RS waiting for the 
    monitor response will never receive it and display the annoying message.
    
    The fix is to move the wrkMonitorData.completeComputing() call into the 
    synchronized section.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6194 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mrossign
     
  • …nd lastExternalChangelogCookie missing until first search
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6193 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • …ree searches without reading the response.
    
    Insert timeout based blocking write channel at bottom of LDAPClientConnection ByteChannel stack.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6192 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

24 Nov, 2009

2 commits