13 Oct, 2009
6 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5970 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The problem was that the code assumed that the only windows OS supporting UAC was Windows Vista. This was the case before Windows 2008 came out. The fix consists on creating a method that allows identifying which OS versions of vista support UAC and which do not. git-svn-id: https://svn.forgerock.org/opendj/trunk@5969 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5968 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
In the case of Windows, the options are tested using the script helpers. If there is an error these scripts require the user to provide some input. The fix consists on allowing the scripts to write the message to the process output and after that to kill the process (we used to kill the process right after detecting an error). git-svn-id: https://svn.forgerock.org/opendj/trunk@5967 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5966 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Do the same as is done for the instance path with the install root: try to use File.getCanonicalPath to avoid having relative paths (../..). Since this is done only once when the config file handler is created, there is no performance impact. git-svn-id: https://svn.forgerock.org/opendj/trunk@5964 41b1ffd8-f28e-4786-ab96-9950f0a78031
12 Oct, 2009
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5960 41b1ffd8-f28e-4786-ab96-9950f0a78031
09 Oct, 2009
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5957 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5956 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5953 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5952 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Oct, 2009
7 commits
-
in handshake phase instead of a ReplServerStartMsg. ReplServerStartDSMsg contains same thing as ReplServerStartMsg but also contains - replication server weight - number of ciurrently connected DS on the RS => both will be used for future new RS choice algorithm - Addition of a StopMsg sent: - when any entity (DS,RS) is closing a connection (sent just before) with a peer - when DS finishes phase 1 of handshake (was gathering RS info for RS choice so sent just after new ReplServerStartDSMsg is received) => both are used to distinguish between a proper connection closure (no message) and an unexpected one (error log) - Compatibility between protocol V4 and V3 (and before) - changed MonitorMsg to never be created with a protocol version - MonitorMsg now always sent with publish(msg, version) (publish method without version was used so bug) - TopologyMsg now always sent with publish(msg, version) (publish method without version was used so bug) git-svn-id: https://svn.forgerock.org/opendj/trunk@5950 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5949 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5948 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5946 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5944 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5943 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5942 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Oct, 2009
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5941 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5940 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Since using File when you have different OS in the control panel and in the managed server can be really problematic, use String instead in the ServerDescriptor object. git-svn-id: https://svn.forgerock.org/opendj/trunk@5937 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
value of 65535 for the server-id property. Nevertheless, the server-id in the ReplicationDomain implementation is managed as a short allowing a maximum value of 32767. With this change the code now uses an int to store the server-id. The maximum is still limited to 65535 and this is enforced by the management framework. This change should not impact compatibility as the messages exchanged by the servers are not impacted. This change also add unit tests allowing to test the compatibility of the V4 protocol with V3 protocol. git-svn-id: https://svn.forgerock.org/opendj/trunk@5936 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Oct, 2009
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5932 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Add the option to specify the number of threads to be used for the import and the option to do the DN check later in the import LDIF process. git-svn-id: https://svn.forgerock.org/opendj/trunk@5930 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5929 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5928 41b1ffd8-f28e-4786-ab96-9950f0a78031
05 Oct, 2009
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5923 41b1ffd8-f28e-4786-ab96-9950f0a78031
04 Oct, 2009
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5922 41b1ffd8-f28e-4786-ab96-9950f0a78031
03 Oct, 2009
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5921 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Oct, 2009
7 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5920 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5919 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…e at the product level. git-svn-id: https://svn.forgerock.org/opendj/trunk@5918 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5917 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5916 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The failures are caused by a real but very rare and minor bug. When a Directory Server connects to a Replication Server at the same time a change is generated by another server and this change is the first to be sent to the directory server it can be sent with the wrong assured status. This cause no harm in a real deployment but was causing test failure in our case. This is fixed by using the message from the message queue rather than from the replication log git-svn-id: https://svn.forgerock.org/opendj/trunk@5915 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5914 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Oct, 2009
4 commits
-
…d to run as a service. git-svn-id: https://svn.forgerock.org/opendj/trunk@5906 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5905 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@5904 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…d iterations cancellation process. git-svn-id: https://svn.forgerock.org/opendj/trunk@5903 41b1ffd8-f28e-4786-ab96-9950f0a78031