Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.lang.VerifyError : Illegal target of jump or branch

98 views
Skip to first unread message

Arnaud Ferrand

unread,
Jan 20, 2003, 1:40:23 PM1/20/03
to
Hi,

We have a problem runing my application on Weblogic 6.1 sp 4 on solaris 8.
The application works correctly on Windows NT. But we got this exception on
SUN (see the end of the message).

This occurs in a jsp including another big with the old include statement
<%@ include file="/Templates/onglets/Methodes.jsp" %>
the Methodes.jsp file defines some variables used in the current jsp so we
can't use the <jsp:include...> tag ! But why does it work on NT ?

Can anybody help us ???


<Jan 20, 2003 1:46:45 PM GMT-01:00> <Error> <HTTP>
<[WebAppServletContext(2804551,Welcome,/Welcome)] Error loading servlet:
"/Activities/FTWEL/initManagerArrInt_01.jsp"
java.lang.VerifyError: (class:
jsp_servlet/_Activities/_FTWEL/__initManagerArrInt_01, method: _jspService
signature:
(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResp
onse;)V) Illegal target of jump or branch
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.jav
a:690)
at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.j
ava:658)
at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.ja
va:603)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:215)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:154)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:3
70)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav
a:240)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav
a:321)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav
a:198)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherIm
pl.java:250)
at fr.w4.http.W4Servlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav
a:262)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.jav
a:198)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletC
ontext.java:2637)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.jav
a:2359)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>

Steven Samorodin

unread,
Jan 25, 2003, 2:07:22 PM1/25/03
to
Hi Arnaud,

In the past I've seen this exception because the JSP in question
compiled to have a try catch block that was too large. I forget what
the number of allowable lines is, but you can exceed it when making a
large JSP. What version of the JDK are you using? With WL7 and
JDK1.3.1.03 we see a better error message, but it amounts to the same
thing. We got around this problem by using dynamic includes for large
components. It is a pain to do this in places where you are doing it
only because of this problem, but it has worked for us.

There is also a 'no try blocks' option on weblogic's JSP Compiler, but
I've never played with that much.

As for why you might see it on Solaris, but not NT, I can verify that
we have seen the same behavior before. Maybe the windows VM
implementation allows for try blocks that are larger than the spec.

Either way good luck.
Steven

Arnaud Ferrand <arnaud....@steria.com> wrote in message news:<Xns9309C83453...@216.148.48.100>...

0 new messages