[
https://issues.apache.org/jira/browse/DIRSERVER-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630821#action_12630821
]
Emmanuel Lecharny commented on DIRSERVER-1254:
----------------------------------------------
I cant' reproduce this behavior. Moreover, the MonitorContext attribute is not
declared at all in the server.
I think that the client (Studio) is sending the MonitorContext attribute as a
requested attribute when issuing a seach in RootDSE.
> An error and a warning are shown in the log when accessing the RootDSE
> ----------------------------------------------------------------------
>
> Key: DIRSERVER-1254
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1254
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.4
> Reporter: Pierre-Arnaud Marcelot
> Fix For: 1.5.5
>
>
> An error and a warning are shown in the log when accessing the RootDSE:
> [14:45:19] ERROR
> [org.apache.directory.server.schema.registries.DefaultOidRegistry] - OID for
> name 'monitorcontext' was not found within the OID registry
> [14:45:19] WARN
> [org.apache.directory.server.core.interceptor.context.SearchingOperationContext]
> - Requested attribute monitorcontext does not exist in the schema, it will
> be ignored
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
