You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by GOMEZ Henri <hg...@slib.fr> on 2000/09/06 12:10:22 UTC
Info : JDK 1.3.0 update for Linux
There is also an update for 1.3.0 Linux JDK (August 14th, 2000)
=> here is the fixes from 1.3.0 prev version
File fixesd.lst for cx130
Automatic generation started at Sunday, August 13, 2000 10:32:17 PM
+--------------+------+-------+-+--------+----------------------------------
----------+
|Build |Defect|APAR |P|SunBugId|Description
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|GA Release cx130-20000623
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000706|12728 | |d|N/A |ICAT: Fatal Error in
threadControl.c - thre |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000706|13323 | |c|N/A |Occasional hang on SMP
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000708|13097 | |c|N/A |Interoperability problems due to
codeset |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000712|12493 | |l|N/A |equal on Any containing
wstring/wchar throw |
+--------------+------+-------+-+--------+----------------------------------
----------+
|au130-20000713|13015 | |d|N/A |Only 1st -D option recognized in
PluginCont |
+--------------+------+-------+-+--------+----------------------------------
----------+
|au130-20000713|13016 | |d|N/A |Java p-lugin not honoring
JAVA_PLUGIN_TRACE |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000718|13444 | |d|N/A |read_value(Helper) does not handle
omitted |
+--------------+------+-------+-+--------+----------------------------------
----------+
|au130-20000730|14149 | |d|N/A |plugin: possible trap in user pref
parsing |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hx130-20000802|14495 | |d|N/A |Incorrect parms on xeRunJavaMethod
call for |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000804|14150 | |l|N/A |Streaming performance degradation
from 118 |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000804|14174 | |l|N/A |OmniORB/Names initial GIOP level
problem & |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000804|14566 | |d|N/A |Error handling for value_tag
required in CD |
+--------------+------+-------+-+--------+----------------------------------
----------+
|hx130-20000805|12912 | |d|N/A |ICAT: JVM hangs on resume
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000805|13614 | |c|N/A |Swing Problems with JCChart
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|hx130-20000810|13509 | |d|N/A |Memory leak in ProcHelper.java
|
+--------------+------+-------+-+--------+----------------------------------
----------+
|hs130-20000814|13997 | |c|N/A |Beta: Application JNI Use of LE
PIPI result |
+--------------+------+-------+-+--------+----------------------------------
----------+
Automatic generation completed successfully Sunday, August 13, 2000 10:32:54
PM
-
Unix is like a 'hogan' -- no Gates, no Windows, and an Apache inside.
-----Original Message-----
From: GOMEZ Henri [mailto:hgomez@slib.fr]
Sent: Wednesday, September 06, 2000 7:45 AM
To: tomcat-user@jakarta.apache.org
Subject: RE: SIGSEGV 11 (*) segmentation violation
Just for information when I do java -version I got :
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000623 (JIT enabled:
jitc))
Seems you have the pre version of IBM 1.3 SDK.
PS: My version was installed from RPMs
-
Unix is like a 'hogan' -- no Gates, no Windows, and an Apache inside.
-----Original Message-----
From: mark@smartmonsters.com [mailto:mark@smartmonsters.com]
Sent: Wednesday, September 06, 2000 12:12 AM
To: tomcat-user@jakarta.apache.org
Subject: Re: SIGSEGV 11 (*) segmentation violation
My own experience with these SIGSEGV11 crashes tends to point away from the
VM as cause. Some notes:
1. In my experience, IBM's 1.3 VM has been quite stable on RedHat. I have a
complex server application which runs for weeks at a time with no errors.
(Current uptime: 25 days, 17 hours, 3 minutes -- just checked.) Whereas I
do occasionally experience SIGSEGV 11 crashes running Tomcat on the same
machine. While this doesn't categorically rule out the VM as the cause, it
does seem to point more toward Tomcat than the VM.
2. For me the SIGSEGV 11 crashes didn't happen with Tomcat 3.1. Only
started when I upgraded to 3.2b2. Same VM, it was the Tomcat version which
changed.
3. But, it's not clear that the Tomcat upgrade is the cause, since there was
a lot of JSP development happening on the same machine at the same time. In
particular, my project began implementing Session management around the
time of the Tomcat upgrade. It would be possible to rule out Tomcat version
change as the cause by experimentally re-deploying my app-in-progress on
Tomcat 3.1; I may do this while tracking down this problem.
Again, this doesn't rule out the VM, just tends to point in a different
direction. I suspect an instability somewhere in the Tomcat implementation,
perhaps something specific to Session management. Will have to trace this
down before my app moves toward production-readiness. Will post any new
info as it turns up; meanwhile many thanks if you'll do the same.
Hope this helps,
--Mark
Thomas Hagedorn <Th...@alcatel.de>
Sent by: tomcat-user-return-10461-mark=smartmonsters.com@jakarta.apache.org
09/05/2000 05:13 AM
Please respond to tomcat-user
To: tomcat-user@jakarta.apache.org, sabourdin@cybericare.com
cc:
Subject: Re: SIGSEGV 11 (*) segmentation violation
Hi,
I guess a problem with the IBM JVM in 1.3. even if it is declared as
final release, SUN JDK1.3 which is declared beta (for Linux) is still
more stable.
I'm working on RH6.2 and I had a lot of problems with IBM-JDK1.3 and
tomcat and jBoss and TogetherJ and all troubles dissappeared when
switching to SUN JDK1.3beta.
hope this helps
best regards
tom
Am Die, 05 Sep 2000 schrieben Sie:
> hello, I had tiwce this error in my terminal :
> "SIGSEGV 11 (*) segmentation violation
> stackpointer=0xbe5c0cb0 "
> Can anyone explain my what type of error could it be,
> or where to look at.
> I use:
>
> Red Hat Linux release 6.1 (Cartman)
> Kernel 2.2.12-20
> --
> java version "1.3.0"
> Classic VM (J2RE 1.3.0 IBM build cxdev-20000502 (JIT
> enabled: jitc))
> --
> tomcat 3.1
> (Is there any official stable version of tomcat 3.2?)
>
> your sincerely,
>
> thanks.
>
> =====
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com/
Re: Info : JDK 1.3.0 update for Linux
Posted by Chong Yu Meng <cy...@cyberway.com.sg>.
Hello Henri :
Do you know if the new update supports SMP ? I heard on the newsgroup that
the JDK doesn't support SMP.
Regards,
Chong Yu Meng
----- Original Message -----
From: "GOMEZ Henri" <hg...@slib.fr>
To: <to...@jakarta.apache.org>
Sent: Wednesday, September 06, 2000 6:10 PM
Subject: Info : JDK 1.3.0 update for Linux
> There is also an update for 1.3.0 Linux JDK (August 14th, 2000)
>
> => here is the fixes from 1.3.0 prev version
>
> File fixesd.lst for cx130
>
> Automatic generation started at Sunday, August 13, 2000 10:32:17 PM
>
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |Build |Defect|APAR |P|SunBugId|Description
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |GA Release cx130-20000623
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000706|12728 | |d|N/A |ICAT: Fatal Error in
> threadControl.c - thre |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000706|13323 | |c|N/A |Occasional hang on SMP
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000708|13097 | |c|N/A |Interoperability problems due to
> codeset |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000712|12493 | |l|N/A |equal on Any containing
> wstring/wchar throw |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |au130-20000713|13015 | |d|N/A |Only 1st -D option recognized in
> PluginCont |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |au130-20000713|13016 | |d|N/A |Java p-lugin not honoring
> JAVA_PLUGIN_TRACE |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000718|13444 | |d|N/A |read_value(Helper) does not
handle
> omitted |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |au130-20000730|14149 | |d|N/A |plugin: possible trap in user
pref
> parsing |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hx130-20000802|14495 | |d|N/A |Incorrect parms on
xeRunJavaMethod
> call for |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000804|14150 | |l|N/A |Streaming performance
degradation
> from 118 |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000804|14174 | |l|N/A |OmniORB/Names initial GIOP level
> problem & |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000804|14566 | |d|N/A |Error handling for value_tag
> required in CD |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hx130-20000805|12912 | |d|N/A |ICAT: JVM hangs on resume
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000805|13614 | |c|N/A |Swing Problems with JCChart
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hx130-20000810|13509 | |d|N/A |Memory leak in ProcHelper.java
> |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
> |hs130-20000814|13997 | |c|N/A |Beta: Application JNI Use of LE
> PIPI result |
>
+--------------+------+-------+-+--------+----------------------------------
> ----------+
>
> Automatic generation completed successfully Sunday, August 13, 2000
10:32:54
> PM
>
>
>
> -
> Unix is like a 'hogan' -- no Gates, no Windows, and an Apache inside.
> -----Original Message-----
> From: GOMEZ Henri [mailto:hgomez@slib.fr]
> Sent: Wednesday, September 06, 2000 7:45 AM
> To: tomcat-user@jakarta.apache.org
> Subject: RE: SIGSEGV 11 (*) segmentation violation
>
>
> Just for information when I do java -version I got :
>
> java version "1.3.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
> Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20000623 (JIT enabled:
> jitc))
>
> Seems you have the pre version of IBM 1.3 SDK.
>
> PS: My version was installed from RPMs
>
> -
> Unix is like a 'hogan' -- no Gates, no Windows, and an Apache inside.
> -----Original Message-----
> From: mark@smartmonsters.com [mailto:mark@smartmonsters.com]
> Sent: Wednesday, September 06, 2000 12:12 AM
> To: tomcat-user@jakarta.apache.org
> Subject: Re: SIGSEGV 11 (*) segmentation violation
>
>
>
> My own experience with these SIGSEGV11 crashes tends to point away from
the
> VM as cause. Some notes:
>
> 1. In my experience, IBM's 1.3 VM has been quite stable on RedHat. I have
a
> complex server application which runs for weeks at a time with no errors.
> (Current uptime: 25 days, 17 hours, 3 minutes -- just checked.) Whereas I
> do occasionally experience SIGSEGV 11 crashes running Tomcat on the same
> machine. While this doesn't categorically rule out the VM as the cause,
it
> does seem to point more toward Tomcat than the VM.
>
> 2. For me the SIGSEGV 11 crashes didn't happen with Tomcat 3.1. Only
> started when I upgraded to 3.2b2. Same VM, it was the Tomcat version
which
> changed.
>
> 3. But, it's not clear that the Tomcat upgrade is the cause, since there
was
> a lot of JSP development happening on the same machine at the same time.
In
> particular, my project began implementing Session management around the
> time of the Tomcat upgrade. It would be possible to rule out Tomcat
version
> change as the cause by experimentally re-deploying my app-in-progress on
> Tomcat 3.1; I may do this while tracking down this problem.
>
> Again, this doesn't rule out the VM, just tends to point in a different
> direction. I suspect an instability somewhere in the Tomcat
implementation,
> perhaps something specific to Session management. Will have to trace this
> down before my app moves toward production-readiness. Will post any new
> info as it turns up; meanwhile many thanks if you'll do the same.
>
> Hope this helps,
>
> --Mark
>
>
>
> Thomas Hagedorn <Th...@alcatel.de>
> Sent by:
tomcat-user-return-10461-mark=smartmonsters.com@jakarta.apache.org
> 09/05/2000 05:13 AM
> Please respond to tomcat-user
>
> To: tomcat-user@jakarta.apache.org,
sabourdin@cybericare.com
> cc:
> Subject: Re: SIGSEGV 11 (*) segmentation violation
>
>
> Hi,
>
> I guess a problem with the IBM JVM in 1.3. even if it is declared as
> final release, SUN JDK1.3 which is declared beta (for Linux) is still
> more stable.
> I'm working on RH6.2 and I had a lot of problems with IBM-JDK1.3 and
> tomcat and jBoss and TogetherJ and all troubles dissappeared when
> switching to SUN JDK1.3beta.
>
> hope this helps
>
> best regards
> tom
>
> Am Die, 05 Sep 2000 schrieben Sie:
> > hello, I had tiwce this error in my terminal :
> > "SIGSEGV 11 (*) segmentation violation
> > stackpointer=0xbe5c0cb0 "
> > Can anyone explain my what type of error could it be,
> > or where to look at.
> > I use:
> >
> > Red Hat Linux release 6.1 (Cartman)
> > Kernel 2.2.12-20
> > --
> > java version "1.3.0"
> > Classic VM (J2RE 1.3.0 IBM build cxdev-20000502 (JIT
> > enabled: jitc))
> > --
> > tomcat 3.1
> > (Is there any official stable version of tomcat 3.2?)
> >
> > your sincerely,
> >
> > thanks.
> >
> > =====
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Mail - Free email you can access from anywhere!
> > http://mail.yahoo.com/