Bug 35735 - Classloader often does not seperate Webapp Classpaths
Summary: Classloader often does not seperate Webapp Classpaths
Status: RESOLVED INVALID
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Jasper (show other bugs)
Version: 5.5.7
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-14 14:48 UTC by Power-Netz HOSD
Modified: 2005-07-14 06:51 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Power-Netz HOSD 2005-07-14 14:48:18 UTC 
Hi, 

we use TC 5.5.7 with 5 WebApps which have ususally the same classes, but are
complettly seperated by directories. Think of it as Production-, Beta-
and Developer-WebApps. 

From time to time, we restart TC .

If we do, and the dev webapp is first who is accesed and for this loads it
classes, these classes are also used in the production web.

for 95% of the used classes in this three apps, code and class methodes
are the same, as the jsps are the same too. 

Our Production web does not reload classes in the classpath for speed reasons.
The dev app does reload the classes. 

We used TC3 before we switched to TC5 and TC3 did NEVER show this behaviour.

What do you need from our server to investigate this?
Comment 1 Remy Maucherat 2005-07-14 14:51:50 UTC 
Please post on tomcat-user instead.