Leak? Java memory grows and then crashes Jserv

9iAS 9.0.1 (no patch) on Solaris 8 (sparc).  JVM 1.2.2

I'm not getting an Out of memory error.

I tried setting the
wrapper.bin.parameters=-ms128m
wrapper.bin.parameters=-mx384m

course, this only works with Jserv mode set to auto (so it manages instances itself)

but when I do a while loop with pmap -x [pid]|grep total, I can watch the memory grow:

total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272
total Kb  207808   86000    4472   81528
total Kb   42056   23688    4416   19272

[I clicked here]

total Kb  207824   86016    4472   81544
total Kb   42056   23688    4416   19272
total Kb  207848   86040    4472   81568
total Kb   42056   23688    4416   19272
total Kb  207848   86040    4472   81568
total Kb   42056   23688    4416   19272
total Kb  207848   86040    4472   81568
total Kb   42056   23688    4416   19272
total Kb  207848   86040    4472   81568
total Kb   42056   23688    4416   19272

and this continues.  We are really, really sure our code doesn't have any memory leaks and we close db connections.  The point is, I can't keep memory at what I specify.  And eventually, Jserv respawns and we lose the session.  Bad.

If I set it to min=16 max=32 it starts at like 84meg of memory!

I've been searching and trying for 16 hours now.


I would try a patch for Java or 9i but this just started happening (no, I don't know what changed) and I can't find a patch.

My real question:  Is this normal?
milkfilkAsked:
Who is Participating?
 
niggCommented:
It seams to me, that the JVM is running the GarbageCollector very late, so try to limit the the JVM's Memory use. Like that the GC runs more often, but also the sessions get lost, I guess. Otherwise try to put more memory to that machine....

Later..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.