ClassFormatError

[Konstantin Piroumian <KP...@flagship.ru>]

Does anybody meet such an error:

java.lang.ClassFormatError: Code of a method longer than 65535 bytes
...

This happens if my XML file is very long (more than 35K) and after the XSP
processing
the generated method (I think that it's the populateDocument) become too
long.
Is there any possibility to workaround this?

Any help will be appreciated.

This is the full stack trace:

java.lang.ClassFormatError: Code of a method longer than 65535 bytes
 at java.lang.ClassLoader.defineClass0(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:426)
 at
org.apache.cocoon.processor.xsp.language.java.XSPClassLoader.loadClass(XSPCl
assLoader.java:90)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
 at
org.apache.cocoon.processor.xsp.language.java.XSPJavaProcessor.load(XSPJavaP
rocessor.java:164)
 at
org.apache.cocoon.processor.xsp.XSPProcessor.loadPage(XSPProcessor.java:509)
 at
org.apache.cocoon.processor.xsp.XSPProcessor.process(XSPProcessor.java:490)
 at org.apache.cocoon.Engine.handle(Engine.java:359)
 at org.apache.cocoon.Cocoon.service(Cocoon.java:167)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java:503)
 at org.apache.tomcat.core.ContextManager.service(ContextManager.java:559)
 at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java:160)
 at
org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java:338
)
 at java.lang.Thread.run(Thread.java:484)
--
Regards,
  Konstantin Piroumian

Email: kpiroumian@mail.ru

Re: ClassFormatError

[Ulrich Mayring <ul...@denic.de>]

Konstantin Piroumian wrote:
> 
> Does anybody meet such an error:
> 
> java.lang.ClassFormatError: Code of a method longer than 65535 bytes
> ...
> 
> This happens if my XML file is very long (more than 35K) and after the XSP
> processing
> the generated method (I think that it's the populateDocument) become too
> long.
> Is there any possibility to workaround this?

There have been extensive discussions about this problem. The short
answer is: there is no easy workaround. The long answer: see mailing
list archive.

Ulrich

-- 
Ulrich Mayring
DENIC eG, Systementwicklung