what version of RichFaces? are you using FF? I vaguely remember there being an issue with fileUpload in 3.2.0 and FF2 on mac. try using RichFaces 3.2.1 and FF3.
I'm on RichFaces 3.2.0.
I get the same problem with FF or Safari. It seems to be the Java instance running JBoss that crashes and not the browser.
I'll try 3.2.1 though and see if this is any different.
Upgrading to RichFaces 3.2.2 has fixed the issue.
Looks like RichFaces 3.2.0 and OS X don't play happily together.
I'm running into the same problem, but with the new version of Richfaces. I had Richfaces 3.2.0 running smoothly under JBoss 4.2.2.GA on my Mac OS X (Tiger v. 10.4.11), and when I tried upgrading to RF 3.2.1 or 3.2.2 I got the same error Dave mentioned right after a browser calls my app's context (the app that runs Richfaces). The error I get is:
Invalid memory access of location 43e83458 eip=904716f9
bin/run.sh: line 246: 3201 Segmentation fault "$JAVA" $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"
and then the server halts. I tried this with IE6, IE7, FF3, Camino, and Safari 3, with the same results. The crash happens even though my app forwards to a login page that only has an <h:form> with username and password text fields, and a <h:commandButton> to execute the login action. I tried to run Richfaces 3.2.1 and 3.2.2 also under Tomcat 6 with JBoss embedded but it crashed as well (3.2.0 works fine).
Any ideas or help is greatly appreciated. Thanks!
We had the same problems (and some other) with our Mac servers (tiger, leopard) to the extent that we've had to move most web apps to non mac servers (linux and recently windows). If that isn't an option for you, I suggest you send bug reports over and over again to Apple. I think the jvm on Apple is defect in some way.
I actually have the same stack running on Leopard with no issues and a different app with a similar stack running on another computer with the same version of Tiger as I have. I should have also mentioned that I tried different versions of Seam (2.0.0.GA, 2.0.1.GA, 2.0.2.GA, and 2.1.0.BETA1) all with the same results.
Unfortunately, I have to use this Mac for development, and if I can't find the exact reason for what's happening, I might have to try to change the Java version on it, or upgrade to Leopard and see if that works. I will start sending out those crash reports to Apple though..
Thanks for your input, Daniel.
Update: I found a post on the JBoss forums (http://jboss.com/index.html?module=bb&op=viewtopic&t=136650) that suggests the problem is Apple's quartz renderer, and a workaround for it is to run your server with the option "-Dapple.awt.graphics.UseQuartz=false" so if you're running JBoss AS it would be:
I haven't tried this on Tomcat, but it worked for me on JBoss 4.2.2. Hope this helps.
I've just updated to seam 2.1.0.GA and deployed a very simple seam ap. As soon as I view a page the JVM crashes with the following error:
Invalid memory access of location 52b81000 eip=904706f9
./run.sh: line 246: 262 Segmentation fault "$JAVA" $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"
This happens consistently, every time I visit a page. If I revert back to seam 2.0.2.SP1 then it all works fine. What has changed between 2.1.0.GA and 2.0.2.SP1 that can cause this?
I'm running :
Mac Os X 10.4.11.
I've tried using the -Dapple.awt.graphics.UseQuartz=false system property suggested in the previous post but that doesn't help. :(
Anybody shed any light on this? I really don't want to have to abandon Mac Os X...
I'm really stuck on this one...
Could it be anything to do with this?
It's suggesting some stuff compiled using java 6 might not like being run on Mac Os X? :(
Any updates on the topic yet? I'm having the same problems on Mac OS X 10.4.11, JBoss AS 4.2.3 and Seam 2.1.0 SP1.
So I downgraded to Seam 2.0.2.SP1 (still use JBoss AS 4.2.3.GA) and the simple CRUD app works now. I have no glue why? Any ideas?
The first thing I'm doing after Glassfish installation on my OS X Server is configuring the
jvm option for glassfish.
Not sure if it will helps, but it was not mentioned here so far.