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 behavior 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 with 430 <mylib:mytag1> survives with 435 <mylib:mytag2> so this obviously has 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/HttpServletRespo 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 generated java and .class files and rebooting the box), and a new file name has to 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 runs 5 pages in this category, which are all prone to growing) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
