31 Aug, 2007

2 commits


30 Aug, 2007

6 commits


29 Aug, 2007

10 commits


28 Aug, 2007

4 commits

  • Instead of closing the environment, deleting the files, and re-opening the
    environment, we are keeping the environment open and just truncating the
    databases.  This dramatically reduces the amount of memory required to run the
    unit tests, apparently as a result of a memory leak in the Berkeley DB JE when
    the environment is repeatedly opened and closed.
    
    Note that the latest release of Berkeley DB JE (3.2.44, which we aren't yet
    using) claims to have a fix for a similar problem (JE issue #15444 as described
    in http://forums.oracle.com/forums/thread.jspa?messageID=1782659) but testing
    with that JE version didn't appear to resolve the problem so it is likely that
    the issue still exists.  However, while it was causing a significant problem in
    our test cases, it is unlikely to cause problems in production environments
    because the JE environment should not be repeatedly opened and closed in the
    same JVM instance.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2834 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …ng TestNG on some machines.
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2833 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • There is a new backend representing the certificate trust store, which allows the setup code to query and populate the trust store over protocol. However, we are using blind trust until that piece of the setup code is ready.
    
    The encryption settings are currently global to the server instance in a new crypto manager config entry. Authentication will always be performed so the main setting is whether to use encryption or not. In the future (post 1.0) we will need to allow encryption to be configured on or off depending on which replication server we are connecting to but we need some discussion on the best way to specify that in configuration.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2829 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2825 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

27 Aug, 2007

7 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2823 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • 2 - fix in runTestJob: removed copy of results.html in tmp folder
    3 - fix in staf-installer.xml removed references to results.html
        only rely on my-report.html now
    4 - attach my-report.html to the in place of results.html
    5 - added knowIssue facility to allow to tag tests failing because of known issues
    6 - updated the XSL style sheet to show known issue
    7 - added testcase coloring based on status pass/fail/unknown/known
    8 - added table of contents title row to make it easier for newcomers to read the
        report
    9 - added known bugs calls in backends group
    10- added known bugs calls in security group
    11- added known bugs call in logging group
    12- fix in utils for default windows environment variables
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2822 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • Also, modified the dsconfigSet function so that two of its existing parameters are now optional instead of required. This was necessary for such cases as set-global-configuration-prop where no object may be specified.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2821 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mkeyes
     
  • - Implemented as virtual attributes
       - They are enabled by default
       - numSubordinates and hasSubordinates methods added to the backend API and implemented for all existing backends
       - JE implementation uses the id2children index to keep count of the number of subordinates for each entry.
       - The behavior of exceeding the index-entry-limit (ALL-IDs) has changed to store a 8 byte entry ID set count with the most significant bit 
    set to 1 instead of a 0 byte array to signify the index-entry-limit has been exceeded. The previous format is still compatible but all requests 
    for numSubordinates will return undefined (-1).
       - The DBTest tool is also included in this fix. This can be used to list root containers, entry containers, database containers, index 
    status, as well as dumping a database with or without decoding the data. 
    
    Fix for issues 43 and 72
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2820 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2816 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@2812 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     
  • When debugging 2097 I've noticed that during a replication total update,
    if the updated server fails, the publisher thread on the other server hangs.
    
    The hang happens because normally the publisher thread never tries to reconnect
    after a protocol session failure but waits for the receiver threads to do the job but
    here the publishing activity is done in a receiver thread that holding the session lock
    and therefore prevent the other thread from doing there job.
    
    The solution is to move this work outside of the lock.
    
    I've tested this manually as it is difficult to automate.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2811 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

26 Aug, 2007

5 commits


25 Aug, 2007

4 commits


24 Aug, 2007

2 commits