Yeah, that's it ;0) [Edit: Found my post}

Post #154,033 by mmoffitt 5/6/04 10:56:46 AM 5/6/04 11:14:25 AM Reply	Yeah, that's it ;0) [Edit: Found my post} We struggled with the same problem for almost two months. Having tried everything suggested here (and various and sundry other things) with no success, we finally downgraded glibc to version 2.2.4. It works and keeps running for weeks. We were able to identify that the bug is in the garbage collection of the jvm - at least that's where our jvm was crashing all the time. It looks like libjvm.so is dependent upon a bug in glibc that is not there anymore. With any later version of glibc, we saw crashes in anywhere from minutes to a couple of hours, regardless of which jdk we used. After downgrading glibc, we could use virtually any jdk just fine. If anyone seeing this problem is running tomcat 4.1.29 on a linux distro - and you can, try moving back your glibc. bcnu, Mikem Edited by mmoffitt May 6, 2004, 11:14:25 AM EDT Expand All History
Post #154,042 by admin 5/6/04 11:33:15 AM Reply	Have you since checked the release notes... ... for notations that it works with glibc > 2.2.4 now? Here's what I'm running at home: \nanderson@spork:~$ java -version\njava version "1.4.1"\nJava(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)\nJava HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode)\nanderson@spork:~$ dpkg -l \| grep libc\nii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries and Timezone\n And at work: \nsanderson@bd00402:~$ /usr/local/java/bin/java -version\njava version "1.4.1_06"\nJava(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_06-b01)\nJava HotSpot(TM) Client VM (build 1.4.1_06-b01, mixed mode)\nsanderson@bd00402:~$ dpkg -l \| grep libc\nii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries and Timezone\n I haven't tried 1.4.2 yet. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #154,050 by mmoffitt 5/6/04 11:46:17 AM Reply	No, I haven't. Been too busy w/loads of other stuff. I was just happy to get it running. I will, no doubt, have to re-visit this. It was a panic situation before. The product was delivered two months late, everybody's head was on fire, PHB screaming 'Get it to work! Get it to work!', etc. I'll try to approach it with a more open mind next time. But, the PHB in question is being replaced. This app is our only JSP app and could be redone from scratch w/PHP in a month tops. Dunno if the new PHB will want to continue w/JSP or not (this might be a do-over). Even if we stick with java, I'd bet the ranch that 80% of the code will be reworked completely. I know for sure that the database will be redesigned and that sp's will be used to insert/delete/update data (not to mention all the 'select a.*, b.column1 from table1 a, table2 b where a.name = b.name and a.date = b.date and a.address = b.address and a.plant = b.plant and a.location = b.location and a.type = b.type and a.invoice = b.invoice' crap. Who knows, might even add some Views, Triggers, explicit transaction processing and DRI to the database!) Thanks. bcnu, Mikem

Welcome to IWETHEY!