org.forgerock / org.forgerock.opendj

11 Jan, 2008

1 commit

08 Jan, 2008

1 commit

07 Jan, 2008

4 commits

04 Jan, 2008

3 commits

03 Jan, 2008

2 commits

  • b2e7b0cf   Fixed the config change listeners for all log publishers so they will prevent ch… ... Browse Dir » 
    …anging the log file permissions to an invalid value. The listeners will now reject changes that will prevent OpenDS from writing to the log files.

Fix for issue 2107


git-svn-id: https://svn.forgerock.org/opendj/trunk@3619 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • d768d5f4   Issue 2345: global replication monitoring ... Browse Dir » 
    https://opends.dev.java.net/issues/show_bug.cgi?id=2345

Feature description:

** Before these changes, the monitoring information for the replication contain the information for the replication server itself, and for the LDAP server that are currently connected to it, not for the 
LDAP servers connected to other RS.
** With these changes, each RS exposes the delay informations for all RSes in the topology. In addition the delay for each server is consolidated across the whole topology.

see details in
https://www.opends.org/wiki//page/MonitoringReplication

Note:
- This feature is loosely tested by unit tests. We should probably add more tests in the future but I think it is a good idea to commit the feature and basic tests right now.
- The UI part of this feature still need some adaptations to the changes done in the server.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3614 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     

22 Dec, 2007

1 commit

21 Dec, 2007

2 commits

  • 834f82fb   Fix for 1862 verbosity options for quicksetup tools ... Browse Dir » 
    The fixes are just cosmetic.  They consist basically of:

* Add verbosity options for the uninstall and upgrade utilities and make them behave as the verbosity options of the setup.

* Make the output of the upgrader consistent with the output of setup and uninstall.

* Update the non verbose output of the import LDIF and the import automatically generated data so that a point is displayed every 3 seconds during the import is ongoing.  This way the user will not have the impression that the setup is blocked and we show that some work is going on.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3607 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • c0dcfb1a   [2773] add operation into a non existing naming context returns wrong error code ... Browse Dir » 
    - Fix return code for add operation on a non existing backend (32 instead of -1 currently)


git-svn-id: https://svn.forgerock.org/opendj/trunk@3600 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mmarie
     

20 Dec, 2007

1 commit

18 Dec, 2007

2 commits

  • 51eb2a98   Fix for #2570: Received fatal alert: certificate_unknown ... Browse Dir » 
    We now log (notice, instead of error) a more explicit message that tells an SSL connection attempt failed (from node xxx) to the replication server.

git-svn-id: https://svn.forgerock.org/opendj/trunk@3584 41b1ffd8-f28e-4786-ab96-9950f0a78031
    mrossign
     
  • ab19a003   Fix for issue 1862 (verbosity options for quicksetup tools) ... Browse Dir » 
    The fix consists on adding a verbose option to the setup command-line.

With these modifications the graphical setup and the CLI setup (by default) run in non-verbose mode.  The logs for import and start are not displayed, nor we make any reference to the ADS when configuring replication.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3582 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

17 Dec, 2007

1 commit

  • b5ad1173   2730: New - The setup command should perform some basic memory tuning ... Browse Dir » 
    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
     

14 Dec, 2007

2 commits

13 Dec, 2007

1 commit

  • 64a93f9f   Fix for issue 1730. ... Browse Dir » 
    In the error messages quote the values that are causing problems to help the user identify proble
ms with trailing spaces.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3556 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

07 Dec, 2007

1 commit

  • 8cfaab0f   This relates to issue 2661 "public APIs must not reference private classes". ... Browse Dir » 
    The classes in org.opends.messages need to be made public so that they can be referenced from other public APIs. This change adds the PublicAPI annotation to the classes defined in this package as follows:

   * the org.opends.messages package is VOLATILE

   * the org.opends.messages core classes (Message, MessageDescriptor,
     MessageBuilder, Category, and Severity) are all UNCOMMITTED

   * the class org.opends.messages.MessageDescriptorRegistry is PRIVATE
     (it's only used in unit tests)

   * generated message classes are PRIVATE

In addition minor cleanup was made to the classes where appropriate to make them suitable for public APIs:

   * used "final" where possible

   * reduced visibility of classes, methods, and members where appropriate

   * fixed some potential bugs spotted during this clean-up: class
     members not being initialized (the "final" keyword is useful for
     spotting this!)

   * added missing javadoc
   
   * I've removed the third-party and user-defined message generation
     since we could see know way in which they could be easily used
     without impacting core OpenDS source


git-svn-id: https://svn.forgerock.org/opendj/trunk@3536 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

02 Dec, 2007

1 commit

27 Nov, 2007

1 commit

26 Nov, 2007

2 commits

  • 98bd2647   Fix for issue 2010. ... Browse Dir » 
    The fix consists in including a little bit more on context to the error message.

For command-line dsconfig list-local-db-indexes --backend-name tasks -n -p 1389 -w s

The output was:

"Task Backend" is not a recognized component type

With the fix the output is:

"Task Backend" component type cannot be used with subcommand
{list-local-db-indexes} 


git-svn-id: https://svn.forgerock.org/opendj/trunk@3497 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 1a5488a0   ... Browse Dir » 
    Fix for Issue #1961 (reviewed by Josu)
 * Remove instances of "Specifies the..."
 * Remove instances of "Indicates that..."
 * Reword instances of "Specifies to..." (which doesn't really make
   sense anyway)
 * Change instances of "This utility may be used..." to "This utility
   can be used..." as discussed in a previous issue
 * Change some erroneous instances of "may" to "might" or "can". This
   might sound like a pointless change but it has implications for
   localization - "may" is generally ambiguous. 


git-svn-id: https://svn.forgerock.org/opendj/trunk@3496 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lfrost
     

22 Nov, 2007

1 commit

  • ef8e09d0   Fix for issue 2613 ... Browse Dir » 
    The upgrader is breaking replication (and not just dsreplication).

The problem occurs because the upgrader is systematically overwriting the contents of the admin-backend.ldif file when it should not.  The fix consists on not updating this file unless it does not exist.

The same fix has been applied to tool.properties since it was also systematically overwritten (and so the user lost the changes made to it).

Appart some fixes related to message formatting are also included in the attached diff file.  The code used to display messages with HTML formatting in CLI mode, so specific messages have been added when the upgrade is run from the command line.

Finally the code of the upgrader has been updated to use the MenuBuilder class.  This is done to have a consistent output with the rest of the command-lines. 


git-svn-id: https://svn.forgerock.org/opendj/trunk@3485 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

19 Nov, 2007

2 commits

16 Nov, 2007

1 commit

  • 5fa5763c   Update admin framework and dsconfig to support tagging ... Browse Dir » 
    of component definitions as advanced and customizable:

* advanced components: these will not be displayed by
  default in dsconfig. Examples include the various
  system backends

* customizable components: these components are tagged
  as intended for customization using the CLI XML
  profile. Customizable components are usually the top
  level components previously referred to as "generic"
  by dsconfig. This term confused users who would, for
  example, mistake a "generic" backend for a JE backend.

This change is part of issue 1829.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3460 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

15 Nov, 2007

1 commit

  • 832a958d   CLI part for Issue 2424 (Impact of generation ID on binary copy). ... Browse Dir » 
    New two subcommands have been added to dsreplication:

Usage:

$ dsreplication pre-external-initialization --help
dsreplication pre-external-initialization {options}
This subcommand must be called before initializing the contents of all the replicated servers using the tool import-ldif or the binary copy method for replication to work.  You must specify the list of Base DNs that will be initialized and you must provide the credentials of any of the servers that is being replicated.  After calling this subcommand, you must initialize the contents of all the servers in the topology and after the initialization is over you must call the subcommand {post-external-initialization}.
Global Options:    See "dsreplication --help"

SubCommand Options:
-h, --hostname {host}
    Directory server hostname or IP address
-p, --port {port}
    Directory server port number
-Z, --useSSL
    Use SSL for secure communication with the server
-q, --useStartTLS
    Use StartTLS to secure communication with the server
-l, --only-local
    Use this option when only the contents of the specified directory server will be initialized with an external method (import-ldif command or binary copy)


$ dsreplication post-external-initialization --help
Usage:  dsreplication post-external-initialization {options}
This subcommand must be called after initializing the contents of all the replicated servers using the tool import-ldif or the binary copy method for replication to work.  You must specify the list of Base DNs that have been initialized and you must provide the credentials of any of the servers that is being replicated.  See the usage of the subcommand {pre-external-initialization} for more information.

Global Options:
    See "dsreplication --help"

SubCommand Options:
-h, --hostname {host}
    Directory server hostname or IP address
-p, --port {port}
    Directory server port number
-Z, --useSSL
    Use SSL for secure communication with the server
-q, --useStartTLS
    Use StartTLS to secure communication with the server


git-svn-id: https://svn.forgerock.org/opendj/trunk@3455 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

14 Nov, 2007

2 commits

13 Nov, 2007

2 commits

12 Nov, 2007

1 commit

  • 6db22638   Update the dsreplication command-line to be consistent with dsconfig in the use … ... Browse Dir » 
    …of menus and in the order that questions to connect to the servers.
Update the upgrade to use the same menus as the other command-lines.
Do some minor changes in the uninstall command-line in order to be more consistent with dsconfig in the order where the connection parameters are provided.
Fix a bug in ApplicationTrustManager related to the accepted certificates when there is a mismatch between the certificate and the host name.
Do some refactorization of the code and remove the CliApplicationHelper class so that we use ConsoleApplication everywhere.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3435 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

09 Nov, 2007

2 commits

  • d5442b54   This set of updates fix several issues related to the JEB backend: ... Browse Dir » 
    1. The db directory is now automatically created if it doesn't alreadly exist. When changing the db directory, a message is now displayed to let the user know the files will have to be manually moved and the backend restarted. (Issue 1979)

2. The backend no longer uses the Database.count method in JE as it is too expensive for large databases. The count can also be inaccurate when concurrent operations are executing on the server. This was causing the getEntryCount method up to 20 seconds to return. The count is now obtained from the id2subtree index. If the count is not maintained or the index is corrupt, it will fall back to using Database.count. (Issue 2581 and Issue 2420) 



git-svn-id: https://svn.forgerock.org/opendj/trunk@3434 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     
  • fcdb2e12   Be explicit about the fact that we require a fully qualified name of the host na… ... Browse Dir » 
    …me in the dsreplication usage.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3428 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

08 Nov, 2007

2 commits

  • c33ffd2d   Fix for issue 2575. ... Browse Dir » 
    The problem is that there is a timeout when reading the monitoring informations 
on the server and the code did not handle this properly.

I have made the method Utils.getMessage to handle properly the case when a Topol
ogyCacheException has not a Throwable cause.  In addition to that the method ret
urns a specific message when a timeout occurs.  Finally the timeout thresold has
 been risen from 10 to 30 seconds to be able to read the topology.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3426 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 10c22e4f   Fix for issue 2573. ... Browse Dir » 
    Fix the copy/paste errors in the description of the destination server arguments for the dsreplication initialize sub-command.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3424 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara