the problem is that java has a size limitation of 64k for any one method.
your entire jsp is translated into a single method of a java servlet and with that many tags being used it's simply exceeding java's limit. the "illeg al target of jump or branch" means that the destination of a branch (i.e., r eturn statement, etc.) is too far away... different tags are generated into a different amount of java code depending on their behavior which is why changing a tag appears to change the behavior. your "pragmatic solution" is the *only* solution. you need to break up t he functionality of your jsp into one or more other jsp's. your comment about the page becoming "unusable" is interesting... we use jrun 3/3.1 on nt/solaris and i've never seen that, although we have experience d the "illegal target..." hth! "Johansen, Roar" <[EMAIL PROTECTED]> wrote: > One of the jsps in our service has now apparently reached a limitation. It > sports some 430+ tags that point to our own tag library. > > It has nothing to do with the total number of tags, because the behavio r > that I am about to describe varies independently of the number of tags on > the page, when we swap the tags for some other tag. A page that dies wi th > 430 <mylib:mytag1> survives with 435 <mylib:mytag2> so this obviously h as > something to do with some sort of resource used by the tags. > > Now for the behaviour: > > This message: > > java.lang.VerifyError: (class: jrun__jsp__toobig2ejsp11, method: _jspService > signature: > (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletRe spo > nse;)V) Illegal target of jump or branch > > occurs when this limit is reached (and don't ask how much time it took us to > figure this out...) > > On NT the page is unusable forever more (even after deleting the genera ted > java and .class files and rebooting the box), and a new file name has t o be > assigned before a new version of the page with fewer tags in it can be > re-run. This does not, however, happen on Solaris. > > This happens on both JRun 3.02a and on JRun 3.1 > > Any light shed on this topic is most welcome! > > (Of course, I am aware that the pragmatic solution is "not to use that > amount of tags", but nevertheless, I suspect that it's only a matter of time > before the next page with this behaviour crops up, since our system run s 5 > pages in this category, which are all prone to growing) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
