On Wednesday 03 December 2003 07:39, Adrian Brock wrote: > On Tue, 2003-12-02 at 19:11, Rod Macpherson wrote: > > Segmentation Violation. Unless you are making JNI calls there is nothing > > application code can do to generate this signal. > > Except allocate all the memory and the VM doesn't trap the out of memory > situation.
I get these (and signal 10, buserror) with both the linux 1.3.x/1.4.x and Solaris VMs. It doesn't happen very often but often enough to worry me about the stability of the JVM in a 24x7 production environment. Getting the patch levels correct on Solaris can be a bit of a pain, there is usually a list included in the JVM release notes but they are not always available if they have been superceded, you have to get the latter one. This in itself can be a problem as sun are not unknown to have a regression of a problem, particularly in the threading area. Linux is a different but similar problem, the recent glibc changes have introduced some problems as well. I run mostly Mandrake 9.(0,1,2) based systems but often with a redhat (2.4.7-10) kernel due to our usage of clearcase. I've never been able to find a commonality between the crashes and have never been able to reproduce one at will so it is very difficult to report the error. Are similar problems seen on Windows JDKs? (and which versions of Windows?) We now have systems in production on Solaris 8 (although with very light usage for the moment) and are going to be watching the stability very closely. thanks, brian wallis... ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
