Bug 42796 - Permormance issue with Websphere Application server 6.0.2.17 and JDK 1.4
Summary: Permormance issue with Websphere Application server 6.0.2.17 and JDK 1.4
Status: RESOLVED INVALID
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.2
Hardware: Sun Solaris
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords: JDK1.4
Depends on:
Blocks:
 
Reported: 2007-07-02 10:18 UTC by Jacob Joseph
Modified: 2007-08-22 20:17 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 Jacob Joseph 2007-07-02 10:18:23 UTC 
Hi,

We recently upgraded our application server from Webshpere Application server 
5.0.2.8 (JDK 1.3) to Websphere Application Server 6.0.2.17 (JDK 1.4). We had 
major performance degradation in doing so. Upon investigation we found that 
log4j logging is taking almost thrice the time it used to take in WAS 5028.

It would be great if someone can throw some light on the above mentioned issue.

The version of log4j we are using is 1.2.8 (we are using the same set of jars 
and same version of log4j in both servers.)
Comment 1 Curt Arnold 2007-08-22 20:17:13 UTC 
This is a request for advice or assistance that should be posted to log4j-user, not a bug for the developers 
to fix.