Diablo 1.5 SIGBUS

[Greg Lewis]

On Wed, May 03, 2006 at 03:54:40PM +0100, Richard Cooper wrote:
> I'm running tomcat on FreeBSD 6.1-RC with diablo -1.5.0.06.00 (this is 
> the current port as of today). This is on an amd64 X2 with SMP running.
> 
> I am getting the SIGBUS error that was mentioned back in April -
> 
> > I was able to catch the SIGBUS in gdb once so far on a remote
> > multiprocessor system. There was some evidence that the use of
> > of the jvm argument -XX:+UseMembar will help correct the problem.
> > I wasn't readily able to reproduce the problem so I'm not sure
> > yet if this is the proper solution. Can those of you who are
> > getting the SIGBUS try this and see if it improves things?
> 
> It seems the problem has some kind of temporary fix at least. _My_ 
> problem is I am no developer (bash and cgi are about my limits - I'm 
> setting up a load test machine for tomcat developers). So if someone 
> could be kind enough to  give me a quick step by step on how to execute 
> this solution I would be eternally grateful. I've looked in 
> /usr/local/bin/javavm, as it was suggested adding the above fix there, 
> but I wouldn't even know where to start.

You did say bash was within your limits, and javavm is a shell script... :)

A quick and dirty hack would involve something like this.  Every where
it invokes tryJavaCommand (there are about 6 instances) you need to add
-XX:+UseMembar.  That is, the lines look something like:

tryJavaCommand "PATH_TO_JAVA_COMMAND" "${@}"

make them

tryJavaCommand "PATH_TO_JAVA_COMMAND" -XX:+UseMembar "${@}"

You don't really need to change all six instances, but which to change
depends on your usage pattern, so changing all 6 is safe.

If that works you owe me two beers... ;)
-- 
Greg Lewis                          Email   : glewis at eyesbeyond.com
Eyes Beyond                         Web     : http://www.eyesbeyond.com
Information Technology              FreeBSD : glewis at FreeBSD.org