asked on

Code of a method longer than 65535 bytes exception, need urgent help!

hey guys here's the situation, we have a standard ntier j2ee app running on weblogic. Everything is fine until last night, we got this exception on multiple jsp/java files in our app:

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

1) there was no code change to the app
2) the exact same war file work in our dev and qa weblogic environment with no such exceptions, only in stage this exception comes up. Again the war file is exactly the same!

why is this happening? ANY ideas are welcome, thank you!

bloodredsun

I've normally seen this when a JSP is larger than 64K in size. This happens when someone has been editing the JSPs which when the are compiled to java classes, the entire JSP becomes one big method jsp_service(). You can normally get round this by using dynamic includes/composite view pattern.

I don't know why it's working on dev and qu but not prod. Is there any different in hardware/setup?

SOLUTION

hadolphs

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gagaliya

ASKER

yes 100% sure the file was not touched, we did a diff, last update time check, cvs check etc the files are exactly the same. Also same file works in qa/dev but not stage.

we are using wls81, and always manually delete the caches from wls when we deploy just to be sure.

my only guess was the java jdk itself was changed by the network guys somehow, but they said that's not the case and our onsite weblogic team told us even if the jvm are changed this should not cause the issue because the 64k limit is a standard java limitation across all versions of jdk.

so what gives?? :( the day before new year weekend...argg......

ASKER CERTIFIED SOLUTION

bloodredsun

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gagaliya

ASKER

this is resolved, weblogic support added an external memory monitoring (hp openview) to our app..and this increased the file size across the board for the app. so the already large files are now over 64k. Once the memory monitoring was removed, everything is back to normal.

another great mystery resolved...thanks guys.

bloodredsun

Legend! Glad to have helped if only a little :-)