org.forgerock / org.forgerock.opendj

28 Feb, 2008

1 commit

27 Feb, 2008

1 commit

  • 069eb677   For Configuration Reference generated doc: ... Browse Dir » 
    Added 2 new parameters (java properties) for M1 needs (1st one only):

OpendsWiki - The URL of the OpenDS Wiki
             (default is "https://www.opends.org/wiki")
OpendsHome - The URL of the OpenDS project Home page
             (default is "http://www.opends.org")

Usage:
In the M1 build target, add :
      <jvmarg value="-DOpendsWiki=https://www.opends.org/<M1 Wiki>"/>
 
Note that as a side effect, now all the html files are generated (index.html and maintop.html were not generated until now)





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

20 Feb, 2008

2 commits

  • 21078a31   Fix for issue 2972 (The usage of stop-ds.bat shows the class name) ... Browse Dir » 
    The fix consists on updating the scripts and the java code to reflect correctly the name of the script and be consistent with all the other batch files (we don not include the .bat on the usage).

Apart from that the modifications include a modification in StatusPanelLauncher so that we use the ArgumentParser class in the whole class (this avoids duplicated code and fixes a bug with the usage).


git-svn-id: https://svn.forgerock.org/opendj/trunk@3900 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • b0edfe56   Fix for issue 2962 (Setup should allow non-secure replication port while LDAP access is SSL-enabled) ... Browse Dir » 
    I was not able to reproduce the issue as it is described but discussing with the QA team we decided that it would be worth to do the following improvements:

1. If we cannot contact on one of the ports of a server that is registered in the ADS we must try to connect to the other ports.

2. We should try to connect to the port specified by the user in the setup (when specifying the server that we want to configure replication with).  This also applies to the dsreplication utility.

Beside the two improvements above, I updated the code so that the progress messages use the port specified by the user to identify the OpenDS instances.

Without these changes (if security is configured) the user can be confused since we refer to secure ports (even if (s)he specified the regular LDAP port) and we ask the user to accept certificates.

Concerning the implementation, basically I added a class called PreferredConnection that is used to describe the LDAP URL and connection specified by the user.  The objects are passed to the TopologyCache and the TopologyCache passes them to ServerLoader which is the class that creates the connection to the servers to read their configuration. 


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

19 Feb, 2008

2 commits

  • 21382b1b   Fix for 2968 : dependent ADD operation can incorrectly generate conflicting entries ... Browse Dir » 
    With the following sequence of operation :
Add first entry with DN X
delete first entry with DN X
Add another entry with DN X

The second ADD is sometimes not computed as dependent and a false
DN conflict is sometime created.

This happens when the delete operation complete after we tried to process the second
add but before we check for dependencies in the operation queue.

To avoid this problem all operations must be attempted twice before going into
the conflict resolution mechanism, unfortunately in this case, we were not checking if
this is the first try he operation is attempted and therefore were going directory into
conflict resolution.

git-svn-id: https://svn.forgerock.org/opendj/trunk@3898 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • 2df342a4   Fix for issue 2970 (Off-line export-ldif -n replicationChanges shouldn't return '0') ... Browse Dir » 
    Make the code to return a error 1 if there is a problem with the export


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

15 Feb, 2008

5 commits

  • 536583cc   Fix for issue 2886 (Cannot get status from running server without authenticating) ... Browse Dir » 
    The code has been modified (with no new arguments) in order to work in a best-effort mode.  If the user does not provide authentication we will display the same information independently of whether the server is running or not.  We still display the messages informing that authentication is required to display some monitoring data.

The status panel code has also been updated to have the same behavior.

However it will be required anyhow to provide authentication to display monitoring information since this information is available only through LDAP.

In addition to this changes the following issues have been fixed:

1. Close the ManagementContext created by the LDAPConsoleInteraction object so that we have only one open connection to the server.
2. Fix a bug when the user chose to accept automatically certificates (the default trust manager was used in this case and we could not connect).


git-svn-id: https://svn.forgerock.org/opendj/trunk@3893 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 12241ab4   Fix for issue 2960 (uninstall -? launches graphical interface) ... Browse Dir » 
    Instead of checking for the presence of the help argument call SubCommandArgumentParser.usageOrVersionDisplayed that actually takes into account the built-in option '?'.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3891 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 158ea91b   Sorry, fixed mistake by previous commit ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3890 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ctissot
     
  • 448f0e9b   Changed build repository for Java WebStart script ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3889 41b1ffd8-f28e-4786-ab96-9950f0a78031
    ctissot
     
  • 97227d81   Fix 2904: "dsreplication enable" cannot initialize b11 from b10 because the sche… ... Browse Dir » 
    …ma initialization fails on the config schema.
The code already tests whether the new objectclass is part of the config schema and then excludes it from the import. That's fine.
Except that the test relies on the decoding of the OC and fails if the new OC comes with a new attribute.
The fix consists in relaxing the decoding when doing the test .. and really doing a strict decoding after the test once we know the new OC is not a config OC.



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

14 Feb, 2008

5 commits

13 Feb, 2008

11 commits

  • e265c384   Fix a typo in a comment in installer.xml and use a proper formatting for the pro… ... Browse Dir » 
    …gress message in the uninstaller when disabling the windows service.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3880 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • f381d08f   Add a line break to the progress message displayed when we enable the windows service. ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@3879 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • b67e5d05   - [Issue 2877] : Issue with creation of connection handler: ... Browse Dir » 
    refactor "address in use" test from connection handled implementations into a standalone isAddressInUse() StaticUtils method.
  invoke isAddressInUse() when validating connection handler config and connection handler initialization, both LDAP and JMX.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3878 41b1ffd8-f28e-4786-ab96-9950f0a78031
    abobrov
     
  • 98040c09   - Issue #2004 (cont'd) (automatically generate HTML configuration guide) ... Browse Dir » 
    Added duration syntax pointer on new wiki page



git-svn-id: https://svn.forgerock.org/opendj/trunk@3877 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jcambon
     
  • 6fcbcf2f   Fix end point ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3876 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • 438c97a1   Commit flag day changes for r3873. ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@3875 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • c234442e   Improve error logging on monitor data when a server is too late ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3874 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • c0c65a00   Fix relating to issues 2813 and 2578. Make DN string representations more user-f… ... Browse Dir » 
    …riendly when they contain non-ascii characters.

This change is a flag day due to the potential for database format incompatibilities introduced by the change in DN normalized form.

Currently the DN and RDN implementations are very conservative regarding the string representation of DNs that they construct. Any non-ascii characters are escaped using back-slashes. For example, the DN:

   uid=Météo.0,ou=People,dc=example,dc=com

Is encoded as:

   uid=M\c3\a9t\c3\a9o.0,ou=People,dc=example,dc=com

Which is not very readable in LDAP client applications. It is also much less space efficient - something we should consider if we wish to have non-western users of OpenDS who will be heavy users of multi-byte UTF8 sequences. For example, a single Chinese character would be encoded in UTF8 as 3 or 4 bytes IIRC which would equate to 9-12 bytes or a 3X increase. This would have implications for database performance (substrings) and space efficiency.

The change is not without its minor problems however:

  1. LDIF cannot contain non-ascii characters so any DNs or attribute
     values must be base-64 encoded in order for the LDIF to be valid.
     This is not very user-friendly, but it's easier for inquiring
     users to decode base 64 than to manually decode UTF8 byte
     sequences. A future change could improve this behavior by making
     our LDIF generation tools (e.g. ldapsearch, ldif-export) output
     comments before each base-64 encoded DN / value containing the DN
     / value in the client's native character set. This is something
     that OpenLDAP clients do and I think it is a nice usability feature

  2. the dn2id index and any DN / RDN syntax attribute indexes will be
     potentially invalid due to the modified DN / RDN normalization
     (hence this change is a flag-day)

  3. DNs returned to LDAPv2 clients will potentially contain non-T.61
     characters (LDAPv3 uses UTF8 and LDAPv2 uses T.61). However, I
     don't think we are bothered by this because we already break
     compatibility for LDAPv2 clients for directory string based
     attribute values which we also return using UTF8.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3873 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • 5c0b329c   Fix potential NPE when computing monitor data ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3872 41b1ffd8-f28e-4786-ab96-9950f0a78031
    pgamba
     
  • f77c21f9   Fix for issue 2652 (stop-ds should provide the -t 0 option) ... Browse Dir » 
    The t option now supports the "0" value.

I have updated the usage of the stopTime argument to be consistent with the usage of the startTime argument of the other command-lines.

I have fixed a typo in the startTime argument usage.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3870 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • da42dae7   Fix 2911 - dsreplication pre/post-external initialisation fails to clear all the changelogs ... Browse Dir » 
    The following changes fixes the fact that the 'server-state' information, visible under cn=monitor, is erroneous (not updated) when an OpenDS instance starts and there were some changes done on the topology while 
this server was stopped. This bug can always be seen when running the scenario to reproduce #Issue 2911.

This issue comes from the fact that, at start time, the main thread creates and start the ReplicationDomain thread, that itself creates and starts the replication listener threads.
Then the listener thread start receiving some updates, and the replay thread start replaying them.
While, with a race condition, in the main thread, the multimaster replication registers the post op plugin of the replication.
So the first operations are successfully replayed but the necessary replication post op plugin is not called by the core server and the server-state is not updated.

To fix properly that issue, we need to wait for the Replication Master Synchro provider to be successfully registered in the core, before starting listening for the replication updates. So a new method called 
'completeSynchronizationProvider()' (any better proposal is welcome) is added to the SynchronizationProvider API for that purpose.

A side effect is that a ReplicationDomain must now be started after creation. Some replication tests, that create ReplicationDomain on the fly, are also fixed here.



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

12 Feb, 2008

12 commits

11 Feb, 2008

1 commit

  • d984382d   Fix for issue 2130 (i18n CLI usage placeholders) ... Browse Dir » 
    The fix consists on changing the placeHolderValue from a String to a Message so that it can be localized.  The interfaces and constructors of the argument objects have been updated to reflect this change. The placeholders are defined in tool.properties.



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