Any time you see a bus error, it's a problem with your VM.  You should
send mail to the folks who wrote it, as they'd probably like to know about
this -- there is no time at which a VM should ever generate SIGBUS.  No
Java code should ever cause that to occur.

The most likely cause for this bug is in how the VM loads classes into
memory (it may page them off the disk when needed, which means changing
the ones on the disk would produce an error like this) -- but the end
result is definitely a bug in their JVM.

When configured to do so, JServ uses class reloading (if you mean you
changed a class which is defined in a repository, but not in the
classpath) -- it's remotely possible that this is the behavior which
triggers the bug.  You might mention it in your bug report.

hth --

Ed

On Wed, 26 May 1999, Michael Lee wrote:

> hi all
> 
> I just wondering why does the servlet cause a  bus error with message
> below...
> 
> SIGBUS    10* bus error
> si_signo [10]: SIGBUS 10* bus error
> 
> I belief this occurs when I try to replace the class files of the
> servlet without restarting the server..
> 
> Why does this happen ? Is this an expected behaviour?
> 
> Thanks in Advance
> 
> mike
> 
> 
> 
> 
> 
> -- --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> READ THE FAQ!!!!     <http://java.apache.org/faq/>
> Archives and Other:  <http://java.apache.org/main/mail.html/>
> Problems?:           [EMAIL PROTECTED]
> 



-- --------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
READ THE FAQ!!!!     <http://java.apache.org/faq/>
Archives and Other:  <http://java.apache.org/main/mail.html/>
Problems?:           [EMAIL PROTECTED]

Reply via email to