25 Jan, 2010

1 commit


22 Jan, 2010

4 commits


21 Jan, 2010

3 commits


20 Jan, 2010

8 commits


19 Jan, 2010

8 commits

  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6366 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Copied from the issue:
    
    Fix a bug where an NPE is occurring during ACI processing because the base entry contains a single RDN component which our one-level scope resolution does not handle very well (actually this is understandable - DN.getParent() has surprising behavior for single RDN DNs). This bug can be seen more clearly on trunk builds because the NPE stack trace is non-empty (IIRC there was a bug in older JVM versions where the NPE stack trace could be empty).
    
    Fix a bug where our exception handling code fails when an exception's stack trace is empty (in this case the NPE does not have any stack trace elements).
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6365 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • …0MBto 100MB): decrease default checkpoint frequency from 20MB to 100MB in order to reduce frequency of fsyncs. This should not increase recovery times significantly since modern hardware is capable of recovering 100MB of log very quickly.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6364 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6363 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • replication server it will connect to. This also introduces a new 
    (weighed) load balancing feature that spreads DS connections across the 
    RSs, according to the RS weights defined by the administrator,
    
    Issue 4343: https://opends.dev.java.net/issues/show_bug.cgi?id=4343
    
    The commit includes necessary modifications for implementing what is 
    described in this document:
    
    https://www.opends.org/wiki/page/ReplicationServerSelection
    
    There is a little "implementation" section in this document that 
    explains some important stuff.
    
    Also good to know for these code modifications:
    
    - The topology info related to RSs and kept by the ReplicationBroker is 
    now fully kept in a new map of a new ReplicationServerInfo bag class. 
    This map is updated upon reception of a TopologyMsg.
    - Protocol change: the TopologyMsg now includes the RS url in the RSInfo 
    list
    - The dynamic change of the weight of a RS triggers a new TopologyMsg 
    being fired, to support dynamic change of weights and automatic topology 
    re-connections
    - SameGroupIdPoller thread has disappeared and its functionality is 
    replaced by the mechanism that re-evaluates the more suitable RS (see 
    section 5, in the document for more details)
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6362 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mrossign
     
  • The password was systematically modified unnecessarily which lead to the misleading message.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6361 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6360 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6359 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     

18 Jan, 2010

5 commits

  • …y with large umount of data)
    - Add a 'Runtime Options' step in the wizard.  By default this will contain just two labels and two buttons:
    Server Runtime Options: Use Default <button to change>
    Import Options: Use Default <button to change>
    
    If the user clicks on one of these buttons, (s)he will be able to modify the runtime settings for the import and the server.
    
    There are also some messages trying to help the user.The idea is to find out if the user wanted to import a big LDIF file, a lot of automatically generated data or if the replicated base DNs contain lot of entries.  If it is the case and we consider that the default memory we allow to run the server (256 Mb) is not enough, the panel will display a message informing that it is recommended to increase the memory required.   For the moment the message is just a warning and has not a lot of information about a recommended memory size, but it improves the current behavior, were the import fails because of a lack of heap in the JVM.
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6358 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • If the server is running, launch the service after the service has been enabled.  The code of the service (native code in service.c) already handles the case where the server is running before the service code has been launched.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6357 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Improve the code of windows service to poll the status of the server (whether is running or not).
    Improve some of the messages associated with the events that are sent to the windows service log.
    Improve the code that is in charge of starting the service (and the server) to help identify cases where the server startup is correctly launched but the startup itself fails (because for instance a port of the server is already in use).
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6356 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@6355 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • …d of leaking ThreadLocal [ Sun Java Bug ID: 6254531 ] by replacing it with thread to asn1writer mapping.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@6354 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     

14 Jan, 2010

5 commits


13 Jan, 2010

6 commits