RE: Segmentation Violation with HttpCoyoteConnector
Thanks. The stacksize was already limited with ulimit -s 2048. I think that I have already found the solution. It seems that there was a bug in the system libraries and there are some rpms to be updated. - Original Message - From: pero <[EMAIL PROTECTED]> To: 'Tomcat Users List' <[EMAIL PROTECTED]> Sent: Thursday, February 27, 2003 10:10 PM Subject: RE: Segmentation Violation with HttpCoyoteConnector > Hi, > > this is a JVM issue. Did you limit the stacksize with > ulimit -s 2048 (bash)? That helps in most cases. > > Peter > > > -Original Message- > > From: Juan [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 27, 2003 6:16 PM > > To: [EMAIL PROTECTED] > > Subject: Segmentation Violation with HttpCoyoteConnector > > > > > > Hello > > > > I have a Tomcat 4.1.18 standalone server installed on Red Hat > > Linux 7.3, using the Sun JVM 1.3.1_03, green threads, standalone. > > > > After having some problems with Http11Connector, I activated > > Coyote about 10 days ago. In these days JVM has crashed, > > obtaining a Segmentation Violation message, about 5-6 times. > > The CPU maintained mostly idle and there was still enough > > free memory for the JVM. It happens normally after working > > between 1 and 2 days, it has not been in the moments with > > more work load, and some times it has been preceded by some > > incorrect requests (extrange characters appeared in the log) > > from the same IP, at the same time of the day (I suspect that > > could be a user with a browser whose JVM generates bad requests) > > > > Have anybody reported such problem? Any solution suggested? > > > > Juan Zubieta > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Segmentation Violation with HttpCoyoteConnector
Hi, this is a JVM issue. Did you limit the stacksize with ulimit -s 2048 (bash)? That helps in most cases. Peter > -Original Message- > From: Juan [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 6:16 PM > To: [EMAIL PROTECTED] > Subject: Segmentation Violation with HttpCoyoteConnector > > > Hello > > I have a Tomcat 4.1.18 standalone server installed on Red Hat > Linux 7.3, using the Sun JVM 1.3.1_03, green threads, standalone. > > After having some problems with Http11Connector, I activated > Coyote about 10 days ago. In these days JVM has crashed, > obtaining a Segmentation Violation message, about 5-6 times. > The CPU maintained mostly idle and there was still enough > free memory for the JVM. It happens normally after working > between 1 and 2 days, it has not been in the moments with > more work load, and some times it has been preceded by some > incorrect requests (extrange characters appeared in the log) > from the same IP, at the same time of the day (I suspect that > could be a user with a browser whose JVM generates bad requests) > > Have anybody reported such problem? Any solution suggested? > > Juan Zubieta > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Segmentation Violation with HttpCoyoteConnector
Hello I have a Tomcat 4.1.18 standalone server installed on Red Hat Linux 7.3, using the Sun JVM 1.3.1_03, green threads, standalone. After having some problems with Http11Connector, I activated Coyote about 10 days ago. In these days JVM has crashed, obtaining a Segmentation Violation message, about 5-6 times. The CPU maintained mostly idle and there was still enough free memory for the JVM. It happens normally after working between 1 and 2 days, it has not been in the moments with more work load, and some times it has been preceded by some incorrect requests (extrange characters appeared in the log) from the same IP, at the same time of the day (I suspect that could be a user with a browser whose JVM generates bad requests) Have anybody reported such problem? Any solution suggested? Juan Zubieta - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Segmentation Error SIGSEGV 11 * Segmentation Violation
> HI, I am using Red Hat 7.2, Tomcat 3.2.3, MySQL and JDK 1.2.2. > I am getting the error: "Segmentation Error SIGSEGV 11 * > Segmentation Violation" > Can u pls provide some solution for this? No, please take a few minutes to formulate your problem more precisely. -- --Jhair -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Segmentation Error SIGSEGV 11 * Segmentation Violation
HI, I am using Red Hat 7.2, Tomcat 3.2.3, MySQL and JDK 1.2.2. I am getting the error: "Segmentation Error SIGSEGV 11 * Segmentation Violation" Can u pls provide some solution for this? Thanks in advance... Koti -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: SIGSEGV 11* segmentation violation
which version of the C++ libraries do you have? freebsd 4.5 is the newest-greatest, right? (forgive me, been a while) On 5/23/02 1:33 AM, "Joseph G. Mercado" <[EMAIL PROTECTED]> wrote: > Hi, > Im trying to run tomcat 3.3 on a freebsd 4.5 box with jdk1.2.2 running. > When i run sh tomcat.shs start i get SIGSEGV 11* segmentation violation. > WHat do u thinks its causing this i read thru the archive email regarding > this stuff i followed thier siggestion on double checking my PATH and > CLASSPATH. What do u think?Did i miss something along the way please > helpThank you in advance > > jmer > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
SIGSEGV 11* segmentation violation
Hi, Im trying to run tomcat 3.3 on a freebsd 4.5 box with jdk1.2.2 running. When i run sh tomcat.shs start i get SIGSEGV 11* segmentation violation. WHat do u thinks its causing this i read thru the archive email regarding this stuff i followed thier siggestion on double checking my PATH and CLASSPATH. What do u think?Did i miss something along the way please helpThank you in advance jmer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: Segmentation violation
"Harippriya Sivapatham" <[EMAIL PROTECTED]> writes: > Hi there, > I am getting a segmentation violation in tomcat (the full error message > is added to the end of this mail). Tomcat stops when this error occurs. I am > getting this error when i call a particular servlet. The error message > displays a lot about Threads. So, i just want to note that the servlet that > causes this problem does not use any threads. > > I would really appreciate any help with this. > > Thanks a lot. > Harippriya > > > Here is error message... > > SIGSEGV 11 segmentation violation > si_signo [11]: SEGV > si_errno [0]: > si_code [1]: SEGV_MAPERR [addr: 0x45a0920] In most cases there is some problem with your hardware (overclocked cpu/damaged ram/etc). -- ICQ #83060237 MAN-UANIC NIK6-RIPE
Re: Segmentation violation
Harippriya Sivapatham at [EMAIL PROTECTED] wrote: > > Hi there, > I am getting a segmentation violation in tomcat (the full error message > is added to the end of this mail). Tomcat stops when this error occurs. I am > getting this error when i call a particular servlet. The error message > displays a lot about Threads. So, i just want to note that the servlet that > causes this problem does not use any threads. > > I would really appreciate any help with this. > > Thanks a lot. > Harippriya > > > Here is error message... > > SIGSEGV 11 segmentation violation > si_signo [11]: SEGV > si_errno [0]: > si_code [1]: SEGV_MAPERR [addr: 0x45a0920] What version of Tomcat are you using? What version of Java Virtual Machine? What operating system? (Kinda hard to tell without those informations) :) Pier
RE: segmentation violation in Java
The point is that there can only be two possible causes for a "segmentation violation": * the jvm has a bug,or * JNI is being used, and is calling buggy native code libraries There are no alternative reasons! By definition, java **cannot** cause segmentation violations, no matter how buggy or badly written. Ok, there are certain code constructs that could trigger the jvm crash, and programs that don't use those features are therefore not going to encounter the crash, but it is almost impossible to deduce, from a jvm crash, what java code caused the problem. I think that trying to randomly modify a java program that causes a jvm to crash in order to find some variant which does *not* cause the jvm to crash is really not the best way of solving the problem... far better to move to another jvm. I suggest that if a JVM crash happens for one person, then every other person using the same JVM version from the same vendor on the same platform should be very worried; there is no guaruntee at all that it won't happen to other programs Having said that, I happen to be using Sun's jvm 1.2.2_04 on solaris, and haven't seen any segmentation violations. If I ever do get one, I will be upgrading to 1.3, rather than trying to tweak my code, I can promise you! Cheers, Simon > -Original Message- > From: Khaled Ben Mohamed [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, January 11, 2001 6:26 PM > To: '[EMAIL PROTECTED]' > Subject: TR: > > I use the same jvm so i don't understand ? > > > > -Message d'origine- > > De : Michael Kuz [mailto:[EMAIL PROTECTED]] > > Envoyé : jeudi 11 janvier 2001 18:27 > > À : 'Khaled Ben Mohamed' > > Objet : RE: > > > > > I'm using Suns 1.2.2 for Linux > > > [mkuz@mkuz ~]$ java -version > > java version "1.2.2" > > Classic VM (build 1.2.2_006, green threads, nojit) > > > > > -Original Message- > > From: Khaled Ben Mohamed [ <mailto:[EMAIL PROTECTED]>] > > Sent: Thursday, January 11, 2001 10:17 AM > > To: '[EMAIL PROTECTED]' > > Subject: > > > > > > >>-Original Message- > > >>From: Kitching Simon [ <mailto:[EMAIL PROTECTED]>] > > >>Sent: Thursday, January 11, 2001 9:50 AM > > >>To: '[EMAIL PROTECTED]' > > >>Subject: RE: TOMCAT PROBLEM of disconection > > > > > > > > >>The problem is that the java virtual machine you are using > > >>has a bug. There really isn't any work-around for this sort > > >>of problem - if the jvm is buggy, the best thing is to change > > >>jm. > > > > > > >>JVM version 1.3 is available for just about every platform > > >>now, I suggest you download & install it. > > > > >Isn't 1.3 still 'buggy' on Linux? > > > > What JVM do you think i have to use ? > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
