---------------------------------------------------------------- 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 -----Original Message----- From: Mark [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 13, 1999 9:36 AM To: [EMAIL PROTECTED] Subject: FW: Subject: RE: IBM JVM doesn't run, but Blackdown JVM does on same 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 all, I just thought I'd post a little update on this one. I noticed that someone else just posted with the same problem, so I'm not alone with this IBM 1.1.8, Mandrake (he posted that he had version 6.1, my box says 6.5, but my login prompt says 6.1...I don't know) problem. I compiled a simple echo server application that I found in a java manual which simply prints what is sent to a port, and it works fine using the Blackdown JDK on this system, but it hangs using the IBM JDK. It seems that applications that use sockets crash the IBM VM on this OS. I am now more inclined to believe that it is a problem with the glibc version, but after reading the readme file, I think it may be the opposite problem than was originally suggested, which wouldn't be good in my case. The readme file says that this VM was tested on RedHat 6.0, which has earlier glibc libraries than Mandrake 6.5, which has glibc 2.2.1. I don't think that downgrading my glibc libraries would be such a hot idea, so maybe the only solution to running this VM on a Mandrake 6.1 installation would be for IBM to compile a new version using the newer glibc. Does this sound like it may be correct? Mark -----Original Message----- From: Mark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 10, 1999 12:37 PM To: [EMAIL PROTECTED] Subject: Subject: RE: IBM JVM doesn't run, but Blackdown JVM does on same installation Thanks for the quick reply. I will try writing a simple socket listener tomorrow to see if it works. I will try to duplicate this problem on another machine with the same OS as soon as possible and try solving it there because this is a production machine and changing the glibc library may tend to break things. I examined the README file again, and in the 1.1.8 readme it simply says to use glibc 2.1 or greater. My system is running 2.1.1, and it seems to meet all of the other requirements. Mark -------------Original message-------------- >Subject: RE: IBM JVM doesn't run, but Blackdown JVM does on same installation >From: "Conrad Chan" <[EMAIL PROTECTED]> >Date: Tue, 9 Nov 1999 13:53:10 -0800 >We did have a similar problem when we switched from Blackdown to IBM JDK >with our Mandrake 6.1 a while ago. It came down to our IBM JDK did not >listen to TCP port properly. We solved our problem by using the proper >glibc library specified in the IBM JDK readme file. I will suggest to make a >simple socket listener and connector java program to see whether it works. >If not, make sure you are using the right glibc files. >Conrad -- -------------------------------------------------------------- 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]
