23 Feb, 2007

13 commits

  • OpenDS Issue Number:  1277
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1249 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …s) did not check for null OperationStatus objects being passed in and caused an NullPointerException whenever EntryCount was called. Added a null check.
    
    Changed ID2Entry#getRecordCount to use the Database#count method in JE 3.1.0. The JE backend no longer keeps a count of entries in entry ID 0. Modified TestVerifyJob unit test to no longer simulate a incorrect entry count.
    
    It was a clear case that using Database#count is much faster then keeping a count at entryID 0. At the least, it can eliminate a database read and write on every entry add and delete operation. In addition, calling Database#count is faster then getting an entry out of the database as the following shows.
    
    Time took to get entry count 100 times (w/o transactions):
    
    Duration using Database#count: 16731000 ns
    Duration using old entry counter: 22094000 ns
    
    Duration using Database#count: 17124000 ns
    Duration using old entry counter: 39434000 ns
    
    Duration using Database#count: 15522000 ns
    Duration using old entry counter: 20069000 ns
    
    Duration using Database#count: 15873000 ns
    Duration using old entry counter: 19732000 ns
    
    Duration using Database#count: 15871000 ns
    Duration using old entry counter: 20594000 ns
    
    Duration using Database#count: 21099000 ns
    Duration using old entry counter: 21877000 ns
    
    Fix for issue 740
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1247 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • …r enabled.  The testDigestMD5 test in LDAPCompareTestCase was not actually binding using DigestMD5 because the SASL mechanism name was omitted from the arguments.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1246 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • introduced a large number of test failures.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1245 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • … default.  Most of the failing tests are fixed by adding bypass-acl privilege to the entries of the users the failing tests bind as.
    
    This change also includes an important fix to the server for operations carrying the proxied auth control.  The ACI check in the core operation is moved after the controls processing to ensure that the correct authorization user is picked up, and the ACI handler now gets the authorization user from the operation rather than the connection.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1244 41b1ffd8-f28e-4786-ab96-9950f0a78031
    coulbeck
     
  • least one value.  This will prevent add requests from being able to add entries
    containing attributes with no values.
    
    OpenDS Issue Number:  1275
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1241 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • about whether a given SSL certificate should be trusted.  This will be used for
    all of our client tools in the case when no trust store is available and the
    user has not requested the "--trustAll" option.
    
    OpenDS Issue Number:  1274
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1240 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@1239 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • we don't need in the core server but can help other applications interoperate
    with OpenDS.
    
    Also, add a class org.opends.server.interop.LazyDN which is a
    lazily-initialized version of the org.opends.server.types.DN class.  This makes
    it possible to have very fast DN processing when you need to create a DN from
    a String and the only thing that will be called on that DN is the toString()
    method.  This commit includes test cases to ensure that the public methods of
    the DN and LazyDN classes stay in sync.
    
    OpenDS Issue Number:  1276
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1238 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …e JE backend no longer keeps a count of entries in entry ID 0. Modified TestVerifyJob unit test to no longer simulate a incorrect entry count.
    
    Fix for issue 740
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1237 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • "%*" Does not work properly when we have arguments with quotes.  Use a FOR statement to determine whether the user provided arguments or not to the stop-ds.bat command. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1233 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1232 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     
  • are intended only for internal use.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1230 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

22 Feb, 2007

10 commits

  • notification whenever the access control handler is enabled or disabled.
    
    OpenDS Issue Number:  1269
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1229 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • the dseecompat implementation by default.  It will still remain disabled by
    default.
    
    OpenDS Issue Number:  1270
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1228 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1227 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • we want to stop the local server an we use the pid to kill it.  If other
    arguments are passed (which appart from --help are arguments related to LDAP
    authentication) I will assume that we are trying to stop the server using
    protocol.
    
    This fixes issue 1261.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1225 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • properly handle the case where the server is already running.
    
    OpenDS Issue Number:  1251
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1221 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • the PID file is only written if the server is not already running.  If it's not
    being used to try to start the server, then just invoke the command without a
    PID file.  If it is trying to start the server but the server is already
    running, then exit with an error.
    
    OpenDS Issue Number:  1251
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1220 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1219 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • …if LDAP port' and 'cannot stop server through status panel').
    
    The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.
    
    In order to do this I have written some native code.  This native code is called when we start the server to:
    1. Launch the java process and get the associated PID.
    2. Create a server.pid file as we do for UNIX systems to store the PID of the process.
    
    The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.
    
    In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.
    
    I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.
    
    The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.
    
    I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.
    
    A README file has been also been included to explain how to generate the binaries.
    
    Extras:
    When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.
    
    When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.
    
    When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1218 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …if LDAP port' and 'cannot stop server through status panel').
    
    The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.
    
    In order to do this I have written some native code.  This native code is called when we start the server to:
    1. Launch the java process and get the associated PID.
    2. Create a server.pid file as we do for UNIX systems to store the PID of the process.
    
    The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.
    
    In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.
    
    I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.
    
    The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.
    
    I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.
    
    A README file has been also been included to explain how to generate the binaries.
    
    Extras:
    When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.
    
    When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.
    
    When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1217 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • …if LDAP port' and 'cannot stop server through status panel').
    
    The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.
    
    In order to do this I have written some native code.  This native code is called when we start the server to:
    1. Launch the java process and get the associated PID.
    2. Create a server.pid file as we do for UNIX systems to store the PID of the process.
    
    The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.
    
    In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.
    
    I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.
    
    The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.
    
    I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.
    
    A README file has been also been included to explain how to generate the binaries.
    
    Extras:
    When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.
    
    When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.
    
    When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1216 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

21 Feb, 2007

6 commits


20 Feb, 2007

3 commits


19 Feb, 2007

2 commits

  • When it is enabled, the synchronization code can sometimes decide to abandon
    an add operation. In such case the handleConflictResolution() method
    of the SynchronizationProvider will return a code indicating to stop the
    OperationProcessing.
    However when doing this, the ChangeListener are still invoked
    at the end of the AddOperation processing.
    Since the operation has not been processed, the ChangeListeners are given
    a null entry parameter but the StaticGroup code that runs as a ChangeListener
    makes the assumptions that the entry is always non null at this point.
    This currently causes the following assert when running the test
    synchronization.UpdateOperationTest.namingConflicts()
    
    The change notification listeners will only be invoked if the result
    code for the operation is "SUCCESS", and at that point in the processing
    it should only be SUCCESS if the update was actually applied.  If the
    synchronization code decided to abort the operation the
    the provider.handleConflictResolution() therefore now set
    a Cancel Result code.
    
    
    
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1201 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@1200 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     

18 Feb, 2007

6 commits