When running a stress test against an internal release of Sun ONE Web Server 6.1 (which is still under development) we noticed a memory leak on Solaris and Solaris x86 (but not Win2k). We've identified the Java portion of the workload as what is triggering the leak in the server and dbx points to leaks from within the JVM.

The webserver has an embedded JVM and uses JDK 1.4.1_03.

Java HotSpot(TM) Server VM, Version 1.4.1_03

% bin/java -server -version
java version "1.4.1_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_03-b02)
Java HotSpot(TM) Server VM (build 1.4.1_03-b02, mixed mode)

http://iwsqa.india.sun.com/S1WS61/Stress/s1ws61_stress_test.html and the attachment to Bug# 4878425 has details about the memory growth over time.

We set -Xms and -Xmx to the same number but still noticed the memory growth.

Enabled memory leak checking in dbx and periodically did a 'showleaks' and noticed that OopMapCache was always listed as a leak.

Actual leaks report (actual leaks: 43 total size: 7688 bytes)

 Total Num of Leaked Allocation call stack
 Size Blocks Block
                Address
====== ====== ========== =======================================
  6656 13 - os::malloc < OopMapCache::OopMapCache #Nvariant 1
  1032 30 - os::malloc < CHeapObj::operator new

showleaks -a at the end showed the following (only top few lines listed) :

Possible leaks report (possible leaks: 0 total size: 0 bytes)
 56320 110 - os::malloc < OopMapCache::OopMapCache #Nvariant 1
 13128 38 - calloc < 0xa7503b50
  9720 276 - os::malloc < CHeapObj::operator new
  2463 115 - _strdup < FileRealm::add
  1120 20 - calloc < Java_java_util_zip_Inflater_init

(more showleaks snapshots are in the Comments section of Bug# 4878425)

With or without the SecurityManager we still see OopMapCache leaks reported by showleaks.

Please let me know if you need more information. I can also help with installing and configuring S1WS 6.1 on your machine.

###@###.### 2003-07-16
--