tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49600] New: Bad exception thrown by ProxyDirContext.lookup
Date Fri, 16 Jul 2010 09:38:51 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49600

           Summary: Bad exception thrown by ProxyDirContext.lookup
           Product: Tomcat 7
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: mguillemot@yahoo.fr


Created an attachment (id=25766)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=25766)
Unit tests illustrating the problems

Two problems with exception thrown by ProxyDirContext.lookup

- ProxyDirContext.lookup throws notFoundException when the entry doesn't exist.
notFoundException is a field and therefore initialized at ProxyDirContext
creation.

The consequence is that the exception thrown contains a stacktrace that has
nothing to do with the current execution stack. This makes difficult to find
the root cause of a problem. If this is really an optimization (what is the
gain), then what about making this field static?

- ProxyDirContext.lookup is not consistent: for the same call it may throw
NamingException or NameNotFoundException depending whether the cache has been
used or not.

Problems occur in Tomcat 6 and 7.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message