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 51744] JNDI Lookup Error after a Context is closed
Date Tue, 25 Oct 2011 21:17:49 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51744

Leonid Mikhailov <lmikhailov@esri.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|7.0.14                      |7.0.22
         OS/Version|Linux                       |Windows 7

--- Comment #9 from Leonid Mikhailov <lmikhailov@esri.com> 2011-10-25 21:17:49 UTC ---
Guys,

It appears that something is not quite right with this fix in 7.0.22. The
following worked just fine in 7.0.14 (and GlassFish, WebLogic, and WebSphere)
and now fails on envCtx.close() with "Context is read only" message.

javax.naming.Context initCtx = new InitialContext();
javax.naming.Context envCtx = (javax.naming.Context)
initCtx.lookup("java:comp/env");
//some clever logic that uses envCtx
envCtx.close();//Fails here!
initCtx.close();

According to JavaDoc I should be able to safely close the context when I am
done with it.  

Thanks,

Leon

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