Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat throwing jsp error where other application servers do not

 
jason adam
Chicken Farmer ()
Ranch Hand
Posts: 1932
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a vendor's webapp I am trying to run through Tomcat. However, when certain pages are accessed, the following error appears:
org.apache.jasper.compiler.CompileException: /jsp/case/caseinjdata.jsp(12,0) Unterminated <%-- tag at org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEventListener.java:784) at org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingListener.java:121) at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java:243) at org.apache.jasper.compiler.Parser.parse(Parser.java:1133) at org.apache.jasper.compiler.Parser.parse(Parser.java:1091) at org.apache.jasper.compiler.Parser.parse(Parser.java:1087) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:213) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:210) at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:546) at ...
(number lines change for the first line depending on the page)
According to the vendor, they have not had this problem with WebLogic, WebSphere, JRun, etc. but they have not tested the product on Tomcat. A sample offending page is as follows:

(onLoade misspelled to keep the board from detecting it)
If something runs on the app servers, shouldn't it run on Tomcat, being the reference implementation for the jsp/servlet specifications?
Has anyone had a problem like this, or have any ideas on where the problem is occurring? Nothing appears wrong with their jsp code.
Thanks
 
jason adam
Chicken Farmer ()
Ranch Hand
Posts: 1932
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Vendor responded saying their version of Tomcat (3.3.1) doesn't throw this error. Obviously something with 4.0.1. Odd.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic