You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/14 19:01:54 UTC

DO NOT REPLY [Bug 31720] New: - JNDI NamingContext is not thread safe

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31720>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31720

JNDI NamingContext is not thread safe

           Summary: JNDI NamingContext is not thread safe
           Product: Tomcat 5
           Version: 5.0.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Catalina:Modules
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: gawor@mcs.anl.gov


To make NamingContext thread safe, I created a synchronized context wrapper 
(SynchronizedContext) around an existing context. Then modified the code to 
wrap the NamingContext instances in SynchronizedContext if told to do so. By 
passing "org.apache.naming.synchronized" env property you can control if this 
synchronization wrapping is done or not.

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