tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robinson, Eric" <eric.robin...@pmcipa.com>
Subject RE: Someone Please: Why Is Tomcat Looking In The Wrong Directory?
Date Tue, 01 Aug 2006 17:02:27 GMT
Chris,

It makes sense, but before I try the symlink approach, be advised of the
full scenario. Multiple doctor's offices will be connected to the same
server. Each office will have its own instance of tomcat running a copy
(sometimes a different version) of the 3rd party app. The config files
are different for each site. For example, the file
/home/myacct/tomcat5/webapps/mobiledoc/mobiledocconfig.properties
contains database connection information so each instance of the
mobiledoc application connects to a matching mysql database (on a
different server). Does the brute-force approach you outlined still
apply?

--
Eric Robinson 




Disclaimer - August 1, 2006 
This email and any files transmitted with it are confidential and intended solely for Tomcat
Users List. If you are not the named addressee you should not disseminate, distribute, copy
or alter this email. Any views or opinions presented in this email are solely those of the
author and might not represent those of Physician Select Management (PSM) or Physician's Managed
Care (PMC). Warning: Although the message sender has taken reasonable precautions to ensure
no viruses are present in this email, neither PSM nor PMC can accept responsibility for any
loss or damage arising from the use of this email or attachments.-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net] 
Sent: Tuesday, August 01, 2006 9:55 AM
To: Tomcat Users List
Subject: Re: Someone Please: Why Is Tomcat Looking In The Wrong
Directory?

Eric,

> java.io.FileNotFoundException:
> /usr/local/tomcat5/webapps/mobiledoc/conf/mobiledoccfg.properties (No 
> such file or directory)
> 
> Grrr...

Okay, time for the brute force method:

$ grep "conf/mobiledoccfg" `find /home/myacct/tomcat5/ -type f`

Assuming that you find a .class file (or even better, a Java or JSP
file) that contains that path, poke around in there to see if the path
has been hard-coded.

If it has been hard-coded, call up your 3rd-party vendor and let them
know, and ask for a patch.

Here's a quick workaround:

$ cd /usr/local/tomcat5
$ rm -rf conf     (check to see if this is okay!!)
$ ln -s /home/myaccount/tomcat5/conf .

That ought to do the trick. You might have to turn on symlink following
in order to get it working.

If none of this makes sense or you can't find anything, I might be
willing to take you up on your offer for payment to take a first-hand
look. ;)

-chris



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message