18 Dec, 2007

2 commits


17 Dec, 2007

17 commits

  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3578 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • …les.  The bug prevented the Java WebStart installer to create set-java-home.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3577 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3576 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3575 41b1ffd8-f28e-4786-ab96-9950f0a78031
    dugan
     
  • We check now if it's an absolute path.
    If it's a relative path, we add the instance root path to get the actual file location
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3574 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • Update the indentation as proposed in the issue description.
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3573 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • Note: this issue is not fully covered by the proposed modifications but
    all that is missing in order to fix it is to figure out which are the
    default memory values that we want to propose in the setup.
    
    2620: Server should be started as server JRE and clients should be
    started as client JREs
    
    The proposed solution goes beyond fixing the two issues and proposes a
    manner for the user to set specific java arguments (and use a specific
    JVM) for every command-line.
    
    Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME
    environment variable and the java arguments by using the
    OPENDS_JAVA_ARGS environment variable.  In the case of the JVM this
    covers most of the use cases (in general we will use the same JVM for
    all the command-lines).  However this is quite limiting in the case of
    the java arguments we pass.  For instance in general we want to run the
    server (start-ds command-line) using the server mode of the JVM but
    other command-lines using the -client mode of the JVM.  In the same
    manner we might want to have a bigger heap when running the server than
    when we are running a "lightweight" utility as dsconfig.
    
    The proposed solution is to have a properties file called
    java.properties where the user specifies the different JVM and java
    arguments to be used for every command-line.  Once the user has edited
    this properties file, (s)he must run a command-line called
    dsjavaproperties that will update all the scripts to use the arguments
    specified in that properties file.
    
    NOTE: there are a number of command-lines (import-ldif, export-ldif,
    backup, restore) where the user will be able to specify different java
    arguments (and different JVM) to use depending on whether the
    command-line is run in online or offline modes.  You can see the
    comments on java.properties to get more information about this and in
    general about the different properties that can be set.
    
    The modification in the setup basically try to check if the JVM that is
    being used to run the setup (the one that will be used by default)
    supports the -client and -server options.  Depending on the results of
    these checks the setup will update the java.properties file and then run
    dsjavaproperties to update the scripts. 
    
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3572 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3571 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3570 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3569 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3568 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3567 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3566 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3565 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3564 41b1ffd8-f28e-4786-ab96-9950f0a78031
    andrug
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3563 41b1ffd8-f28e-4786-ab96-9950f0a78031
    schwing
     
  • git-svn-id: https://svn.forgerock.org/opendj/trunk@3562 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

14 Dec, 2007

5 commits


13 Dec, 2007

8 commits


12 Dec, 2007

2 commits


11 Dec, 2007

4 commits


10 Dec, 2007

2 commits

  • If the Replication Server is stopped while the ServerHandler writer threads are blocked waiting for some window credit they are blocked and don't stop
    immediately.
    
    This issue is minimal for real life but can cause unit test failure because replication Servers are stopped and started a number of times during the tests.
    
    This commit also enabled some more replication tests and change them to make the
    order in which they are run more predictible.
    
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3542 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3541 41b1ffd8-f28e-4786-ab96-9950f0a78031
    smaguin