3 Replies Latest reply on Apr 5, 2002 5:24 AM by Nick

    Struts with JBoss and Tomcat (VM crashes)

    Navdeep Newbie

      I am running an application under JBoss 2.4.3 and tomcat 3.2.3 and we are using Struts version 1.0. While accessing some JSP's containing Struts tags my VM crashes. It does not seem to be any particular struts tag which is causing the problem. Also the same application runs fine under Orion.
      I would really appreciate some help on it.
      The exact message is:
      # HotSpot Virtual Machine Error, Internal Error
      # Please report this error at
      # http://java.sun.com/cgi-bin/bugreport.cgi
      # Error ID: 47454E45524154452F4F502D41500E435050084B
      # Problematic Thread: prio=5 tid=0x7c6220 nid=0xd5 runnable
      Press any key to continue . . .


        • 1. Re: Struts with JBoss and Tomcat (VM crashes)
          J. Wolfgang Kaltz Novice

          Which Java under which OS are you using ?

          PS your problem seems unrelated to JBoss, but if we can help we will of course.

          • 2. Re: Struts with JBoss and Tomcat (VM crashes)
            Navdeep Newbie

            Well I am using win NT 4.0 and tried with VM 1.3.0 , 1.3.1, 1.3.1_01 and 1.4 beta . But I found out the problem is with 64K limit for the methods, one of my JSP service methods was bigger than the limit. So I broke up and it works. The only thing is that when I deploy it as a seperate war file on tomcat I get the 64K error message, but when the war file is part of an ear file, the VM crashes.
            Also the same JSp works in Orion, so it is a Tomcat problem. I also tried the largefile option in Tomcat 4.0, which would have helped except I do not have any static HTML in the JSP.
            Any thought on this would be appreciated very much.

            • 3. Re: Struts with JBoss and Tomcat (VM crashes)
              Nick Newbie

              I met the same problem :-( The solution is in patching jasper compiler. The problem is when you have a lot of custom tags in your jsp - jasper creates servlets with a large amount of "try catch" blocks, witch brokes the virtual machine. I resolve the problem by fixing TagBegin, TagEnd and ParserListener in jasper - to create only one try catch block and a release() method in finally clause.