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 40801] New: - antiResourceLocking causes undexpected context results from jndi queries
Date Thu, 19 Oct 2006 22:46:41 GMT
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=40801>.
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=40801

           Summary: antiResourceLocking causes undexpected context results
                    from jndi queries
           Product: Tomcat 5
           Version: 5.5.20
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rick.fisk@authoria.com


In attempting to resolve undeploy/deploy issues, I turned on antiJarLocking 
and antiResourceLocking in the CATALINE_HOME/conf/context.xml file.

This worked as expected but for a pretty nasty side-effect.

Our app queries its own deployment context to ferret out db connect strings 
via a matching jndi tree. We have a webapps/DeploymentProperties/ directory 
which contains the properties files for our context ie; 
DeploymentProperties/application/domaindb.properties would contain the db 
settings for 'application' (we deploy for a specific customer in this fashion).

Because antiResourceLocking is "moving" context - the apps end up in the temp 
directory as x-application (where x is some number), calls to query the 
context no longer return a context matching our jndi properties tree.

We are unaware of a workaround for this. We are using getServletContextName() 
to return our context which is now a moving target. Instead of 'application' 
we get 'x-application' and the app refuses to start when it cannot find its db 
connection properties file.

We'd like to find some solution that would not then break the same application 
when deployed on tomcaton linux without these settings enabled.

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

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


Mime
View raw message