Bug #37 Details

Project: Tomcat
Category: Feature Requests
SubCategory: Enhancement
Class: swbug
State: open
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: 3.1
   JVM Release: SE linux1.3.0b7
   Operating System: linux
   OS Release: 2.2
   Platform: i686

Synopsis: 
entire org.apache.tomcat.util package locks up under load

Description:
The use of the StringManager.getManager() that is everywhere in that package makes 
every thread compete for the lock of that class. The only reason I can see why that 
method is synchronized in the first place is to prevent duplicate loads of the same 
ResourceBundle (which would later be garbagecollected anyway...). Therefore either

a) remove the synchronization of StringManager.getManager()
b) pass the manager around within the package

Please note that this method is called MANY times by each thread when writing the 
reponse.
Title: BugRat Bug # 37

BugRat Bug # 37

Project: Tomcat Release: 3.1
Category: Feature Requests SubCategory: Enhancement
Class: swbug State: open
Priority: high Severity: serious
Confidence: public

Date Opened: Sep 30 2000, 05:59:46 CDT
Date Closed: Not closed.
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:
entire org.apache.tomcat.util package locks up under load
Environment: (jvm, os, osrel, platform)
SE linux1.3.0b7, linux, 2.2, i686

Additional Environment Description:

Report Description:
The use of the StringManager.getManager() that is everywhere in that package makes every thread compete for the lock of that class. The only reason I can see why that method is synchronized in the first place is to prevent duplicate loads of the same ResourceBundle (which would later be garbagecollected anyway...). Therefore either a) remove the synchronization of StringManager.getManager() b) pass the manager around within the package Please note that this method is called MANY times by each thread when writing the reponse.

How To Reproduce:

Workaround:

View this Bug online...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to