tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 54168] New: NamingContext.close() throws exception in case of read-only context
Date Mon, 19 Nov 2012 14:13:35 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=54168

            Bug ID: 54168
           Summary: NamingContext.close() throws exception in case of
                    read-only context
           Product: Tomcat 7
           Version: 7.0.32
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: oleg.n.alex@gmail.com
    Classification: Unclassified

The following exception is thrown when closing Context returned for a JNDI
resource defined in server.xml:

javax.naming.OperationNotSupportedException: Context is read only
    at org.apache.naming.NamingContext.checkWritable(NamingContext.java:962)
    at org.apache.naming.NamingContext.close(NamingContext.java:762)
    ...

Looking at the code it looks like there should be call to isWritable(), not
checkWritable, so that it would just return false and close() would do nothing.

-- 
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