Problem - JHS generating methods too large

Migration From 10.1.2 to 10.1.3.1.26 (licensed)
Thanks for the previous fix. Now I have another problem. I get the following error:
Error(19,15): code segment of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) too large
When ViewController compiles.
This is a 10.1.2 application that I've migrated to 10.1.3.1.26. I had no problems with 10.1.2. How can method_jspService be too big?
The jspx file is a screen that has 8 sub-tabs. I haven't changed anything.
This screen is the heart of our application, any help on this problem would be appreciated.
Thanks!
Message was edited by:
user565025

I'm a colleague of the orignal poster above. I've been looking at this issue further and will summarize it here:
relevant threads:
Error with large / complex pages
Error: code segment of method _jspService(..) too large
Re: jspx Page size limit in ADF in JDeveloper environment 10.1.3.1 (Product
As far as I can tell the root cause is as described here:
http://publib.boulder.ibm.com/infocenter/wasinfo/v4r0/index.jsp?topic=/com.ibm.support.was.doc/html/Java_SDK/1177375.html
"The Java� specification states that there is a 64 K limit on the size of methods in Java. The JVM� does not execute methods that exceed this limit.
It is possible to compile methods larger than 64 K, but the JVM will not run these methods. Consequently, the error occurs during runtime, while attempting to execute Java methods that are greater than 64 K.
A code too large for try statement error can still be issued while compiling a JSP. The compiler limitation does not allow try/catch blocks to have a start or end location greater than 64 K into the method code. Therefore, compiler limitations are usually caught when a try/catch block overlaps the 64 K boundary.
The workaround is to refactor the code into smaller methods or try/catch blocks."
So it looks like Jheadstart is generating a file (see below) which violates the java spec. If I am correct then this is neither an oc4j, Sun or Jdeveloper problem; it's JHeadStart. I have tried setting the embedded server compiler and all project compilers to javac.
Any further suggestions or workarounds would be greatly appreciated.
Removed file listing - too long
Message was edited by:
JavaBat

Similar Messages

  • "Jump distance is too large and cannot be generated." in BI custom exit

    Hi folks,
    we got a mega include with plenty of BI exit variables as part of the EXIT_SAPLRRS0_001 (enhancement RSR00001 - BI: Enhancements for Global Variables in Reporting; /nsmod) and face now the following problem:
    "Jump distance is too large and cannot be generated." when activating the source.
    It seems we reached a certain limit of ABAP statements or LOC. How can we extend this limit
    or solve this challenge?
    Thx for your ideas!
    Cheers, Norbert

    Hi,
    I assume that you have used condition statements like if...endif.
    Every condition statement can hold only 32 KB of code. This issue can be resolved by modularizing the code or changing the logic in such a way that you dont hit the upper limit.
    Following this, you can definitely solve the issue.
    Thanks,
    Aravind.J

  • Page Too Large Error with JHS 10.1.3.2

    Hi,
    I have migrated to the new version of JHS (10.1.3.2). According to the JHS documentation the “page to large error” has been fixed in this version but I am still experiencing this problem.
    I have checked the boxes for Generate Group in Region File and Generate Search Area in Region File in the app def for the large page that I have in my app. With this done the “page too large” error occurs. I then tried checking the box for Generate in Region File on each item group region on my page but the “page too large” error still happens. None of my item group regions contain that many items (average is about 10 items).
    Is any one having the same issues?
    Regards
    Bar

    josealej,
    Have you spilt up your items into different regions and selected the option to generate the groups in a region file? If so then you can try setting the "generate in region file" option on each region container. Check out section 4.6.2 in the JHS developers manual.
    Sandra,
    Unfortunately I don't have enough free time to debug the problem. I will look into it when my schedule is not as hectic.
    Bar

  • Is there a reliable method for detecting that a query is too large?

    I am writing some code (that uses OCI) to properly detect when a query string is too long for OCI and/or the Oracle database server. I can't find any specific error code information in the docs, so I just started firing off large queries to see what would happen.
    The queries I am sending are >2MB in size, up to 16MB. If the queries are above ~10MB, I get the error "ORA-03113 'End-of-file on communications channel'" after a fairly short amount of time (i.e. not enough for a timeout to expire). If the queries are below ~10MB, but above ~2.5MB, it either just sits there and does not do anything (for more than 15 hours). So watching for ORA-03113 when executing large queries does not seem like a very reliable method for detecting the queries that are too large.
    Does anyone know of a reliable way of detecting that a query is too large for the OCI client and/or the Oracle database server?
    I am using version 10.2.0.1 for both the OCI client and the Oracle database server, but I'm getting similar errors for combinations of 10.2.0.1 and 9.2.0.7 for both the OCI client and the Oracle database server.
    These large queries need to be handled properly (i.e. distinguished from some generic failure) because the server handles requests from users, which could be programs that generate SQL queries (and have constructed huge ones in the past).
    Thanks for any information!

    The ORA-03113 means that the Oracle server process has died trying to satisfy your request. In almost all cases it is strictly correct to call that a bug, and we shouldn't easily forgive the server process when it happens. But in the case of multimegabyte statements my anger and disapointment turns to sympathy, for in my heart I can't bring myself to blame it. Can you?

  • How to solve "Error: code segment of method _jspService(...) too large"

    Hi, I am trying to compile a JSPX Page and I keep getting "Error: code segment of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) too large", in some Forums say that this Error is due to a Limit in the Size of Code that a Try/Catch Block can contain (64K), They suggest to remove such Blocks but I don't know how to do this in JDeveloper 10.1.3.2.0, some advice or suggestion?
    Thanks in Advance.
    PD: I cannot refactor the Code into different Pages.

    Hi,
    if I remember well then the problem is solved by setting the compiler used to JAVAC. This is a setting in the project properties
    Frank

  • Code too large Problem

    Hi,
       I am facing the problem of code too large in EP6 SP9 version and EP6 SP2 version. Is there a way to solve this problem.
    Is this problem solved in the latest version EP6 SP12.
    Please help me out in this regard.
    Thanks and Regards
    Padmaja.P

    I had this same problem, JSP code generated is too big.  I had the problem on SP11.  OSS Note 820282 tells you to change the jsp.bigmode.delimit.size = 10000.  This did not work for me.  I opened an OSS note about it.  They told me to set it to "1".  After that, it worked.  I took them 3 weeks to tell me to set it to "1", in the meantime,  I changed my <formlayout> tags to standard HTML,  to get around the problem.  I don't know if SP12 has fixed this issues or not.
    Regards,
    Rich Heilman

  • Jump distance is too large and cannot be generated.

    In smartforms the error  "Jump distance is too large and cannot be generated" is displayed .
    The detailed error desciption is :
    A jump distance is too large and cannot be generated.
    A control structure or a routine with "CHECK" or "EXIT" contains
    too many ABAP statements.

    Hi,
    Remove dummy portions in the smartform and then generate it again and check.
    If your smartform is with too many nodes and program lines then the error would occur.
    Regards,
    Ram

  • Jdeveloper jsp compile problem:too large

    I am getting following error when i try to run the jsp page(I am using embedded oc4j10.1.3.3)
    Error: code segment of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse) too large
    The jsp is over 2000 lines long.
    Any help would be appreciate.
    Thanks
    Kalee

    Hi,
    you can try and change the compiler to Javac
    Also you might want to think about jsp:includes that include JSP snippets from external files at compile time. A JSP with 2000 lines seems to be quite large and may better be broken up into pieces
    Frank

  • C4680 problem when printing incoming mail - too large a font. Have re-installed printer to no avail.

    Incoming mail font prints too large when printing out the message.  Have reinstalled the printer (twice) but the problem continues.  Can you assist please?

    sounds like the variable containing the barcode data is too short...is it at least 22 characters long?

  • ALTER SYSTEM SET processes=1000 generates ORA-00064: object is too large to

    Hi All
    I'm using Oracle Release 10.2.0.1.0.
    When performing:
    =============
    ALTER SYSTEM SET processes=10000 SCOPE=SPFILE;
    We can't start the 10g DB: ORA-00064: object is too large to allocate on this O/S (1,5282400)
    When reducing the size to 150 there is no problem starting the db. I can not start it. ORA-00064: object is too large to allocate on this O/S (1,5282400)
    I refered to ORA-00064: object is too large to allocate on this O/S :::Plz Help Me
    But I can not resolve this problem.
    Please help me.
    thiensu

    Not sure, because i haven't got ORA-00064 yet.
    ORA-00064: object is too large to allocate on this O/S num, num
    Cause: The initialization parameter DB_BLOCK_SIZE is set to a value that calls for more contiguous space than can be allocated on the operating system being used.
    Action: Reduce the value of DB_BLOCK_SIZE so that the requested contiguous space is within the capacity of the operating system.
    http://www.pitt.edu/~hoffman/oradoc/server.804/a58312/newch2a1.htm
    Regards
    Girish Sharma

  • Problem: backup is too large for the backup volume

    I am seeing the following message. Any hints as to what is going on?
    The backup is too large for the backup volume. The backup requires 711.1 MB but only 20.2 GB are available.
    To select a larger volume, or make the backup smaller by excluding files, open System Preferences and choose Time Machine.

    I fixed it. I think.
    Recipe:
    1. Logged in an an administrator (usually my work accounts are Standard)
    2. Ran Onyx utility (http://www.apple.com/downloads/macosx/systemdiskutilities/onyx.html)
    3. Noted that under "Scripts", the weekly and monthly scripts had not been run since before the problem began
    4. Ran weekly and monthly scripts
    5. Restarted Time Machine
    6. TM now correctly deleted my old backups, freeing about 30GB. It now correctly reports that my oldest backup is Feb 3 2008, previously it said Dec 27 2007.
    7. TM ran perfectly
    So it appears that there was some bad juju in the old caches cleared by the scripts. If this pops up again, I will report it here.

  • Problem upload too large file in a Content Area ORA-1401

    Hi All
    I have a customer who is trying to upload a file with a too large name in a content area.
    If the filename is 80 characters, it works fine.
    But if the filename is upper or 80 characters the following error ocurred:
    ORA-01401: inserted value too large for column
    DAD name: portal30
    PROCEDURE : PORTAL30.wwv_add_wizard.edititem
    URL : http://sbastida-us:80/pls/portal30/PORTAL30.wwv_add_wizard.edititem
    I checked the table: WWV_DOCUMENT and it have a column name: FILENAME is defined like VARCHAR2(350).
    If i run a query on this table, the filename column stores the filename of the file uploaded.
    Is this a new bug? may i fill this bug?
    Do you have any idea about this issue?
    Thanks in advance,
    Catalina

    Catalina,
    The following restrictions apply to the names of documents that you are uploading into the repository:
    Filenames must be 80 characters or less.
    Filenames must not include any of these characters: \ / : * ? < > | " % # +
    Filenames can include spaces and any of these characters: ! @ ~ & . $ ^ ( ) - _ ` ' [ ] { } ; =
    Regards,
    Jerry
    null

  • BUG: Web service returns request XML as response when result too large

    Hi,
    sorry for cross-posting, but the Web Services forum seems to be quite abandoned and this is an urgent issue for me.
    I have a web service returning some records of a given type (created using JDeveloper 10.1.3.3). The running environment and the service implementation do not seem to make any difference, as the situation is the same whether running it in embedded OC4J or in AS 10.1.3.1, and whether it is generated from a PL/SQL procedure or a method of a plain Java class.
    The problem is that if the result of this web service is too large (contains a lot of records), then the processing halts in some Oracle class in some web service library, so not in a debuggable generated web service source or in the service implementation itself.
    I think that the XML processing halts because of a "java.lang.OutOfMemoryError: Java heap space".
    Then a more serious problem follows: the service doesn't return a fault message but the original request XML as a response. Obviously, this can lead to some really unexpected errors.
    To reproduce this error:
    1. Create a Java class with a method returning an array of an arbitrary type, of the size specified in an input parameter.
    2. Create a web service from this class.
    3. Call it multiple times increasing the size parameter in every call until you get back the request as response or any error message.
    For example:
    - if you test the web service using the web page generated to access the endpoint, then you can see the response XML - in case you don't get an Internal Server Error (Java heap space).
    - if you use a generated web service proxy for testing, then it will give an error saying "unexpected element name: expected={namespace}someOperationResponseElement
    actual={namespace}someOperationElement".
    Any ideas how to locate / solve this problem?
    Regards,
    Patrik

    Patrik,
    the usual recommendation is to try with 10.1.3.3 instead of 10.1.3.1 to exclude you are hunting down an already fixed issue. From what you describe, the error seems less JDeveloper related than OC4J or OracleAs.
    So in case it reproduces in 10.1.3.3 I suggest to create a testcase and open a service request with support, or try the OC4J forum in case its known there.
    Frank

  • Requested buffer too large - but data is already in memory

    Hello all,
    I am writing a program that generates sound and then uses the Java Sound API to play it back over the speakers. Until recently, using clips have not led to any problems. On two computers I can play the sound without a hitch. However, on the newest computer (and also with the largest specs and especially more RAM), I am getting an error while trying to play back the sound. The exception that is thrown is:
    javax.sound.sampled.LineUnavailableException: Failed to allocate clip data: Requested buffer too large.
    I find this odd because the buffer already exists in memory: I don't have to read in a .wav file or anything because I am creating the audio during the course of my program's execution (this is also why I use Clips instead of streaming - the values are saved as doubles during the calculations and then converted into a byte array, which is the buffer that is used in the clip.open() method call). It has no problems allocating the double array, the byte array, or populating the byte array. It is only thrown during clip.open() call. I also find it strange that it would work on two other computers, both of which have less RAM (it runs fine on a machine with 512MB and 2GB of RAM, both XP 32-bit). The only difference is that the computer with the issue is running Windows 7 (the RTM build), 64-bit with 6GB of RAM. I am running it through Netbeans 6.7.1 with memory options set to use up to 512MB - but it's never gone up that far before. And I've checked the size of the buffer on all three computers and they are all the same.
    Does anyone know what the issue could be or how to resolve it? I am using JDK6 if that matters. Thank you for your time.
    Edited by: Sengin on Sep 18, 2009 9:40 PM

    Thanks for your answer. I'll try that.
    I figured it had something to do with Windows 7 since it technically hasn't been released yet (however I have the RTM version thanks to a group at my univeristy in cahoots with Microsoft which allows some students to get various Microsoft products for $12).
    Edit: I just changed the Clip to a SourceDataLine (and the few other necessary changes like changing the way the DataLine.Info object was created) and wrote the whole buffer into it, drained the line and then closed it. It works fine. I'll mark the question as answered, however that may not be the "correct" answer (perhaps it does have something to do with Windows 7 and not being completely tested yet). Thanks.
    Edited by: Sengin on Sep 21, 2009 8:44 PM
    Edited by: Sengin on Sep 21, 2009 8:46 PM

  • 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.

Maybe you are looking for