Code too large error

Hi,
I have an enum with about 3000 values in application. When I add some more items I get "code too large" error during compilation.
Is there any workaround for that problem? (Some configuration change?)
What exactly does compiler want to say? Where can I find info about what limit do I exceed?
I will appreciate any kind of help :)
Greetings
Michal

what can you kno? Model of the form is not hardcoded, it is in DB, it is modifiable by user(admin). Only elements which have specific business validation have identifier (i mean enum identifier). They must be somehow identified, not just by number. Number may change if sone adds a question before this one.
What's better than that? The solution has been made before I came to the company, but I believe it is one of the best possible.

Similar Messages

Private void initComponents(){} Error - Code too large

I am doing java project using netbean 6.5. It has frame contaning a jtabbedPane.
This tabbed contain 10 tabs.Each tab has contain of labels,textboxes,option button...etc.
my private void initComponents() method has all most 5000 code line.problem is when i try to
add more components in to tabbed it won't compile & gives private void initComponents(){} - Code too large error.
How can i escape from this?
Can anyone HELP me?

Delete that garbage and hand code it. Create individual classes for the panels you add to JTabbedPane.
BTW: you shouldn't use an IDE/Gui builder if you don't know how to do it youself.

Enum code too large 64k limit

While compiling with JDK1.5 received a "code too large" error when trying to compile an enum. Apparently the 64k limit is imposed on the new enum spec.
This restriction doesn't allow for enums with a large set of values which is impractical at best.
Has anyone else encountered this problem and received any response from Sun?

Sorry I should further explain the "impractical" meaning.
Consider the example code:
public enum MyEnum
FIRST( 1, "One" ),
SECOND( 2, "Two" ),
THIRD( 3, "Three" );
private final Integer value;
private final String label;
private MyEnum( final Integer value, final String label )
this.value = value;
this.label = label;
public Integer getValue()
return this.value;
public String getLabel()
return this.label;
The "impractical" part comes in where I'm limited by the enum constant statement string of 64k. So, if I have several enums with even modest lengthed labels I'm stuck. I currently am able to implement this in JDK 1.4 using typesafe enum pattern. I would like to implement the same way using enums in JDK 1.5.

Jdeveloper Error: "Code too large"

Hi all,
While running a page in Oracle Jdeveloper 10g, I am getting compilation error “Code too large” on ‘processformrequest’ in controller. I tried the below steps from metalink, but I am still getting the error message.
1. Try to compile your page with the standard "javac" Java compiler instead of the "ojc" Java
compiler, as it generates methods a bit smaller.
2. Change the compiler used by the Embedded OC4J:
2.1) Go to "Tools" -> "Embedded OC4J Server Preferences..."
2.2) Under "Global" select "Java Compiler"
2.3) Select "javac" from the "Compiler" list
2.4) Then under "Bin Directory", point to the location of the javac compiler
(usually in the JDK bin directory).
Please let me know if there is any way to resolve this error.
Thanks in Advance,
Saravana

Hi Saravana,
Please post this in OAF forum(OA Framework
~Vikram
Edited by: Vikram K on Jul 27, 2009 11:00 AM

500 Internal Server Error OracleJSP: code too large for try statement catch

We have an application which uses JSPs as front end and we are using Struts 1.1. When we run one of the JSP it shows the following error after executing .We are using OCJ4 server having version 9.0.4.0
500 Internal Server Error
OracleJSP: oracle.jsp.provider.JspCompileException:
Errors compiling:E:\oracle\product\10.1.0\AS904\j2ee\home\application-deployments\VAS3006\vas\persistence\_pages\\_Requirement .java
code too large for try statement catch( Throwable e) {
7194
code too large for try statement catch( Exception clearException) {
44
code too large for try statement try {
23
code too large public void _jspService(HttpServletRequest request, HttpServletResponse response) throws java.io.IOException, ServletException {
The JSP/application runs okay on one machine (System Tesing machine)with OCJ4 server having version10.1.2.0 but throughs an error on other machine( Development machine)with OCJ4 server having version9.0.4.0.The question is why it is running on one machine ane giving error on other machine I am aware that there can't be more than 64kB of code between try-catch block .Total size of the generated JSP class in our case is 577KB.
Is the problem because of different version of Application server OC4J?.Is it any fix for this? Or Can anyone please suggest a work around. Or is there a method by which the JSP generated code is split between different try - catch blocks rather than a single try-catch block.Utlimately We don't know the whether is it a problem with JVM or hardware .
It would be really helpful if you would provide me with some suggestion and input.
Regards
Shyam

Sir,
I am aware of the limitations of JVM that it won't allow java code more than 64Kb in method but we are using different versions of Application server .Application is working okay with OC4J application server(10.1.2.0) but gives error on Application server with version 9.0.4.0. Is this a problem with OC4J application server 9.0.4.0. I had gone through the documentation ofOC4J 9.0.4.0.application server but it does not mention about the this bug/fixes.
Please giude me on the same.
Regards,Shyam

Error in jsp:Code too large for try statement

Hi friends,
When i try to run a jsp program i am getting error "code too large for try statement". How can i rectify it rather than truncating that jsp? is there another way?
Basha

Basha,
When we were implenting an e-form component which was very big, the only way we were able to achieve it was by
"jsp includes". In the main form simply included muliple
jsp pages, where each was a section of the e-form.
we have not found any other better way.
Hope this helps.
-Venkat Malempati
Message was edited by: Venkat Malempati
Message was edited by: Venkat Malempati

How do you avoid a code too large for try statement error message while com

i have the jsp which is having 142 fields
i am trying to dispaly 142 fields its showing the above error
at runtime
i think JVM is not allowing to complie the jsp
please any body give me the solution for it

I've got the same error with Weblogic 8.1 .
When I tried to visit a JSP I wrote, which had many tags, the page showed the error: code too large for try statement.
I'v reviewed a lot of discussions through the internet and solved the problem at last by adding one parameter to weblogic.xml.
<jsp-descriptor>
     <jsp-param>
          <param-name>noTryBlocks</param-name>
          <param-value>true</param-value>
     </jsp-param>
</jsp-descriptor>Hope this may help you out.

Error: code too large for try statement, when compiling a big java file.

Hi,
I have a big java file ( around 16000 lines). When compiling it, I got following error message:
MyMain.java:15233: code too large for try statement
} catch ( Throwable t ) {
In MyMain.java, I just repeat following statements about 1000 times.
try {
if ( year >= 2002 ) {
System.out.println( "year: Evaluation version is not valid" );
} else {
System.out.println( "year: Evaluation version is still valid" );
} catch ( Throwable t ) {
if ( year >= 2002 ) {
System.out.println( "year: Evaluation version is not valid" );
} else {
System.out.println( "year: Evaluation version is still valid" );
I tried 1.3 and 1.4 javac compiler, there was some error.
How to make compiler to compile this code?
Thanks,

Hi,
I have a big java file ( around 16000 lines). When
compiling it, I got following error message:
MyMain.java:15233: code too large for try statement
} catch ( Throwable t ) {
I tried 1.3 and 1.4 javac compiler, there was some
error.
How to make compiler to compile this code?
You don't. Each method has an absolute limit on the number of byte codes. You have reached that limit. The limit is part of the specification and JVMs will refuse to run classes that exceed the limit. So even if you could compile it, it wouldn't run.
It is quite common for code generators to generate large monolithic blocks of code. Presumably this is how you got to this spot. Modify the code generator to break it into smaller blocks.
If you did it manually then you did it wrong. And you will have to manually break it into smaller blocks. (And re-examine your design since it is probably wrong.)

Compilation Error Code too large for Try block

I am getting error while jsp compilation.
          code too large for try statement.
          Can anybody help me in this. I am using WL 8.1.4
          Thanks in Advance
          Himanshu

This article pretty much sums it up: http://www.experts-exchange.com/Web/Web_Languages/JSP/Q_20711819.html
          Your JSP_.java file will not compile to a .class file since the JSP is too large and the newer java compiler is more strict. You have to most likely break your JSP up using includes or use a more efficient design.

HELP!!! Error "code too large"

Hello, I am working on a program that has become very large... and apparently it is too large now...
When I try to compile the program it generates an error, "code too large", the code has exceeded 10000 lines and now I dont know what to do. Anyone that has any ideas? Thankful for any response...

Let's say, for instance, that I wnat to initialize an array instance variable that will contain 7462 integer values in my constructor, just as an example. I'm not really sure if this exceeds the maximum size for a java array, but if it does that would be just as useless a restriction as this "code too large" thing. If I write huge code that means I need huge code. [ goes to write program in C, which would be my advice here. :) ]

Too large error troubleshooting jdev10.1.3.3- jhs10.3.2.52

Hi, how are you? I have in my jheadstart application definitiion cases where one detail or detail-detail group has list of values, when I run the application I take the following error: • Error: code segment of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) too large
, then I set the generate groups in region file- generate search area in region file properties- generate and run the application , but I cannot open the detail groups or both the list of values in master groups. Then I uncheck these properties and run again but sometimes I take again the above too large error, which prevents me from running the application. i' ve heard that if one buys the jheadstart license can have access to one patch that faces the too large problem successfully, we have the jheadstart license by oracle, could you inform about any possible solution that could solve this problem?

Yes, if you have a JHeadstart license, you can download the latest 10.1.3.3 release from cso.oracle.com.
Can you download this version and see whether it solves your problem?
Steven Davelaar,
JHeadstart team.

Code too large for try statement

I have a jsp that I am getting the following exception on.
[ServletException in:/jsp/DLG_PTEN.jsp] Unable to compile class for JSP C:\Documents and Settings\ebsgam\My Documents\IBM\wsappdev51\workspace\StnWeb\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\DefaultEAR\StnWeb.war\jsp\_DLG_5F_PTEN.java:13576: code too large for try statement } catch (Throwable t) { ^ C:\Documents and Settings\ebsgam\My Documents\IBM\wsappdev51\workspace\StnWeb\.metadata\.plugins\com.ibm.etools.server.core\tmp0\cache\localhost\server1\DefaultEAR\StnWeb.war\jsp\_DLG_5F_PTEN.java:1165: code too large for try statement try { ^ 2 errors '
I am currently running this on Websphere Aplication Developer 5. First off I'm hoping that this error will go away when it is deployed to tomcat. But I wanted to see if anyone has had this problem and knows of a tweek or work around for it.
The jsp in question is not the longest one I have... but it has a large number of drop down list boxes .. using jstl <select><option>. and the drop downs have around 40 or 50 items in them.

in weblogic 8.1, i've met the same error, and solved the problem by adding param to weblogic.xml , like below:
<jsp-descriptor>
     <jsp-param>
          <param-name>noTryBlocks</param-name>
          <param-value>true</param-value>
     </jsp-param>
</jsp-descriptor>

Code too large

Hi,
I did a search on this in some forums here and I realize that I have too much code in my BIG class.
Right now I have one huge class which has pretty much everything in it. I have fragmented my code within this class, with multiple subclasses and many small methods as I realize this is the idea behind OOP. However, I never really thought about breaking up this one class that everything is inside of.
So I have a couple of questions...
1) I have level layouts that look like the following:
        // LEVEL 6
        char [][] Level_6_Board =
//        0   1   2   3   4   5   6   7   8   9   10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
/* 0 */ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 1 */ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 2 */ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','G','e'},
/* 3 */ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 4 */ {'e','e','e','e','e','e','e','e','e','e','e','W','W','W','W','W','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 5 */ {'e','e','e','e','e','e','e','e','e','e','e','W','e','e','e','W','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 6 */ {'e','e','e','e','e','e','e','e','e','e','e','W','e','R','e','W','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 7 */ {'e','e','e','e','e','e','e','e','e','e','e','W','W','e','W','W','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 8 */ {'e','e','e','e','e','W','W','W','W','e','e','e','W','e','W','e','e','e','W','W','W','W','e','e','e','e','e','e','e','e'},
/* 9 */ {'e','e','e','e','e','W','e','e','W','W','W','W','W','e','W','W','W','W','W','e','e','W','e','e','e','e','e','e','e','e'},
/* 10*/ {'e','e','e','e','e','W','e','e','e','e','e','R','e','e','e','R','e','e','e','e','e','W','e','e','e','e','e','e','e','e'},
/* 11*/ {'e','e','e','e','e','W','e','e','e','W','W','W','W','W','W','W','W','W','e','e','e','W','e','e','e','e','e','e','e','e'},
/* 12*/ {'e','e','e','e','e','W','W','W','e','W','e','e','e','e','e','e','e','W','e','W','W','W','e','e','e','e','e','e','e','e'},
/* 13*/ {'e','e','e','e','e','e','e','W','e','W','W','e','e','M','e','e','W','W','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 14*/ {'e','e','e','e','e','e','e','W','e','W','e','e','e','e','e','e','e','W','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 15*/ {'e','e','e','e','e','e','e','W','e','W','e','R','e','e','e','R','e','W','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 16*/ {'e','e','e','e','e','e','W','W','e','W','M','e','e','e','e','e','M','W','e','W','W','e','e','e','e','e','e','e','e','e'},
/* 17*/ {'e','e','e','e','e','e','W','e','e','e','e','e','e','e','e','e','e','e','e','e','W','e','e','e','e','e','e','e','e','e'},
/* 18*/ {'e','e','e','e','e','e','W','e','e','e','W','e','W','e','W','e','W','e','e','e','W','e','e','e','e','e','e','e','e','e'},
/* 19*/ {'e','e','e','e','e','e','W','W','W','e','W','e','e','e','e','e','W','e','W','W','W','e','e','e','e','e','e','e','e','e'},
/* 20*/ {'e','e','e','e','e','e','e','e','W','e','W','W','W','e','W','W','W','e','W','e','e','e','e','e','e','e','e','e','e','e'},
/* 21*/ {'e','e','e','e','e','e','e','W','W','e','e','e','e','e','e','e','e','e','W','W','e','e','e','e','e','e','e','e','e','e'},
/* 22*/ {'e','e','e','e','e','e','e','W','e','e','e','e','e','e','e','e','e','e','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 23*/ {'e','e','e','e','e','e','e','W','e','e','W','e','e','e','e','e','e','e','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 24*/ {'e','e','e','e','e','e','e','W','W','W','W','e','e','e','e','e','W','W','W','W','e','e','e','e','e','e','e','e','e','e'},
/* 25*/ {'e','e','e','e','e','e','e','W','S','S','D','e','e','e','e','e','D','e','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 26*/ {'e','e','e','e','e','e','e','W','S','S','W','W','W','W','W','W','W','e','e','W','e','e','e','e','e','e','e','e','e','e'},
/* 27*/ {'e','e','e','e','e','e','e','W','W','W','W','e','e','e','e','e','W','W','W','W','e','e','e','e','e','e','e','e','e','e'},
/* 28*/ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
/* 29*/ {'e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e','e'},
        };I should move these to another file, usually like in C++ or something I would create a txt file or something and use include to include it. But I guess I should use import but I get an error saying my filename is not a package. How can I include this file in my code?
2) Let's say my big class is called Big. I have a subclass called Levels I want to move out of the Big class.
Should I create another class file called Levels.java and use import?
This doesn't seem to work either...

Number 2 is resolved. So thank you.
With number one, not to go against your advice of reading in from a file and that is something I may do, but I was trying to get the other way to work first, which as you said involves declaring them as constants.
I have tried:
static char [][] Level_1_Board = ....
char [][] Level_1_Board = ...
final char [][]Level_1_Board = ...
final static char [][] Level_1_Board = ...
all are still code too large.
But an interesting point maybe someone else can elucidate is that if I do say half the levels as final static char and the other half as just char it works...

When editing a wiki page, get a 'request entity too large' error message.

[https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators|https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators] I'm trying to edit one of my wiki pages that has been static for about 5 months now, and when I try and save the page, I get the following message (note I cropped some because of formatting issues when posting):
*413 Request Entity Too Large*
HTTP/1.1 413 Request Entity Too Large Date: Tue, 18 Oct 2011 15:35:41 GMT Server: Oracle-Application-Server-10g Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1
Request Entity Too Large
The requested resource
/teamcollab/wiki/<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta content="text/html; charset=utf-8" http-equiv="Content-Type" /><script type="text/javascript"> var U = "undefined"; var gHttpRelativeWebRoot = "/ocom/"; var SSContributor = false; var SSForceContributor = false; var SSHideContributorUI = false; var ssUrlPrefix = "/splash/"; var ssUrlType = "2"; var g_navNode_Path = new Array(); g_navNode_Path[0] = '1790'; g_navNode_Path[1] = 'splash_collabsuite'; var g_ssSourceNodeId = "splash_collabsuite"; var g_ssSourceSiteId = "splash";</script><script id="SSNavigationFunctionsScript" type="text/javascript" src="/ocom/websites/splash/sitenavigationfunctions.js"></script><script id="SSNavigationScript" type="text/javascript" src="/ocom/websites/splash/sitenavigation.js"></script><script type="text/javascript">var g_strLanguageId = "en";</script><script type="text/javascript" src="/ocom/resources/wcm/sitestudio/wcm.toggle.js"></script><script type="text/javascript" src="/ocom/resources/sitestudio/ssajax/ssajax.js"></script> <script id="ssInfo" type="text/xml" warning="DO NOT MODIFY!"> <ssinfo> <fragmentinstance id="fragment1" fragmentid="universal-metatag" library="server:UNIVERSAL-FRAGMENTS"> </fragmentinstance> <fragmentinstance id="fragment2" fragmentid="ExternalSiteCatalystFragment" library="server:EXTERNALSCFRAGMENTLIB"></fragmentinstance> </ssinfo> </script> <meta name="GENERATOR" content="MSHTML 8.00.6001.18904" /><title>Collabsuite Outage</title><meta name="Title" content="Collabsuite Outage"><meta name="Description" content="Collabsuite Outage"><meta name="Keywords" content="Collabsuite Outage"><meta name="robots" content="NOINDEX, NOFOLLOW"><meta name="country" content=""><meta name="Language" content="en"><meta name="Updated Date" content="4/12/11 10:38 AM"> </head><body> <!--SS_BEGIN_SNIPPET(fragment1,code)...
does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.
Additionally, a 413 Request Entity Too Large error was encountered while trying to use an ErrorDocument to handle the request.
The page, should you wish to eyeball it, is at:
https://stbeehive.oracle.com/teamcollab/wiki/Sales+Playbooks:Demonstrating+Differentiators

Duane,
This looks like the URL has the content of a wiki page as an attachment to the URL which is blowing up the get request. Can you go to the earlier version - the history should allow you to backtrack changes - if you access this earlier version and change something small - does it save OK. If so then maybe the change you made is the problem.
I cannot access the workspace without being given explicit access so this is a guess.
Phil

PLS-00123: Program too large error

Hi,
We have been getting a 'PLS-00123: Program too large' error while compiling a particularly large package on a *11g database*. The package has around 15000 lines of code. We are compiling the package using a third party IDE(PL/SQL Developer).
I went through AskTom's note (http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:571023051648) and Metalink Note#62603.1 which helped in understanding the problem. However, could not resolve the problem since modifying the structure of the package was not an option.
Someone from the team contacted a DBA regarding this who in turn suggested that we compile the package in SQL*Plus. We did as suggested on a *10g client* connected to the 11g database and the package got compiled.
I cannot understand why we encountered the error while compiling the package in PL/SQL Developer but not while doing the same from SQL*Plus. Can anyone please explain this or point out some helpful documents?
Regards,
Sujoy

Hope this link helps..
http://forums.allroundautomations.com/ubb/ubbthreads.php?ubb=showflat&Number=10265&PHPSESSID=2e3c1b028a66500ae8a1730abc88b993

Code too large error

Similar Messages

Maybe you are looking for