Bus error

[Alvaro Martinez Reol <am...@tid.es>]

'¯z¼›¡Üˆ…«ÞjÇ«Š‹¬¦º•éˆš¯Šx–‹h~šènW¦³b´–¤j»ZN‰œjÖ§t‹!¢é]r§é²¦V­~Šæ‰ò&ž‹ZnW­¢Ê%½ëazdáy:&q«\­«!zË.uק—+(™ëb™ëÒ+yÇ¢½ëaŠÇ«®ŠæzÆ àn°J뢻"²('£]
ºÁ+®Šì‰ê랍®º+ÒȜ¡×µD€
5§]¯Lzk­{ë¯lµ§$¦ˆ§µê

Re: Bus error revisited - connected to "reloadable"?

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Mike Bremford wrote:

>  Hi guys...I knew I'd seen it before... I've just got this as well,
> with a similar setup (Alvaro was running Solaris 2.7 with Tomcat 3.1,
> but I'm running 3.2b2)* Solaris 2.7 with the default Java 1.2 setup
> (Solaris VM (build Solaris_JDK_1.2.1_02a, native threads, sunwjit)*
> Tomcat 3.2b2* Apache 1.3.12 + mod_jserv, both compiled from source.
> Cheers... Mike

Bus errors and other JVM crashes *always* indicate a bug in the
underlying JVM -- there is no legitimate way for any pure-Java program
(as Tomcat is) to cause them.

In this particular case, you should update to at least JDK 1.2.2_05.

Craig McClanahan

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Bus error revisited - connected to "reloadable"?

[Mike Bremford <mi...@paperx.com>]

Hi guys...

I knew I'd seen it before... I've just got this as well, with a similar
setup (Alvaro was running Solaris 2.7 with Tomcat 3.1, but I'm running
3.2b2)

* Solaris 2.7 with the default Java 1.2 setup (Solaris VM (build
Solaris_JDK_1.2.1_02a, native threads, sunwjit)
* Tomcat 3.2b2
* Apache 1.3.12 + mod_jserv, both compiled from source.

The funny thing is that tomcat has been running fine for about 5 weeks
without dropping once, except when I bounced it manually to reload a bean. I
got fed up with doing this, so I set "reloadable=true" on my context.

2 minutes and 4 jsps later, it crashed! I didn't catch the error - nothing
in the logs, no processs running - but quickly backed out the "reloadable"
change and restarted tomcat. Two minutes later, it crashed *again* with this
result:

Bus Error
    si_signo [10]: Bus Error
    si_errno [0]: Error 0
    si_code [1]: BUS_ADRALN [addr: 0x8009]
        stackpointer=FA45FF10
*** panic: JIT signal handler did not take the signal
Test for suspension on thread: 40 in process 11463 ...


What does this tell me? Damned if I know, but I'm steering well clear of the
"reloadable" flag, and I'm unsure what was going on with the second crash
(as I'd already backed out the change). I seem to remember that the
"reloadable" aspect of tomcat is still officially flakey - is this expected
behaviour? What is the accepted wisdom on using it in a production
environment?


Cheers... Mike
  -----Original Message-----
  From: amarreo [mailto:amarreo]On Behalf Of Alvaro Martinez Reol
  Sent: 09 August 2000 08:30
  To: tomcat-user@jakarta.apache.org
  Subject: Bus error


  Hi everybody!
  I have a serious problem! I'm having a lot of problems whit Jakarta-Tomcat
and I should change my platform if I'm not able to solve them...

  The Tomcat "crashes" suddenly sometimes and I receive this error mesagge:


  Bus Error
      si_signo [10]: Bus Error
      si_errno [0]: Error 0
      si_code [1]: BUS_ADRALN [addr: 0x6a617669]

          stackpointer=F8DD00D8

  *** panic: JIT signal handler did not take the signal

  Test for suspension on thread: 689 in process 9081 ...


[sgsatip.jsp:typ=foto]ctx=satipextension=9315,satiph323id=pabxip_sc1,satipty
  pe=u
  ser
  Bus Error
      si_signo [10]: Bus Error
      si_errno [0]: Error 0
      si_code [1]: BUS_ADRALN [addr: 0x84042192]

          stackpointer=FA73FEE0

  *** panic: JIT signal handler did not take the signal

  Test for suspension on thread: 354 in process 9299 ...

  *con apache
  Bus Error
      si_signo [10]: Bus Error
      si_errno [0]: Error 0
      si_code [1]: BUS_ADRALN [addr: 0x800b]

          stackpointer=FB85FEE0

  *** panic: JIT signal handler did not take the signal

  Test for suspension on thread: 259 in process 5727 ...

  HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
  java.io.IOException: Stream broken
          at java.lang.Throwable.fillInStackTrace(Native Method)
          at java.lang.Throwable.fillInStackTrace(Compiled Code)
          at java.lang.Throwable.<init>(Compiled Code)
          at java.lang.Exception.<init>(Compiled Code)
          at java.io.IOException.<init>(Compiled Code)
          at
  org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextReque
  st(Compiled Code)
          at
  org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processCon
  nection(Compiled Code)
          at org.apache.tomcat.service.TcpConnectionThread.run(Compiled
Code)
          at java.lang.Thread.run(Compiled Code)



  Does anyone knows where is the problem and how can I solve it? Somebody
has had the same problem?

  THANKS

  Alvaro M. R.