the application is a server side single threaded app that does an XML post and parses it there is a Oracle database connection made with each request

Apple's WebObjects is used

   Pmapout1.txt is a pmap dump taken right after the process starts up.
   Pmapout2.txt is taken after 1 hour after the process has stabilized
while
   running upto 1000 transactions. Of particular concern is the heap segment at
 0002A000
   which grows from 5 to 100 MB.
   
   Before: 0002A000 5504 5448 2008 3440 read/write/exec [ heap ]
   After: 0002A000 104960 104904 1184 103720 read/write/exec [ heap ]
   
   We don't think this is related to the java heap which remains stable:
   
   Before: F0000000 115712 58336 1392 56944 read/write/exec [ anon ]
   After: F0000000 116736 94200 8 94192 read/write/exec [ anon ]
   
   
   2. top results
   
    Before: 178M (90M-Res)
    After: 282M (249M-Res)
    
   
   3. vm arguments
   
   -client -XX:+DisableExplicitGC -XX:NewRatio=2 -Xms96M -Xmx96M
   

A simple program shows that there is more memory used in 1.4.1 and some would be expected but over 100m is unexeptable.

The only test case is on the customer system and they are going to give us access to it to.

there isn't unbounded memory growth, but the 100m jump from 1.3.1 is a great concern