I (accidentally) upgraded my glibc a little too far with debian and I ran
into this problem with the blackdown JDK, so I would say that is a yes. I
am using j2sdk1.3 1.3.1-1. I would have to look at the glibc version I
upgraded to (I eventually downgraded).
-nicole
At 21:40 on Nov 7, Joseph Shra
I;m curious if you looked at all to the program size, and not the size
of the GC ? It may be that a 'native' routine leaks independently of the
GC.
BTW, that a yes. JVM calls upon many functions/services/libraries to do
its bidding. Any one of them may request memory ( from the system pool )
,
My favourite: SAP-DB:
http://www.sapdb.org/
http://www.sapdb.org/sap_db_jdbc.htm
I am still surprised that not too many people have not taken up SAP-DB,
despite being GPL and LPGL, and having some features that other proprietary
databases have ( like Oracle's online redo logs )
http://www.sap
i definitely think swap is my issue. I'm kicking myself for not noticing
it...
What's odd is the only thing that has changed on these servers in many weeks
is the java code for our application. We have a fixed heap size if 512MB.
Where is all this extra memory coming from? 1GB real memory and 7
If any memory has paged to swap, garbage collection through the swap
will be excruciatingly slow. Is another app consuming memory, forcing
the server to use the swap partition heavily?
Dave A King wrote:
I'm trying to troubleshoot some really bizarre behavior in a recent build of
our applicatio
I'm trying to troubleshoot some really bizarre behavior in a recent build of
our application. We have changed our memory usage quite a bit, utilizing
more caching, etc. Overall performance has unsurprisingly improved and all
looked good during QA after we tackled some memory leaks and unbounded
c
