I submitted a ticket to SuSE/Novell on the Java/Tomcat bug. I got a reply
(below) that this appears to be a problem within IBM Java for zLinux itself and
i should report it to IBM. Anyone know how or where? Do I just go through
IBMLink or is there somewhere else?
Hi Gordon,
thank you very much for the crash report.
> I am getting reports from one of my systems administrators that, within
> SLES9-SP1 for zSeries (64-bit) running under z/VM 5.1 on an IBM z800
> machine, the use of java causes Tomcat to crash or hang.
What I can see from the crash analysis is:
> SIGABRT received in gsignal at 0x200000a2a9c in /lib64/tls/libc.so.6.
> Processing terminated.
Don't get confused by the notice that it seemed to have happend in
libc.so.6, aparently gsignal() with SIGABRT as a parameter was called
with the default interrupt handler in place. As gsignal() has been
marked obsolete for ages under Linux, the application or library
using it is very unlikely some of those we have access to the source
code...
SIGABRT usually gets used to exit a program cleanly after a caught
segmentation fault (alternatively, some programs and toolkits such
as Motif use SIGBUS for this purpose)
Unfortunately, I don't see which one of the Java threads has called
this function, but all threads where doing something in libhpi.so.
Thus it is save to assume that libhpi were calling it. libhpi belongs
to Java2: /usr/lib/IBMJava2-1.4.2/jre/bin/libhpi.so
Thus it is safe to assume that this is an IBM Java bug, you might
wish to ask IBM for further analysis.
Best regards,
Joerg Reuter
Novell Technical Services
"A statesman is a dead politician. Lord knows we need more statesmen!"
--Berkeley Breathed
Gordon Wolfe, Ph.D. Boeing Shared Services Group
Enterprise Servers VM Technical Services 425-865-5940
> ----------
> From: Istvan Nemeth
> Reply To: Linux on 390 Port
> Sent: Thursday, June 16, 2005 10:50 PM
> To: [email protected]
> Subject: Re: SLES 9 SP 1 - Tomcat & IBM Java - failure.
>
> I don't have your previous e-mails.. but:
>
> I have installed IBMJava2-SDK-142 (downloaded from some IBM website) and I
> have working jakarta-tomcat-4.1.31 too. I had to install libstdc++5. You
> should try simply run java, and other binaries to see if they have all
> needed libraries. If they are not running, you can check with ldd what's
> missing. Sometimes package names and library names are not the same :(.
>
> Our developers needed j2ee so we put j2ee.jar, tools.jar etc.. into
> $JAVA_HOME/j2sdk1.4.2/lib, so we have sun j2ee..
>
> István
>
>
> Linux on 390 Port <[email protected]> írta 2005.06.16 22:36:48
> idopontban:
>
> > Carolus Walraven wrote:
> > > Your running the 64 JVM (that isn't support in WAS 6.0.1 :) .. try the
> > > 31bit JVM
> >
> > Okay, pulled out the 64bit JRE and SDK, installed the 31 bit versions.
> > Same error, except this time it was /lib instead of /lib64 in the path
> > to libc shown in the error.
> >
> > For kicks, I even tried SLES 8's 1.4.1 31 bit, that was worse, it just
> > locked up tomcat solid.
> >
> > I've requested Gordon Wolfe send in a bug report to SuSE at this point.
> > Any other pointers would be appreciated.
> >
> > Thanks
> > *Brandon Darbro
> >
> > ----------------------------------------------------------------------
> > For LINUX-390 subscribe / signoff / archive access instructions,
> > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> > http://www.marist.edu/htbin/wlvindex?LINUX-390
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
