20 Nov, 2008

2 commits


19 Nov, 2008

7 commits


18 Nov, 2008

7 commits


17 Nov, 2008

8 commits


16 Nov, 2008

1 commit


13 Nov, 2008

4 commits

  • In certain scenarios (e.g. distribution) a single client side persistent search may result in multiple back-end persistent searches being launched. The current server design only supported a one to one relationship. This change removes the restriction:
    
       * persistent search is no longer stored in the search operation
    
       * client connection operation cancellation now supports having
         multiple PersistentSearch objects per client search
    
       * PersistentSearch operation cancellation now cancels all related
         PersistentSearches
    
       * PersistentSearch instances must be enabled before use: doing this
         registers the persistent search with the client connection and
         prevents the underlying search operation from having a result sent.
    
    I have also updated the class' javadoc to include more complete usage information.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4616 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4611 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • …an be downloaded from opends.org. Location of the zip file: <ws>/build/package/svr4/opends.zip
    This also fixes an issue related to bad svn revision number in the SVR4 package.
    
    
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4608 41b1ffd8-f28e-4786-ab96-9950f0a78031
    chebrard
     
  • …r the allowed-client and deny-client properties
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4607 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lfrost
     

12 Nov, 2008

5 commits


11 Nov, 2008

3 commits


10 Nov, 2008

2 commits

  •    * Persistent searches are now registered in the following two places:
    
             o the client connection associated with the search (i.e. as
               before)
    
             o per-WFE lists: it is now the responsibility of the WFE to
               maintain this list.
    
       * The PersistentSearch API has changed:
    
             o it no longer depends on Operations for update notifications.
               This means that the notifications can be sent from "out of
               band" event sources, such as remote persistent searches
               issued from a proxy WFE
    
             o it now supports a cancel() method which should *always* be
               used to cancel a persistent search. This method takes care
               of all resource cleanup: deregistering from the client
               connection and any WFE related resources
    
             o in now provides a mechanism for registering callbacks which
               should be invoked when the psearch is cancelled. This should
               be used by WFE implementations that need to keep track of
               the psearches that they are handling. 
               
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4595 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4594 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jcambon
     

07 Nov, 2008

1 commit

  • …ing it configurable).
    
    The fix increases the number of tries used to figure out if the server is started or not.  This is required in particular after reboot since the system can be really loaded.
    
    The user can modify the default tries value (100 tries with an interval of 5 seconds between tries) by setting the value of the OPENDS_WINDOWS_SERVICE_START_NTRIES  environment variable (it must be a SYSTEM environment variable in order to be taken into account).
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@4592 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara