I used to get this error with WebLogic when there are more than one .class for
a Java class(whether a JavaBean or a Servlet). For example if you have a Java
Bean called User.java and if User.class is there at multiple locations, then
I used to get this error. The only remedy I found was to remove those unwanted
.class files. This was the behavior for WebLogic, I don't if it is the same
with Tomcat.
Shireesh Thanneru
On Tue, 5 Dec 2000, duncan wrote:
>I have seen in the archives several posts detailing the same problem.
>However I could find no response. Hence I'm posting again.
>
>OS - Win NT 4 sp6a
>Suns JDK 1.2.1
>Tomcat 3.2 final
>
>The error occurs with JSP pages with a large number (250+) of taglib
>actions.
>The java source file is generated (500k). The class file is also
>generated (90k).
>When the page is accessed you get the java.lang.VerifyError.
>
>When I compiled the generated java file myself with JDK 1.3 (default
>options) I got a class file of (102k). This class file then works fine
>when running Tomcat under JDK 1.2.1. However Running Tomcat under JDK
>1.3 results in excessively large response times 40+ seconds (see my last
>post - Performance problems with tomcat 3.2 and Sun's JDK1.3 for Win32).
>
>Compiling manually with JDK 1.2.1 produces a class file of 90K and this
>fails with the same verify error.
>
>Does Jasper use any special compiler options ?
>
>Could this be a memory problem that's not logged at compile time?
>
>Any clues?
>
>Regards
>Duncan
>
>
>--
>---------------------------------------------
>Duncan Reade
>TecSys Infopartners S.A.
>4, rue Jos Felten,
>L-1508 Howald
>Luxembourg
>[EMAIL PROTECTED]
>Tel: +352 40116 3303
>Fax: +352 40116 2331
>---------------------------------------------
>
>
>
