---------------------------------------------------------------- BEFORE YOU POST, search the faq at <http://java.apache.org/faq/> WHEN YOU POST, include all relevant version numbers, log files, and configuration files. Don't make us guess your problem!!! ---------------------------------------------------------------- I agree, but the first item I ran across was the replacement of the single lib. I understand the risk involved in replacing a single library and, as is always the case....esp. with Linux, you have to hack it at your own risk. I have the trouble box (very weak in the hardware department) running great with alot of connections, and debug output to the logs for the last day with no errors or problems with the product that we have here at Epicentric. I completely agree with you, and again IT IS VERY RISKY INDEED....as the kernel depends upon the libs, that is why I will always suggest making a copy of the libpthreads and creating an emergency recovery disk set to copy the old one back if needed (which any admin should do)......and....ESP...if your company depends on the box day in and day out.....recognize that you may have alot of explaining to do if the box crashes. I think the better idea is to install an updated glibc package, but a blanket approach to fixing problems is sometimes just as risky (fixing one item but breaking another) esp. with the way in which MDK and RH seem to be diverging on the lib path. Does anyone know (or even speculate) as to why the libs were paired down in the "newest" MDK 6.1 release? My thought was the need for speed, but it's hard to say. The single (backwards) lib approach may be the reason why the fix is not working on a dual processor machine. Thanks for the URLs and advice, JN -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, November 15, 1999 8:20 PM To: 'Java Apache Users' Subject: FIX: IBM JVM doesn't run, but Blackdown JVM does onsame installation ---------------------------------------------------------------- BEFORE YOU POST, search the faq at <http://java.apache.org/faq/> WHEN YOU POST, include all relevant version numbers, log files, and configuration files. Don't make us guess your problem!!! ---------------------------------------------------------------- Hi, Last night i continue to investigate the problem of the IBMJDK118 and Mandrake 6.1 integration. I've identified it is the problem of the glibc. After checking the the IBM's newsgroup I suggest in the last message, I then go to the redhat's mirror and get the lastest glibc related RPMs from Redhat 6.1, they are : glibc-2.1.2-11.i386.rpm glibc-devel-2.1.2-11.i386.rpm glibc-profile-2.1.2-11.i386.rpm and upgrade from glibc 2.1.1 to 2.1.2 on my MDK 6.1. AND IT WORKS!!! Now i can run Apache w/Jserv 1.1b3 and Tomcat perfect, without any crash. While I have the Redhat's glibc installed and have my server running smoothly, I found that Mandrake have built it's own glibc-2.1.2 under MandrakeCooker! You can find it in one of the mirrors: ftp://rpmfind.net/linux/MandrakeCooker/cooker/Mandrake/RPMS/ and get: glibc-2.1.2-8mdk.i586.rpm glibc-devel-2.1.2-8mdk.i586.rpm glibc-profile-2.1.2-8mdk.i586.rpm I've also tried it, it also works! Of course, i use the Mandrake's glibc packages instead of Redhat's from now on, as Mandrake claims that its packages are optimized for pentinum chips. JN: I suggest you to upgrade the glibc rather than just replace the libpthread, it is quite risky. Have fun!! (^_^) Punky Tse -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jon B. Norris Sent: Tuesday, November 16, 1999 1:36 AM To: Java Apache Users Cc: Dean Moses; Seth Ladygo; Danny Stewart; Brian Scott; Brian Slesinsky Subject: RE: Subject: RE: IBM JVM doesn't run, but Blackdown JVM does ons ame installation ---------------------------------------------------------------- BEFORE YOU POST, search the faq at <http://java.apache.org/faq/> WHEN YOU POST, include all relevant version numbers, log files, and configuration files. Don't make us guess your problem!!! ---------------------------------------------------------------- Hi: RE: The IBM JDK118, MDK 6.1 (marketing release number:), JSDK2.0, MDKApache_x.x.9, and Glib(s)......etc.:( Hi: esp. Mark and Mr..Punky(;) Hi: In general....and apologies on my lengthy 1st. message, but detail is sometimes the key to getting good suggestions via proxy. Thanks for the replies, nice to know that a couple of other individuals have an interest in solving what seems to be a sticky BigBlueJava-possibly-Glibc-maybe-BluishJVM conundrum. I can definitely see the Glibc connection (no pun intended), but what bothers me is the fact that most system libraries (.....most being on the side of more) have a reference to older lib forms & functions (e.g.. strings -v /lib/* | more .... will result in a listing that shows the greater % of libs referring back 2.1.1-->2.1-->2.0-->). My understating of GNU/Linux c/c++ libraries is getting better all the time, but I am not an expert in the area by any means...soooo, I will post the issues to IBM's Java site and Linux gen community pages, to see if there are any items I may have overlooked (if I find anything relevant to the current integration problem, I will post it here on this thread:) Also, I have looked at the bug reports for IBM (re: IBMJDK118) and do see a quite a few areas where the bugs could contribute to what we are seeing here, but I have not subscribed to newsgroups for IBM (soon to change). In-the-manyshadesofgrey-conclusion-forthis(sic)reply........I would agree with the Glibc problem, would also like to know how the supplied classes(methods...etc) utilize native Linux system calls to open/close and monitor sockets....as we could have a combination of problems.....which do seem to point to something which plagues the ongoing genesis of branded JVM(s).......sacrifice of flexibility/portability for speed. More later, JN -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED] -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
