https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #13 from Christopher Schultz ---
(In reply to York Chen from comment #12)
> Looks like this issue exists in all Tomcat 9.
> Is there any way to fix it in tomcat9?
The problem is that your JSP code is "too big". Try to break-up your
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #12 from York Chen ---
Looks liks this issue exists in all Tomcat 9.
Is there any way to fix it in tomcat9?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #11 from Günter Paul ---
Have the same problem, tomcat 8.5 and tomcat 9 too.
We have hundred of older jsp-files with struts 1.1 and no easy solution for the
problem.
We are using tomcat 8.0.3 without problems. Can't find the differ
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #10 from Ralf Hauser ---
(In reply to Christopher Schultz from comment #9)
> Please take this conversation to the users list. If you do so, please
> provide examples of the .java files that will not compile successfully.
cannot uplo
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #9 from Christopher Schultz ---
Please take this conversation to the users list. If you do so, please provide
examples of the .java files that will not compile successfully.
--
You are receiving this mail because:
You are the assi
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #8 from Ralf Hauser ---
Finally got it to compile again.
Just for the record (in my case the exact error message was "The code of method
_jspService(HttpServletRequest, HttpServletResponse) is exceeding the 65535
bytes limit"):
1)
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #7 from Christopher Schultz ---
(In reply to Ralf Hauser from comment #5)
> see also bug 60578#c3
I'm not sure these bugs are related in any way.
I'm surprised to see a file owned by root. That should not be possible unless
your p
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
Ralf Hauser changed:
What|Removed |Added
CC||hau...@acm.org
--
You are receiving thi
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #6 from Ralf Hauser ---
we got that problem when upgrading from tc8.0.14 to 8.5.9 for several jsp pages
that before didn't have it (and not change to the jsp).
1) the jsp generation got less efficient!
before 8.0.14: wc outboxmess
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #5 from Ralf Hauser ---
see also bug 60578#c3
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #4 from Christopher Schultz ---
(In reply to Mark Thomas from comment #3)
> It should be possible to analyse you generated clss files to see how big
> they are.
In this case, the compiler is failing, so no .class file is generated.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #3 from Mark Thomas ---
What actaully matters is the size of the .class file. That has to conform to
the JVM specification. There are various limits there although the method size
one is the one folks tend to hit first.
It should b
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
--- Comment #2 from Björn Mahler ---
Okay - so how do we know that we are close to the limit - what kind of limits
in our JSP do we have to consider and how can we avoid that?
But I'll check what you suggested... thanks for the quick answer.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60126
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
14 matches
Mail list logo
