You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Rahul Mohan <ra...@pune.tcs.co.in> on 2004/05/18 07:36:19 UTC
code too large for try statement
Hi,
I have a JSP page with Struts and JSTL tags. It is pretty big with about
15 conrols and a *LOT* of JSTL tags. When I try host the page in Weblogic8.1
i get the following compile error:
window.java:12652:code too large for try statement
try { // _c_set1 popBody() try/finally.. ...
in other words the try {} block in _jspservice is so huge, it exceeded the
64K limit imposed by jvms.
The root problem I found out to be in the jsp traslation mechanism of
weblogic8.1 container. It translates the entire page into a single
_jspservice method. Is this a known problem with weblogic and jstl tags (i
think its the code for tag thats making the servlet huge) ?
I tried the same page on tomcat. Tomcat does not give any problem as it
handles each tag as a seperate method which is being called from
_jspService. we have to agree that tomcat uses a much better way of doing
it!
has anybody else faced this problem before? do we have any workarounds,
other than using jsp:include?
awaiting ur comments....
rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: code too large for try statement
Posted by Susan Bradeen <Su...@softlanding.com>.
"Rahul Mohan" <ra...@pune.tcs.co.in> wrote on 05/18/2004 01:36:19
AM:
>
> Hi,
>
> I have a JSP page with Struts and JSTL tags. It is
> pretty big with about
> 15 conrols and a *LOT* of JSTL tags. When I try host the page in
Weblogic8.1
> i get the following compile error:
>
> window.java:12652:code too large for try statement
> try { // _c_set1 popBody() try/finally.. ...
>
> in other words the try {} block in _jspservice is so huge, it exceeded
the
> 64K limit imposed by jvms.
>
> The root problem I found out to be in the jsp traslation mechanism of
> weblogic8.1 container. It translates the entire page into a single
> _jspservice method. Is this a known problem with weblogic and jstl tags
(i
> think its the code for tag thats making the servlet huge) ?
>
> I tried the same page on tomcat. Tomcat does not give any problem as it
> handles each tag as a seperate method which is being called from
> _jspService. we have to agree that tomcat uses a much better way of
doing
> it!
>
> has anybody else faced this problem before? do we have any
workarounds,
> other than using jsp:include?
>
Yes, this has come up before on this list. I ran into this issue using on
older version of Websphere until I started using tiles. This search in the
archives may give you some background and ideas.
http://marc.theaimsgroup.com/?l=struts-user&w=2&r=1&s=64k+limit&q=b
Hope that helps,
Susan Bradeen
> awaiting ur comments....
>
> rahul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org