07 Jun, 2011
3 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6982 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6981 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…uide, as the default of 50# is now appropriate for most deployments. git-svn-id: https://svn.forgerock.org/opendj/trunk@6980 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Jun, 2011
7 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6979 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…current unit test runs. git-svn-id: https://svn.forgerock.org/opendj/trunk@6977 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…eflecting things I found while writing the draft chapter. git-svn-id: https://svn.forgerock.org/opendj/trunk@6976 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…to the isExceptional method describing exactly which result codes are not error results. git-svn-id: https://svn.forgerock.org/opendj/trunk@6975 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The "approx-older-change-not-synchronized-millis" monitor attribute is optional, so we should avoid throwing unnecessary exceptions. git-svn-id: https://svn.forgerock.org/opendj/trunk@6974 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…e size, and replication purge delay See issue description for exact changes. git-svn-id: https://svn.forgerock.org/opendj/trunk@6973 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…the developer (e.g. ldapsearch). git-svn-id: https://svn.forgerock.org/opendj/trunk@6972 41b1ffd8-f28e-4786-ab96-9950f0a78031
03 Jun, 2011
4 commits
-
…nfig.ldif (see dn: cn=Collation Matching Rule,cn=Matching Rules,cn=config) git-svn-id: https://svn.forgerock.org/opendj/trunk@6971 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6970 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6969 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6968 41b1ffd8-f28e-4786-ab96-9950f0a78031
02 Jun, 2011
1 commit
-
Added the following APIs: * RequestContext * CancelRequestListener * RequestHandlerFactory * Connections.newServerConnectionFactory(RequestHandler) * Connections.newServerConnectionFactory(RequestHandlerFactory) Updated example proxy and server. git-svn-id: https://svn.forgerock.org/opendj/trunk@6967 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Jun, 2011
4 commits
-
…here are no format arguments git-svn-id: https://svn.forgerock.org/opendj/trunk@6964 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6963 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6962 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6961 41b1ffd8-f28e-4786-ab96-9950f0a78031
31 May, 2011
10 commits
-
…allow clients to access the directory git-svn-id: https://svn.forgerock.org/opendj/trunk@6960 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6959 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6956 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This is for the trunk. git-svn-id: https://svn.forgerock.org/opendj/trunk@6953 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6952 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6951 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6950 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6949 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6948 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6947 41b1ffd8-f28e-4786-ab96-9950f0a78031
30 May, 2011
8 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6946 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6945 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…hanges with updates and purging. More specifically these changes are resolving the following issues : OPENDJ-57 - ECL: lastChangeNumber and firstChangeNumber reset to zero when the changelog is purged to empty OPENDJ-172 - External ChangeLog Cookie varies when searching with an empty cookie. Cookie should be reproducible. OPENDJ-173 - External ChangeLog cookies content is altered by Change purging and prevents from continuing search with a previous returned cookie. The changes are multiples and interdependant, hence a single commit. But : - The DraftCNDB is now purged but always keep the last record. The firstKey value is updated accordingly. - The ReplicationDB is purged but always keep the last record before the trimdate. - If no cookie is specified, the initial cookie is computed from the ReplicationDomain StartState, but keeping only change numbers older than the trimdate. - Fix a possible issue when searching a ChangeNumber, and a Count record is found, the changeNumber value was not correct. These changes mostly revert revision 6406 which meant to fix the same issue (cookies would become obsolete and a search using them returns an Unwilling To Perform), but only managed to hide the root cause of the issue. git-svn-id: https://svn.forgerock.org/opendj/trunk@6943 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Finally, the lastExternalChangelogCookie attribute should be consistent with the ChangeLogCookie operational attribute. Let's make them both DirectoryString. git-svn-id: https://svn.forgerock.org/opendj/trunk@6942 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6941 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…astExternalChangelogCookie. firstChangeNumber and lastChangeNumber are now Integer, single valued. The lastExternalChangelogCookie is an opaque set of bytes. I agree it looks like a string, but it would be better handled as opaque, thus an OCTET STRING. I'm marking it SINGLE-VALUE though. git-svn-id: https://svn.forgerock.org/opendj/trunk@6940 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
No brainer : If there's no value, create an empty MultiDomainServerState. The server already knows how to deal with them. git-svn-id: https://svn.forgerock.org/opendj/trunk@6938 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Fix now check if the control is present in the search and returns it only if so. Tests have been added in unit-tests to verify this. git-svn-id: https://svn.forgerock.org/opendj/trunk@6936 41b1ffd8-f28e-4786-ab96-9950f0a78031
27 May, 2011
3 commits
-
…from working, however doing so seems to significantly impact max throughput (around 20%), probably due to context switching during Future.get() calls. #### From OpenDS SDK SVN history for revision 6650 ##### Backout xxxrate threading changes introduced in revision 6648 since they prevent the -M (throughput throttling) option from working. Several attempts were made to fix it: 1) Putting the adaptive sleeps inside the ConnectionWorker.operationComplete callback causes the Grizzly worker thread to be blocked which, in turn, delays other incoming results on other connections (and impacts their etime calculations). 2) Instead of doing adaptive sleeps, I tried putting the "delayed" requests into a ScheduledExecuterService, but this just introduces more complexity (e.g. more threads), more context switches, etc. At this point, I decided to go back to the original design. The new threading strategy introduced in revision 6649 seems to more than compensate for the performance benefits made in revision 6648. git-svn-id: https://svn.forgerock.org/opendj/trunk@6935 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6934 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@6933 41b1ffd8-f28e-4786-ab96-9950f0a78031