directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Created: (DIREVE-89) Better exception handling on Modify ops
Date Sat, 27 Nov 2004 17:12:18 GMT
Better exception handling on Modify ops
---------------------------------------

         Key: DIREVE-89
         URL: http://nagoya.apache.org/jira/browse/DIREVE-89
     Project: Directory Eve
        Type: Improvement
  Components: jndi-provider, protocol  
    Reporter: Alex Karasulu
 Assigned to: Alex Karasulu 


Modifications where we have an unknown attribute should throw the right Attribute unknow or
whatever exception as required by the LDAP JNDI provider implementers guide.  Here's an example
of a cryptic modification exception:


12:04:42 PM: Failed to read entry uid=admin, ou=system
Root error: [LDAP: error code 54 - failed on search operation:
org.apache.ldap.common.message.SearchRequestImpl@16f5261
javax.naming.NamingException: OID for name 'blah' was not found within the OID registry
	at org.apache.eve.schema.GlobalOidRegistry.getOid(GlobalOidRegistry.java:161)
	at org.apache.eve.schema.GlobalAttributeTypeRegistry.lookup(GlobalAttributeTypeRegistry.java:135)
	at org.apache.eve.jndi.ibs.SchemaService$BinaryAttributeFilter.doFilter(SchemaService.java:149)
	at org.apache.eve.jndi.ibs.SchemaService$BinaryAttributeFilter.accept(SchemaService.java:192)
	at org.apache.eve.jndi.ibs.FilterServiceImpl.accept(FilterServiceImpl.java:228)
	at org.apache.eve.jndi.ibs.FilterServiceImpl.access$0(FilterServiceImpl.java:219)
	at org.apache.eve.jndi.ibs.FilterServiceImpl$2.accept(FilterServiceImpl.java:193)
	at org.apache.eve.db.ResultFilteringEnumeration.prefetch(ResultFilteringEnumeration.java:254)
	at org.apache.eve.db.ResultFilteringEnumeration.<init>(ResultFilteringEnumeration.java:88)
	at org.apache.eve.jndi.ibs.FilterServiceImpl.search(FilterServiceImpl.java:186)
	at org.apache.eve.jndi.BaseInterceptor.invoke(BaseInterceptor.java:173)
	at org.apache.eve.jndi.FailFastPipeline.invoke(FailFastPipeline.java:62)
	at org.apache.eve.jndi.EveJndiProvider.invoke(EveJndiProvider.java:241)
	at $Proxy0.search(Unknown Source)
	at org.apache.eve.jndi.EveDirContext.search(EveDirContext.java:539)
	at org.apache.eve.jndi.EveDirContext.search(EveDirContext.java:498)
	at org.apache.eve.protocol.SearchHandler.handle(SearchHandler.java:91)
	at org.apache.seda.protocol.DefaultRequestProcessor.reply(DefaultRequestProcessor.java:133)
	at org.apache.seda.protocol.DefaultRequestProcessor.access$200(DefaultRequestProcessor.java:44)
	at org.apache.seda.protocol.DefaultRequestProcessor$ProcessorStageHandler.handleEvent(DefaultRequestProcessor.java:207)
	at org.apache.seda.stage.DefaultStage$ExecutableHandler.run(DefaultStage.java:311)
	at org.apache.seda.thread.AbstractThreadPool$AbstractWorker.run(AbstractThreadPool.java:202)




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message