12 Replies Latest reply on Dec 4, 2008 7:13 PM by Nick Belaevski

    RichFaces 3.2.1 JBoss Segmentation fault!

    Thomas Kessler Newbie

      I'm running JBoss 4.2.2 and I just updated my RichFaces library from 3.20 to 3.2.1. Everything seemed to be fine until I tried to load a page which contained a simpleTogglePanel. JBoss just crashed, totally dead. This did not happen w/RichFaces 3.2.0 Here's what JBoss said:

      /usr/local/jboss/bin/run.sh: line 246: 512 Segmentation fault "$JAVA" $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"
      

      TK

        • 1. Re: RichFaces 3.2.1 JBoss Segmentation fault!
          Nick Belaevski Master

          Hello,

          Could you please provide some more info: JVM, JBoss, OS versions; JVM crash dump?

          • 2. Re: RichFaces 3.2.1 JBoss Segmentation fault!
            Thomas Kessler Newbie

            JBoss 4.2.2
            OS:

            ProductName: Mac OS X
            ProductVersion: 10.4.11
            BuildVersion: 8S165

            Java:
            java version "1.5.0_13"
            Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
            Java HotSpot(TM) Client VM (build 1.5.0_13-121, mixed mode, sharing)


            The only output when running JBoss on a command line was what I pasted above. Is there a JVM crash log somewhere?

            • 3. Re: RichFaces 3.2.1 JBoss Segmentation fault!
              Reid Swanson Newbie

              I'm having a similar issue.

              Running:
              osx 10.4.11
              java 1.5.0_13
              tomcat-6.0.16

              tomcat crashes on just about anything I try with RichFaces 3.2.1.

              E.g. I can load a page with a modal panel and an outputLink with a componentControl but when I show the panel tomcat crashes and I get an error on the command line like:
              Invalid memory access of location 02435000 eip=90471719

              Nothing is output in the apache logs and like djkrite I don't know how to access the jvm error log

              • 4. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                Thomas Kessler Newbie

                i'm able to run the same web application with richfaces 3.2.1 on:

                Linux version 2.6.22-14-generic (buildd@king) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12 02:46:46 UTC 2008


                and:

                Java version: 1.5.0_13


                JBoss 4.2.2


                Seems to be an OS X or OS X Java related issue.


                • 5. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                  Reid Swanson Newbie

                  I can also get my application working on Linux but unfortunately for work I need it running on the Mac.

                  Hopefully a solution will present itself.

                  • 6. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                    Dmitry Shultz Novice

                    Hi,

                    I'm running Glassfish on OS X Server and having the same problem.

                    Not sure when it started, but Java crashes often recently, looks like there is some bug in Apple 1.5 JVM and there is no 1.6 for me... :(

                    I'm going to switch from Apple to something more Java friendly.

                    • 7. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                      Craig Hollinshead Newbie

                      Ran into a similar problem on Mac OS X using RichFaces 3.2.1 and Tomcat.

                      The problem seems to be occurring with certain controls (in this case rich:tabPanel). Removal of the control eliminated the crash. Also, while this problem IS occurring on a PPC system running 10.4.11, it IS NOT occurring on an Intel MacOS X system running 10.5 (both using RichFaces 3.2.1, both running Tomcat 6.0.16).

                      From the JVM crash log(~/Library/Logs/CrashReporter/java.crash.log) , it looks like it faults trying to render the control with Apple's code.

                      System Info

                      OS = 10.4.11 (PPC)
                      Tomcat = 6.0.16
                      JVM = 1.5.0_13-b05-241


                      Relevant part of a big JVM crash log (email me for the whole log):


                      
                      Exception: EXC_BAD_ACCESS (0x0001)
                      Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
                      ...
                      ...
                      Thread 24 Crashed:
                      0 com.apple.CoreGraphics 0x904f2230 getNextAxialDitheredShadingScanline + 1080
                      1 com.apple.CoreGraphics 0x904850c8 getNextAxialShadingScanline + 48
                      2 com.apple.CoreGraphics 0x904856cc getBytesAxialShadingDataProvider + 128
                      3 com.apple.CoreGraphics 0x903d5e70 CGAccessSessionGetChunks + 508
                      4 com.apple.CoreGraphics 0x903d59f4 img_raw_read + 240
                      5 com.apple.CoreGraphics 0x9043b684 img_alphamerge_read + 476
                      6 com.apple.CoreGraphics 0x903d4648 img_data_lock + 3680
                      7 com.apple.CoreGraphics 0x903d2e64 CGSImageDataLockWithReference + 156
                      8 libRIP.A.dylib 0x9483238c ripc_AcquireImage + 920
                      9 libRIP.A.dylib 0x94830a88 ripc_DrawImage + 2428
                      10 com.apple.CoreGraphics 0x903d2bb4 CGContextDelegateDrawImage + 76
                      11 com.apple.CoreGraphics 0x903d2b0c CGContextDrawImage + 340
                      12 com.apple.CoreGraphics 0x90484094 drawAxialShading + 1052
                      13 com.apple.CoreGraphics 0x90483bf8 CGContextDrawShading + 172
                      14 libawt.jnilib 0x9fe61464 CompleteCGContext + 828
                      15 libawt.jnilib 0x9fe6fa88 ImageSD_finishCGContext + 44
                      16 libawt.jnilib 0x9fe6fce8 Java_apple_awt_CRenderer_doShape + 500
                      17 <<00000000>> 0x04591264 0 + 72946276
                      18 <<00000000>> 0x0458aab0 0 + 72919728
                      19 <<00000000>> 0x0458aab0 0 + 72919728
                      20 <<00000000>> 0x0458aab0 0 + 72919728
                      21 <<00000000>> 0x0458aab0 0 + 72919728
                      22 <<00000000>> 0x0458ae10 0 + 72920592
                      23 <<00000000>> 0x0458ae10 0 + 72920592
                      24 <<00000000>> 0x0458aab0 0 + 72919728
                      25 <<00000000>> 0x0458aab0 0 + 72919728
                      26 <<00000000>> 0x0458aab0 0 + 72919728
                      27 <<00000000>> 0x0458a9c0 0 + 72919488
                      28 <<00000000>> 0x0458ae10 0 + 72920592
                      29 <<00000000>> 0x0458aab0 0 + 72919728
                      30 <<00000000>> 0x0458aab0 0 + 72919728
                      31 <<00000000>> 0x0458ad20 0 + 72920352
                      32 <<00000000>> 0x0458aab0 0 + 72919728
                      33 <<00000000>> 0x0458ad20 0 + 72920352
                      34 <<00000000>> 0x0458aab0 0 + 72919728
                      35 <<00000000>> 0x0458a930 0 + 72919344
                      36 <<00000000>> 0x0458ae10 0 + 72920592
                      37 <<00000000>> 0x0458aab0 0 + 72919728
                      38 <<00000000>> 0x0458ae10 0 + 72920592
                      39 <<00000000>> 0x0458ae10 0 + 72920592
                      40 <<00000000>> 0x0458aab0 0 + 72919728
                      41 <<00000000>> 0x0458aab0 0 + 72919728
                      42 <<00000000>> 0x0458ae10 0 + 72920592
                      43 <<00000000>> 0x0458ae10 0 + 72920592
                      44 <<00000000>> 0x0458ae10 0 + 72920592
                      45 <<00000000>> 0x0458ae10 0 + 72920592
                      46 <<00000000>> 0x0458ae10 0 + 72920592
                      47 <<00000000>> 0x0458ae10 0 + 72920592
                      48 <<00000000>> 0x0458ae10 0 + 72920592
                      49 <<00000000>> 0x0458aab0 0 + 72919728
                      50 <<00000000>> 0x0458ac90 0 + 72920208
                      51 <<00000000>> 0x0458ae10 0 + 72920592
                      52 <<00000000>> 0x04588164 0 + 72909156
                      53 libclient.dylib 0x9c9fcd38 jio_snprintf + 397640
                      54 libclient.dylib 0x9ca0a444 JVM_StartThread + 2612
                      55 libclient.dylib 0x9ca0a330 JVM_StartThread + 2336
                      56 libclient.dylib 0x9ca0a2c0 JVM_StartThread + 2224
                      57 libclient.dylib 0x9ca0a17c JVM_StartThread + 1900
                      58 libclient.dylib 0x9c99518c JNI_CreateJavaVM_Impl + 48364
                      59 libSystem.B.dylib 0x9002bd08 _pthread_body + 96
                      
                      ...
                      ...
                      


                      • 8. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                        Stephan Grüter Newbie

                        I noticed the same problem with OS X 10.4.11 PPC, Java 1.5.0_13-b05-241 and jboss 4.2.2.

                        I tried to use the sun renderer instead of quartz renderer by starting
                        jboss with option "-Dapple.awt.graphics.UseQuartz=false".

                        It seems that the problem can be avoided with this workaround.


                        • 9. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                          Thomas Kessler Newbie

                          Thank you very much.

                          TK

                          • 10. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                            Aladdin El-Nattar Newbie

                            I had the same problem with Mac OS X 10.4.11 (Intel) after upgrading from Richfaces 3.2.0 to 3.2.1 or 3.2.2, but it wasn't connected to a specific component in my case (as far as I could tell). The same stack runs fine on Leopard.

                            The workaround suggested has worked for me, so thanks, sgrueter!

                            --
                            Nazem

                            • 11. Re: RichFaces 3.2.1 JBoss Segmentation fault!
                              Damian Harvey Master

                              I also just upgraded from 3.2.0.GA to 3.2.2.SR1 and encountered this problem on Mac OSX 10.4.11.

                              Sgrueter's useQuartz workaround sorted it for me as well.

                              Cheers,

                              Damian.