----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Well, it works! I have been fighting with getting Apache_x.9, MDK6.1,
IBMJDK118, ApacheJSERV_b3, and JDSK2.0 to produce a working
environment for quite some time, with no success. Thanks to a great
suggestion and Jeff Crowder (see below) the problem with IBMJDK118/Mandrake
6.1 seems to be solved! I implement the fix this afternoon, and have had no
errors or failures of the Servlet Engine. Looks like the current release of
Glibc from Mandrake has hacked/trimmed down c-libraries that make it
difficult to integrate older JVMs into the new framework! Ugh....:( I will
post the results of a source code & install diff when I get a chance, if
anyone is interested. Would be interesting to know which system
functions/calls are being used, that Mandrake has decided to remove!
See below for details on the fix, but it basically boils down to this....
1). Find a working installation of Red Hat 6.0 and ftp (get)
/lib/libpthread.so.8 to your local (MDK6.1) machine.
1a). Or....ftp RH6.0_RPM glibc-2.1.1-6.i386.rpm from maybe....
ftp://ftp.cdrom.com/pub/linux/redhat/old-releases/redhat-6.0/i386/RedHat/RPM
S/ , and install it using the prefix options (e.g. rpm -ivh --prefix
/<my_dump_dir> --relocate
/<dir_wherever_I_keep_my_RPMs>/glibc-2.1.1-6.i386.rpm
........(WARNING....always use the --test option first to make sure it won't
override the prefix option, especially when it comes to files that the
kernel depends upon:).
2). Copy /lib/libpthread.so.8 to /lib/libpthread.so.8_old, and copy the
RH6.0 libpthread.so.8 to /lib.
3). Run the command...... #ldconfig -v | grep libpthread
4). You should see an (updated) message along with the logical link to
libpthread.so.0
5). If things don't pan out on the update, check /etc/ld.so.config and make
sure there is an entry to /lib
6). Now the library cache (/etc/lib.so.cache) should be updated with the new
lib info.
7). I recompiled Jserv to be on the safe side, although I believe it just
points to the library (strings -v /etc/httpd/modules/mod_jserv.so)
8). Voilla......the problem goes away.....THANK YOU JEFF!
-JN
-----Original Message-----
From: Jon B. Norris [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 15, 1999 12:39 PM
To: Java Apache Users; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Subject: RE: IBM JVM doesn't run, but Blackdown JVM does on
s ame installation !!!!!!!! a possible FIX is in from the IBM-Java news
gr oup.....
Importance: High
----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Hello all.....
Quick fix..... see the excerpt that follows the "##### Message from Jeff
Crowder..." below, for a more on the problem, keep reading....:)
First, many thanks to punkytse@geocites for suggesting the IBM Newsgroup
(news://news.software.ibm.com/ibm.software.java.linux), and way thanks to
Jeff at One.Net (see below)! The following 2 part thread seems to be the
answer to the MDK6.1/IBMJDK118 integration problem. I spoke with a couple of
the best in UNIX/Java Engineering at my company, and they felt that the
thread lib could very well be the culprit of Jserv not being able to bind to
port 8007. The reasoning is, that when the JVM initializes the Servlet
engine, a separate thread is started to bind to a TCP port that the Servlet
engine will listen on (as specified in the directives for ApacheJserv). I
have not had time to implement/test this fix, but will do so today, and
report my findings. Even if this does not fix the Servlet engine
initialization problem, it does seem to indicate that the current set of
2.1.1 libs for Linux (MDK, at least.....will need to check out RH6.1) have
backwards compatibility with 2.1 libs of the 6.0 releases, but only as far
as Linux applications go. Seems that somewhere in the upgrade process,
depreciation of certain c-functions/system calls were made that are not
supported in the older IBMJDK118 java binary. After doing a strings and file
on the actual java binary, and armed with the insight about the libpthread
mentioned in the IBM newsgroup excerpt below, it would seem that the glibc
thing is where the answer lies (could this be a result of the Java1.2(2.0) .
Maybe need to install the lib packages from RH Dist Archives in a separate
directory and do a lib-by-lib comparison!!!! Ugh.
Stay Tuned....,
JN
BTY: Here is an output of the command strings and file on the "/<path to
actual java binary in native-threads>/java" binary:
>file java
ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked (uses
shared libs), not stripped
>strings java
/lib/ld-linux.so.2
__gmon_start__
libm.so.6
libpthread.so.0
libc.so.6
__finitef
__deregister_frame_info
__finite
_IO_stdin_used
__libc_start_main
__register_frame_info
__finitel
libdl.so.2
libjava.so
_DYNAMIC
_GLOBAL_OFFSET_TABLE_
java_main
_etext
_edata
__bss_start
_end
GLIBC_2.1
GLIBC_2.0
PTRh
QVhX
##### Message from Jeff Crowder of One.Net and reply thread from Brian Watt
of IBM #######################
##### The folowing excerpt was copied from the ibm.software.java.linux
newsgroup #######################
To all,
I have been using the 10/13 build of JDK118 on both RedHat 6.0 (SMP)
systems and typical Mandrake 6.1 systems with greatly varying results.
As should be expected, the tested platform (RedHat 6.0 in this case),
has performed well beyond my expectations, while the Mandrake 6.1 system
has nothing but problems running the JDK. Typically, applications
dealing with more than a couple executing threads (especially Swing)
have caused SIGSEGVs or runaway processes. The attached class is as
simple an example of this problem as can be illustrated. To make a long
story short, I grabbed libpthread.so.8 from the RedHat 6.0 box and put
it in place in Mandrake 6.1 and all previous crash scenarios immediately
dissappeared within the JDK. Use at your own risk.
Regards,
-Jeff
----------------------------------------------------------------------------
----
import java.util.*;
public class TestCase implements Runnable {
public static void main(String[] args) {
TestCase t1 = new TestCase("test1");
TestCase t2 = new TestCase("test2");
// TestCase t3 = new TestCase("test3");
// TestCase t4 = new TestCase("test4");
// TestCase t5 = new TestCase("test5");
(new Thread(t1)).start();
(new Thread(t2)).start();
// (new Thread(t3)).start();
// (new Thread(t4)).start();
// (new Thread(t5)).start();
}
protected String name;
public TestCase(String name) {
this.name = name;
System.out.println("Created " + name);
}
public void run() {
Vector list = new Vector();
System.out.println("Beginning loop in " + name);
for (int i = 0; i < 100000; i++) {
list.addElement(new Integer(i));
}
System.out.println("Loop complete in " + name);
}
}
Brian Watt <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> Jeff,
>
> Thanks for the insight. I'm wondering what Mandrake 6.0 has done to
> libpthread-0.8.so. The RedHat 6.0 lib is 235,419 bytes and the Mandrake
6.1
> lib is only 79,218. Whoa! I've tried it here, and it has helped greatly
reduce
> the SIGSEGVs (w/o JIT) and hangs (w/ JIT) on Mandrake 6.1. However, I
agree
> "Use at your own risk."
>
> Sincerely,
> Brian Watt
########################## Message and reply thread from IBM newsgroup
above ###########################
--
--------------------------------------------------------------
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]
