Release Build Failure - 18meg SWF, Heap Space Issue

I am trying to do a release build on a project that creates an 18 meg debug swf - specifically I am trying to embed a unicode font with asian character ranges (CJK Unified Ideographs).
I follow the steps outlined here to allocate more memory for compiling - http://livedocs.adobe.com/flex/3/html/help.html?content=configuring_environment_3.html
These are the results -
-Xmx512m (default) I get an error when attempting to build the app
> -Xmx512m the app builds with no error but is Zero KB. Furthermore, this seems to take longer than the default of -Xmx512m, as if it it's trying to complete the task, but it never does, it just produces a 0kb swf, and returns to the first export screen as if i never hit "finish" in the first place
Is there an alternative method to compiling larger applications?

Hi Shane,
Can you please try downloading Flash Builder 4.7 64 bit from http://labs.adobe.com/technologies/flashbuilder4-7/
Open FlashBuilder.ini file from the installed directory example (C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)/FlashBuilder) and
if you are on Mac go to /Applications/Adobe Flash Builder 4.7/Adobe Flash Builder 4.7.app/Contents/MacOS and set your -Xmx to 1024 and try packaging. If this doesn't solve increase you -Xmx to 2048.
Please let me know if this works.
-Hari

Similar Messages

[svn] 4488: Attempt to fix the heap-space issue with the doc target.

Revision: 4488
Author: [email protected]
Date: 2009-01-12 12:10:58 -0800 (Mon, 12 Jan 2009)
Log Message:
Attempt to fix the heap-space issue with the doc target.
Also removing some unused code.
QE Notes: None
Doc Notes: None
tests: checkintests
Modified Paths:
flex/sdk/trunk/frameworks/projects/airframework/build.xml
flex/sdk/trunk/frameworks/projects/flash-integration/build.xml
flex/sdk/trunk/frameworks/projects/flex/build.xml
flex/sdk/trunk/frameworks/projects/flex4/build.xml
flex/sdk/trunk/frameworks/projects/framework/build.xml
flex/sdk/trunk/frameworks/projects/haloclassic/build.xml
flex/sdk/trunk/frameworks/projects/rpc/build.xml
flex/sdk/trunk/frameworks/projects/utilities/build.xml
flex/sdk/trunk/frameworks/projects/wireframe/build.xml
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
Removed Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/PumpStreamHandler.java

1. Tell more about it, e.g.: OS, a sun jdk or a ibm jdk? 32-bit or 64-bit?
for ibm jdk, look for *.hpd file within the dir.
for sun jdk, add startup option -XX:+HeapDumpOnOutOfMemError
Then analyze them with heap analyzer.
2.MaxPermSize=1024m so big space for class files, really necessary?

Flash Builder 4.5 Java Heap Space Error

Hello everyone,
I've downloaded Flash Builder 4.5 trial a few days ago. Let me first tell that I like the new features a lot and they help to speed up the development process noticably. I thank Adobe for that very much.
However I did not notice any performance boost over the Flash Buidler 4. Even worse, the 4.5 version seems to run much slower and use more memory than Flash Builder 4. I constantly keep getting Java Heap Space errors and needles to say, the tool just crashes and I have to restart it.
Here how my experience working with the new version looks like. I start the Flash Builder 4.5 which has my current project open (for the record, I still use Flex 4.1, and the project includes roughly 300+ classes and 30000+ lines of code (AS and MXML)). At the beggining everything works fine and pretty fast. UI, code completion, snippets and all other good stuff works pretty fast. However, after each build, FlashBuilder.exe process eats up from 50 to 100 megabytes of memory and does not seem to release it or reuse it. So after a 5 or 10 builds it already appears to be using over 1 GB of RAM. At that point the editor becomes sloppy - it can't keep up with my typing, code completion popups takes a few seconds to show up. And a few more builds - the Flash Builder freezes and after a minute or two I get Java Heap Space error.
I've tried increased the JRE heap space used by the Flash Builder (flashbuilder.ini, flashbuilderc.ini, eclipse.ini) to -Xms512m -Xmx1024m as well as permanent generation heap space to -XX:MaxPermSize=512m -XX:PermSize=256m and the mxml compiler (jvm.config) to -Xms384m -Xmx768m. However this did not solve the problem. Maybe just postponed it a bit.
Am I the only one observing such behaviour of Flash Builder 4.5? Does any one have any other ideas how to fix this? (by the way, I work on 64bit machine with Widnows Server 2008R2, 4GB of RAM and 2.66 GHz Intel Core 2 Duo).
Thanks in advance.
Michael

I'm seeing nearly the same thing. I also have a very large set of projects similar to what you are describing and I do have Java Heap Space errors (The details show an error of "java.lang.OutOfMemoryError: unable to create new native thread" occurring for me)
I had similar issues, although they are more frequent in the 4.5 builder, in the 4.1 builder. In 4.1 builder, I didn't get the exact same detailed error regarding threads.
I did install my flash builder into a clean instance of eclipse 3.6.2 vs using the standalone install. That shouldn't make a difference though. In 4.1, I tried he standalone install and saw the same issues I saw in the plugin version.
I'm also using the 4.1 SDK in Flash Builder 4.5 (It appears that is what you are doing). I've been attributing the crashes to the following bug in the 4.1 SDK, although I have applied the files in the bug report and still have the problem. I'm hoping when I'm able to switch to the 4.5 SDK it may help. (I can't switch yet because from what I can tell, it requires 10.2 Flash Player and my company is currently only on 10.0)
The Bug Report I'm referring to is: https://bugs.adobe.com/jira/browse/SDK-26366
I've bumped up all of the memory settings you've referred to and it helps the environment run longer, but it still eventually crashes. One thing I definately do is make sure that the "Build Automatically" is unchecked.
The machine I'm running on is an Intel 2600K with 16GB of memory running Windows 7 64-bit, so I don't think hardware is the issue.
No real answer, but your not alone in having similar issues.
Jon

Flash Builder 4.6 Java Heap Space Error

Hi,
I get this error "Java Heap Space" when trying to clean build (or build in any way) my project.
I have a lot of embeded assets (png, mp3 and some binary files embeded to be read as a ByteArray) which total about 37 MB. Including one more 1.6MB binary asset causes this error to occur.
I have tried to change my memory settings about (-Xmx and -Xms) as previous posts have suggested but this doesn't seem to make any difference.
Is there any patch or solution to this very frustrating limitation of Flash Builder?
Thanks for any help!
Tom

I constantly had issues with this. I managed to run into the max for increasing the heap space. I was able to get beyond the limit by flagging the FlashBuilder.exe file to allow it to allocate to higher memory address ranges. I'm on a 64 bit machine, so the only limitation was the 32 bit FlashBuilder process. Anyways i was able to get from 1024m up to 1720m. Also note that FlashBuilder 4.7 Beta is out and it is a native 64 bit application, so you will get higher addressing there. I just found it to be too buggy for my every day development tasks. Also missing the Design view really hurts development. I hope they put that back in.
Here's more detail on how I got beyond the java heap ceiling.
http://chrsmrtn.azurewebsites.net/flash-builder-java-heap-errors-limitations-of-xms-and-xm x/

Java Heap Space Issues

Greetings. I hope this is the right forum
I have a project, a chess program, that makes use of some very large static arrays. As I experiment with increasing the size of the arrays, I eventually run into heap space out of memory errors when instantiating these arrays.
My research has suggested various ways of adjusting the amount of memory available to the Java Runtime Environment. I am pretty sure I can deal with that.
My comment is that there does not appear to be a way to deal with this programmatically, from within my program. I'd like to make my program available on the web in applet form. If I do so it appears that I have to either limit the size of my arrays, or else instruct any potential user to adjust JVM settings themselves, outside of my program. Do I have this right?
Thanks.

ok I know nothing about jnlp but this looks promising. The following quote from that page suggests to me a way to package my program, with a minimum of modification, so that resources are allocated to the JVM before the application is loaded. The point being that the end user doesn't need to manually adjust the settings. Thanks, I'll give it a try.
By default, jar and nativelib resources will be downloaded eagerly, i.e., they are downloaded and available locally to the JVM running the application before the application is launched. The jar and nativelib elements also allow a resource to be specified as lazy. This means the resource does not have to be downloaded onto the client system before the application is launched.

Flash Builder 4.5 crashes frequently with heap space error

We have a reasonably complex AIR application, but by and large I would not say it is enormous. It compiles down to an AIR file that is around 6MB. It is broken out into about 6 different modules. We have given the java VM the maximum RAM that it will utilize without complaining (somewhere around 768MB. You can't go to 1024MB or it blows up). Yet, Flash Builder crashes very frequently when trying to build, generally with "java heap space" errors. We are developing on Windows 7.
I had hoped Flash Builder 4.5 would be an improvement over Flash Builder 4 in this regard. It in fact got worse.
Is there any hope of seeing action on this?
Kevin

Hi Kevin,
Eliminating this completely is definitely on our radar and a high priority.
For now, there are a couple of things you can do to reduce the occurence of out of memory errors when building:
1. Move all embedded fonts and images into an AS class in a library project.
2. Edit the file: C:\Program Files\Adobe\Adobe Flash Builder 4.5\eclipse\plugins\com.adobe.flexbuilder.project_4.5.1.313231\.options in wordpad. Setting, useGlobalSwcCache and useApplicationCache to false will reduce the overall memory consumed, but decrease performance.
P.S: Please note that 2 is not officially supported or tested. If those options were, they would have been in preferences.
-Anirudh

Exporting release build

In flash builder I am targeting flash player 9 and use actionscript project.
I see some strange behavior. I created my design in Photoshop CS3, then I imported .psd file in Flash CS3 and exported as SWC file. I added this SWC in Reference libraries in Flash Builder. If I run my project in Flash Builder - all is working and graphics objects are smooth and clean. But if I export release build, upload the SWF to server and run my website - I see jerky low quality graphics objects. Please help, any pointing very appreciated.

problem solved, problem was in embeding on web with swfObject

Command Line Build - Java heap space error

I'm attempting to build a Flex app via the command line. Even though the build works fine from within the Flash Builder IDE, I get the following error when I attempt to build via the command line
C:\code\software\web_stuff>"C:\Program Files\Adobe\Adobe Flash Builder Beta 2\FlashBuilderC.exe" --launcher.suppressErrors -noSplash -application org.eclipse.ant.core.antRunner -data "C:\code\software\web_stuff" -file C:\code\software\web_stuff\build.xml WebControlBrowser
Buildfile: C:\code\software\web_stuff\build.xml
WebControlBrowser:
[fb.exportReleaseBuild] Compiling 1 application to C:\code\software\web_stuff\WebControlBrowser\bin-release...
[fb.exportReleaseBuild] Exception in thread "Code Model Worker" java.lang.OutOfMemoryError: Java heap space
[fb.exportReleaseBuild]         at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:404)
[fb.exportReleaseBuild]         at org.eclipse.core.runtime.Plugin.getLog(Plugin.java:282)
[fb.exportReleaseBuild]         at com.adobe.flexbuilder.codemodel.internal.bridge.WorkspaceSpecification.log(WorkspaceS
pecification.java:136)
[fb.exportReleaseBuild]         at com.adobe.flexbuilder.codemodel.internal.parsing.ASTokenizer.parseTokens(ASTokenizer.
java:386)
[fb.exportReleaseBuild]         at com.adobe.flexbuilder.codemodel.internal.search.SWCSearchDataProvider.indexFiles(SWCS
earchDataProvider.java:440)
[fb.exportReleaseBuild]         at com.adobe.flexbuilder.codemodel.internal.search.SWCSearchDataProvider$2.run(SWCSearch
DataProvider.java:364)
[fb.exportReleaseBuild]         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
[fb.exportReleaseBuild]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[fb.exportReleaseBuild]         at java.lang.Thread.run(Unknown Source)
BUILD FAILED
C:\code\software\web_stuff\build.xml:4: java.lang.OutOfMemoryError: Java heap space
Total time: 1 minute 0 seconds
FlashBuilderC:
An error has occurred. See the log file
C:\code\software\web_stuff\.metadata\.log.
I've attached the .log file that is referenced.

Why isn't this documented somewhere? or if it is why isn't it easy to find?
This link ought to have a link to common issues people run into.
I just spent an hour trying to solve this same problem. FlashbuilderC.exe wouldn't even work on very small projects until I found this post, so thanks.

Issues exist in release build that don't exist in debug build

I've been working on a Flex 4.1 project and have recently noticed an issue that does not exist in the debug build. Then when you export a release build and run it the issue appears. This is the only change that's made that breaks it. To me this seems to be a bug in the player, SDK, or compiler that I might need to post, but I figured I'd submit it here in case I'm missing something.
Basically it seems to be an issue with objects in an ArrayCollection being instantiated as the correct class type before being added.
When in debug mode, if you set a breakpoint to view the objects in the ArrayCollection you will see them appropriately as their Strongly Typed class. However, when the release mode build is run it will throw an RTE on that same line indicating that the ArrayCollection members are ObjectProxy and they can't be cast into their Strongly Typed class.
Here's the RTE that happens and right now I just need to know if I'm missing something, or if this looks like a bug, and to which bugbase it should be posted (Flash Player, Flex SDK, Flex Compiler, etc.)
TypeError: Error #1034: Type Coercion failed: cannot convert mx.utils::ObjectProxy@28250141 to
<confidential package path>.PlayerPageSummary.
    at <confidential package path>.service::InitializeStorefrontServiceResponseCommand/execute()
    at org.robotlegs.base::CommandMap/execute()
    at org.robotlegs.base::CommandMap/routeEventToCommand()
    at MethodInfo-1674()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at <confidential package path>::<confidential acronym>ModuleActor/dispatchLocal()
    at <confidential package path>.live::InitializeStorefrontService/result()
    at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()
    at mx.rpc.events::ResultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
    at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
    at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()
    at mx.rpc::Responder/result()
    at mx.rpc::AsyncRequest/acknowledge()
    at DirectHTTPMessageResponder/completeHandler()
    at flash.events::EventDispatcher/dispatchEventFunction()
    at flash.events::EventDispatcher/dispatchEvent()
    at flash.net::URLLoader/onComplete()

Alex,
Thanks for your help and here's an update on this from me. We did try out your suggestion to see if "PlayerPageSummary can be retrieved via getClassAlias". I'm not the one that did the testing, but my teammate who did, said that the class being registered was not the issue.
While he was working on that I further investigated our ANT builder and configuration to see what might have been different between ANT building non-debug SWF and Flash Builder building non-debug SWF. Turns out that my teammate had added some [ArrayElementType] metadata that I was not aware of. Once I realized that, I added it as metadata to be kept in my flex-config.xml which ended up solving the debug vs. release mode issues.
Afterwards, I double-checked the livedocs and also did some Googling. From the above it appears that debug SWF keep all metadata without you needing to explicitly tell it to. On the other hand, outside of a handful of metadata tag such as [Bindable] release builds neeed to be told what to keep.
Does this sound right?
Also, do you know off the top of your head if this is documented by Adobe anywhere and what the link is? I had a real tough time finding anything mentioning how debug SWF retain all metadata.
Thanks again for your help!

How do I get my external swf to load in the release build?

My external swf loads in the debug build, but not in the release build. How can this be fixed?
Thanks,
Doug

After exporting the Flex project on my Macintosh, then importing it on my PC, then rebuilding the relase
build, it works. Probably some "path" issues between Mac and PC.
Doug

Flex: Actionscript project swf is not working after export the release build...

Hi guys..
   I tried to built a project with AS3 only in Flex. When I run the project in flex, everything looks fine, but when I export the release build, the images that are supposed to be added are gone. I appreciate if someone can help me about it.
          init();
            public function init(loadedVideoCount:Number):void{
            singleHolder=new singleVideoCont();
            singleHolder.x=loadedVideoCount*singleHolder.width+2;
            singleHolder.y=6;
            singleHolder.buttonMode=true;
            addChild(singleHolder);
            this.addEventListener(MouseEvent.CLICK,onClick);
            showTn();
        private function showTn():void{
                imgLoader = new Loader();
                imgLoader.load(new URLRequest(_tnPath));
                        imgLoader.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS,onProgress);
    imgLoader.contentLoaderInfo.addEventListener(Event.COMPLETE,onImgLoaded);
        private function onImgLoaded(event:Event):void {
        singleHolder.progBar.alpha = 0;
               var image:Bitmap = imgLoader.contentLoaderInfo.content as Bitmap;
                image.width=TN_WIDTH;
                image.height=TN_HEIGHT;
                image.x=3;
                image.y=3;
                singleHolder.addChild(image); //this line work when I run the project inside flex but the images are gone when I test my release build...
                imgLoader.contentLoaderInfo.removeEventListener(ProgressEvent.PROGRESS,onProgress);
                imgLoader.contentLoaderInfo.removeEventListener(Event.COMPLETE,onImgLoaded);
                //imgLoader = null;

The link you provided is to the SWF file, not to an HTML
file, so no one can test your HTML file.
Have you checked the code for the embedding of the SWF file
in your HTML file? I don't use Dreamweaver much, but I do know that
if you start assembling a Dreamweaver file without first saving the
HTML, embedded graphics and other items are inserted as direct
links to the files on your computer, rather than as relative paths.
There is one other possible issue: I note that your swf is
called CWABanner.swf. Depending on your FTP settings, it is
possible that your server is forcing all file names to lower case
(a common practice). Which means the file on your server will be
cwabanner.swf. Again, depending on how the web server is set up, if
it is case sensitive, it will treat CWABanner and cwabanner as
separate files. So if the HTML calls CWABanner.swf, but the FTP
upload has forced a rename to lower case to cwabanner.swf, the HTML
file will not find it. Check this out, or to be absolutely certain,
rename everything to lower case: the file name itself and the
reference in the HTML file.

BI XML Publiser Issue java langOutOfMemoryError Java heap space

Hi
I am getting 'java.lang.OutOfMemoryError: Java heap space' error in XML publisher report. Just i am running 15MB data report still its giving OutOfmemory issue.
Please help on this.
[5/22/12 9:08:00 AM] [98639:RT12903275] XML Publisher post-processing action complete.
[5/22/12 9:08:01 AM] [98639:RT12903275] Completed post-processing actions for request 12903275.
[5/22/12 10:20:15 AM] [OPPServiceThread1] Post-processing request 12903281.
[5/22/12 10:20:19 AM] [98639:RT12903281] Executing post-processing actions for request 12903281.
[5/22/12 10:20:19 AM] [98639:RT12903281] Starting XML Publisher post-processing action.
[5/22/12 10:20:19 AM] [98639:RT12903281]
Template code: XXGFS_AP_APMCGRN
Template app: XXGFS_AP
Language: en
Territory: US
Output type: EXCEL
Exception: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
     at oracle.jdbc.dbaccess.DBItem.allocBuffer(DBItem.java:204)
     at oracle.jdbc.dbaccess.DBItem.allocBuffer(DBItem.java:232)
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocItemsAndBuffers(DBDataSetImpl.java:300)
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocDataAndItems(DBDataSetImpl.java:261)
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java:2068)
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java:1951)
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameterBytes(OracleCallableStatement.java:278)
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java:402)
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java:477)
     at oracle.apps.fnd.cp.gsm.GenCartComm.getQueueMessage(GenCartComm.java:185)
     at oracle.apps.fnd.cp.gsf.GSMStateMonitor.waitForNextEvent(GSMStateMonitor.java:95)
     at oracle.apps.fnd.cp.gsf.GSMServiceController.mainLoop(GSMServiceController.java:236)
     at oracle.apps.fnd.cp.gsf.BaseServiceController.run(BaseServiceController.java:71)
     at java.lang.Thread.run(Thread.java:619)
Exception in thread "Cache Stats Writer" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "OPPAQMON:98639" java.lang.OutOfMemoryError: Java heap space
     at oracle.jdbc.dbaccess.DBItem.allocBuffer(DBItem.java:204)
     at oracle.jdbc.dbaccess.DBItem.allocBuffer(DBItem.java:232)
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocItemsAndBuffers(DBDataSetImpl.java:300)
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocDataAndItems(DBDataSetImpl.java:261)
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java:2068)
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java:1951)
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameterBytes(OracleCallableStatement.java:278)
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java:402)
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java:423)
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:113)
     at java.lang.Thread.run(Thread.java:619)
[5/22/12 10:24:36 AM] [UNEXPECTED] [98639:RT12903281] java.lang.OutOfMemoryError: Java heap space

user972966 wrote:
There are two tables (tableA, tableB) in two different databases. They both have almost same schema/structure. There is mapping between tables on their columns.
I need to develop a Java application to compare data value between these two tables for a time frame (for example one day) and find missing records or mismatch data.
The volume of data, even for one day, is huge; almost 70M, 100M. Do you mean this many records? or this many MB. either way they are not that big for Java. If you have collections of up to 2 billion entries, you won't have a problem.
>
I have tried to use Thread to split the comparison process in 10 threads. Each thread is fetching portion of data from both tables (for example 7M each) and processing portion them. The issue that I am facing is, I am getting following exception after running:I would suggest you get the program working with one thread first. You will find this is simpler and possibly even faster. Having 10 threads isn't guarenteed to be faster.
>
To compare the data, I am fetching data from tableA and add it into List<MyDataObject> listA (the MyDataObject represent a one row data. It is a java bean) and then I am fetching data from tableB and add it into List<MyDataObject> listB
And then I compare the lists.
It seems there is limitation in size of List and I cannot add many elements to a List object, it’ll throws Out of Memory exception. The limit is 2^31-1. However an Out of Memory error means what it says. You are out of heap space, so you need to either increase it, or use less memory.
>
This method works for small volume, but for large one I get that exceptionIs there any reason you cannot divide the problem so you can process a small volume at a time?

10Mb .swf compilation - OutOfMemoryError: Java heap space...

When I try to compile my 10Mb .swf with the "-Xmx1024m" setting in pfi.bat I getting:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
      at java.util.Arrays.copyOf(Unknown Source)
      at java.io.ByteArrayOutputStream.write(Unknown Source)
      at java.io.OutputStream.write(Unknown Source)
      at adobe.abc.GlobalOptimizer.emitAbc(GlobalOptimizer.java:2670)
      at adobe.abc.GlobalOptimizer.emit(GlobalOptimizer.java:2594)
      at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:320)
      at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:172)
      at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcode(AOTCompiler.java:329)
      at com.adobe.air.ipa.AOTCompiler.GenerateMacBinary(AOTCompiler.java:600)
      at com.adobe.air.ipa.IPAOutputStream.compileRootSwf(IPAOutputStream.java:196)
      at com.adobe.air.ipa.IPAOutputStream.finalizeSig(IPAOutputStream.java:366)
      at com.adobe.air.ADTPackager.createPackage(ADTPackager.java:65)
      at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:165)
      at com.adobe.air.ADTEntrypoint.parseArgsAndGo(ADTEntrypoint.java:132)
      at com.adobe.air.ipa.PFI.parseArgsAndGo(PFI.java:152)
      at com.adobe.air.ADTEntrypoint.run(ADTEntrypoint.java:68)
      at com.adobe.air.ipa.PFI.main(PFI.java:112)
When I increase try jave heap from "-Xmx1024" to "-Xmx1200" or more memory for jave heap I stable getting:
# A fatal error has been detected by the Java Runtime Environment:
# Internal Error (0xe06d7363), pid=3796, tid=3048
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode windows-x86 )
# Problematic frame:
# C [kernel32.dll+0x12afb]
# An error report file with more information is saved as:
# C:\svn\xxx\components\xxx\output\hs_err_pid3796.log
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Compilation process looks like this:
Have anybody idea how can I compile my .swf? Thanks.

Hi Joseph,
I'm having the same problem with CWLMS 4.0.1. But I didn't find this file heap.properties in the
/opt/CSCOpx/MDc/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/cli/framework/
Do you know where I customize this parameter in that version?
Thanks,
Patricia Oliveira

Production Issue heap space error. Getting ERROR 503 Service not deployed

Hi,
I have deployed my web services (VAS services) in tomcat 6.0 in production .I am using axis2 1.4.1 as web service engine and apache 2.2 for httpd service. My problem is that in every 8-10 hrs when no of transactions increase, a problem occurs in my server and I get an ERROR 503 service not deployed. I dont know the exact cause and solution to this problem. Presently every time I face this problem, I restart my httpd services and tomcat. Please help me to rectify this problem as this is hampering our business in a big way. I am sending the log details of catalina.log in tomcats log folder
17-Nov-2008 17:20:56 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet AxisServlet threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet AxisServlet threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:21:33 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet AxisServlet threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:21:36 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
at java.lang.Thread.run(Unknown Source)
17-Nov-2008 17:21:36 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet AxisServlet threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:23:31 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:23:31 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
at java.lang.Thread.run(Unknown Source)
17-Nov-2008 17:23:31 org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:531)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
at org.apache.jk.core.MsgContext.action(MsgContext.java:301)
at org.apache.coyote.Response.action(Response.java:183)
at org.apache.coyote.Response.finish(Response.java:305)
at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:276)
at org.apache.catalina.connector.Response.finishResponse(Response.java:486)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:285)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
at java.lang.Thread.run(Unknown Source)
17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
at org.apache.catalina.connector.Response.getWriter(Response.java:604)
at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:186)
at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118)
at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77)
at org.apache.jsp.axis2_002dweb.Error.error500_jsp._jspService(error500_jsp.java:110)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654)
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447)
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292)
at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424)
at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343)
at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:287)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:686)
at java.lang.Thread.run(Unknown Source)
17-Nov-2008 17:23:34 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError: Java heap space
17-Nov-2008 17:23:34 org.apache.catalina.core.ApplicationDispatcher invoke
Regards,
Paritosh
Edited by: anshu_299 on Nov 18, 2008 9:39 AM

Hi,
503 error comes when the client finds that the target server is not running or accessible.
Is the java system up and running? Check if the server nodes are up ?
check for the logs in work dir and if only server node is not coming up then check for default traces.
Amit.

Missing mxml:html/swf in Export Release Build

Hi,
I am using Flex 3 and have created several projects of which two have dropped the login.mxml (resulting html and swf) files when I export release build and publish it to my web server. I have compared settings in the projects where this does not happen and I can't find a reason for this behaviour. Its very annoying as I have to remember to manually copy the files from the flex_bin manually over. Anyone else encounter this or know why it might be happening?

Hi,
I am using Flex 3 and have created several projects of which two have dropped the login.mxml (resulting html and swf) files when I export release build and publish it to my web server. I have compared settings in the projects where this does not happen and I can't find a reason for this behaviour. Its very annoying as I have to remember to manually copy the files from the flex_bin manually over. Anyone else encounter this or know why it might be happening?

Release Build Failure - 18meg SWF, Heap Space Issue

Similar Messages

Maybe you are looking for