org.forgerock / org.forgerock.opendj

27 Nov, 2009

3 commits

26 Nov, 2009

3 commits

25 Nov, 2009

5 commits

  • cac963a2   Fix for issue 4371 (setup throws NullPointerException when trying to use a PKCS12 certificate) ... Browse Code » 
    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
     
  • 408e98ea   Promotion of OpenDS 2.2.0 Release Candidate 4 ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6195 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ludovicp
     
  • 98b2dbba   This is related to modifications done for RFE 4343. ... Browse Code » 
    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
     
  • bb958ae0   Fix P3/#4340 ECL (draft mode): on second RS, first and last ChangeNumber are 0 a… ... Browse Code » 
    …nd lastExternalChangelogCookie missing until first search

git-svn-id: https://svn.forgerock.org/opendj/trunk@6193 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • 03653715   Fix issue 4360 - OpenDS does not answer anymore when doing 24+ simultaneous subt… ... Browse Code » 
    …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

4 commits

23 Nov, 2009

2 commits

20 Nov, 2009

6 commits

19 Nov, 2009

3 commits

18 Nov, 2009

7 commits

  • ccbb2e6a   Fix for issue 4295 (Issues with dsreplication interactive mode) ... Browse Code » 
    The following changes complete the previous fix done for this bug, if we were using dsreplication enable on the installation of one of the servers, the interactive mode failed if the option --trustAll was NOT specified. 


git-svn-id: https://svn.forgerock.org/opendj/trunk@6163 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 6af6827b   Fix for issue 4189 (dsconfig : --commandFilePath mis-behaviour when correcting e… ... Browse Code » 
    …rrors in interactiv mode)

The PropertyValueEditor object was not kept if there was an error, this created some inaccurate equivalent commands to be displayed when the user made a mistake creating or modifying configuration objects.


git-svn-id: https://svn.forgerock.org/opendj/trunk@6162 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 45405c53   Fix for Issue 4300 : stop replication server cause OutOfMemoryError ... Browse Code » 
    This problem happens in the following conditions :
- use Directory Servers that do not have Replication Servers in the same JVM
- use only 2 Replication Servers
- apply a heavy load of updates on one Directory Server
- stop the first Replication Server
- wait some time long enough to perform millions of change
- Restart the First Replication Server that will therefore have millions of
 change to retrieve from the second
- quickly stop the second Replication Server (before it has time to replicate
 the missing changes to the first RS)

In such case, The DS will connect to the first RS, see that it missing lots of change and will attempt to re-generate them from the historical information
in the database. Unfortunately this process needs to fetch all the changes
in memory because it needs to send them to the RS in the order of the
ChangeNumbers and therefore currently sort them in memory before sending them.

This change fixes the problem by searching for changes by interval. This avoid the memory
problem because in this case, there is only the need to sort a limited number of changes and
this can fit in memory.

However this fix is not enough because this whole process is done in the replication Listener thread and this thread is also responsible for managing the replication protocol window.
Unfortunately while this thread is busy sending a lot of changes to the RS it is not able to also do the job of managing the window and this can therefore fall into a deadlock.

So a second level of changes is necessary to move the code in a separated new thread that is
created only when necessary.

This lead to the last problem that I met : the creation of this new thread caused some concurrency
problems that I had to fix by introducing some synchronization code between this new thread, the listener thread and the worker thread. 

git-svn-id: https://svn.forgerock.org/opendj/trunk@6161 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • a439d05c   Fix#4329 ECL - draft mode: after adding new suffix, can not search ECL because of invalid cookie ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6159 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • f9785fdf   Fix for issue 3256 (Add certificate settings options in setup CLI) ... Browse Code » 
    When the user chooses to generate a self-signed certificate in the command-line setup, prompt to provide the host name that will be used to generate the certificate.


git-svn-id: https://svn.forgerock.org/opendj/trunk@6158 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • d448bd47   Correct a typo that made the JCEKS trust manager created in the setup to have two cn values. ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@6157 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 68b49d83   Fix for #4358 ECL Some ECL error can prevent the server to stop properly by db cursor retention ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6155 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     

17 Nov, 2009

1 commit

16 Nov, 2009

1 commit

11 Nov, 2009

3 commits

10 Nov, 2009

2 commits