Post subject: JSP pages stop working when adding too much to the page? Posted: Jan 02, 2009 - 11:25 AM
Joined: Dec 29, 2005
Posts: 7
Hi,
I have hit the same problem a couple times lately where I am getting errors in the JSP page in the browser (ie malformed HTML) and in the console (java.io.FileNotFoundException) when I add code that I know works.
It seems that the system gets to a point where I add one more method call from an object within the JSP page and the system starts to throw errors (as mentioned above) for that page.
For example, I am now at the point where (after much testing and investigation) I will have a working system and I then duplicate an existing call that I know is working on the same JSP page:
<%=sessionObject.getsomething()%>
So once the duplicate call is in place the system seems to have hit a limit and it cant handle any more. So it does not matter what I add - nothing new added will work. Although I know the calls all work.
Are the upper limits on how complicated the JSP page can be in MyEclipse? This page is rather long and complicated with Includes that have Includes. So all up the files will be up to 7000 lines in the JSP files (if you count all of the includes and includes) but they are never all shown at the same time.
The complete exception is as follows:
java.io.FileNotFoundException: /maindirectory/internal/some junk reference to data or text that would normally appear as text on the page<br>images/help.gif
at jrun.servlet.file.FileServlet.service(FileServlet.java:349)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at com.shipshaperesources.servlets.InternalFilter.doFilter(InternalFilter.java:107)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
I am using MyEclipse 6.5.
Any help or suggestions would be appreciated.
The Whale.
Whale
Post subject: Is this related to the 64K Method size restriction? Posted: Jan 02, 2009 - 09:27 PM
Joined: Dec 29, 2005
Posts: 7
Just wondering if this is related to the 64K Method size restriction but JRun is not throwing the normal exception to show that it is too big?
In relation to the IBM Websphere some websites make reference to "PQ57269: JSP'S FAIL TO COMPILE WITH " BRANCH TOO LARGE " EXCEPTION" or the like.
Although my pages are getting compiled, it is not till they are called that the problems are appearing?