Photoshop running out of memory on fast system

Hi!
I use Photoshop CC on a Win7 System with 16GB RAM and 8Cores (x2,11Ghz)
Since some days, let it be the last update, any of the operations that before have never been a problem suddenly get memory errors.
I cant work like that, i have architectural images with several layers to blend and how can i explain a customer i cant hold a deadline because my
expensive and world leading software isn´t able even to save the workfile without running out of memory??
If it´s a problem with my hardware ok, but if it´s somehow  softwarebased, please correct that an pop another update- i don´t want to swap to Gimp

I don´t know why excactly, but now it is working again.
I reinstalled some plugins and now it seems to be ok.
Thank´s for the effort

Similar Messages

  • System running out of memory

    I have deployed a Windows Embedded Standard 7 on a x64 machine. My answer file includes the File Based Write Filter and my system has 8GB RAM installed. I have excluded some working folders for a specific software and other than that no big change would
    happen in the system. I have set the overlay size of FBWF to be 1GB.
    Now my problem is that after the system works for some time, the amount of free memory starts to decline and after around 7-8 hours the available memory reaches a critical amount and the system is unusable and I have to reset the system manually. I have
    increased the size of the overlay to 2GB but this happens again.
     Is it possible that this problem is due to FBWF? If I set the overlay size to be 2GB the system should not touch any more than that 2GB so I would never run out of memory with 8GB installed RAM. am I right?

    Would you please take a look at my situation and give me a possible diagnosis:
    1- I have "File Based Write Filter" on Windows Embedded Standard 7 x64 SP1.
    2- The installed RAM is 8GB and size of overlay of FBWF is set to 2GB.
    3- When the system is giving the critical memory message the conditions are as follows:
    a) The consumed memory in task manager is somewhere around 4 to 4.5 GB out of 8GB
    b) A process schedule.exe (from our software) is running more than a hundred time and is consuming
    memory,
    but its .exe file is located inside an unprotected folder.
    c) executing fbwfmgr.exe /overlaydetail is reporting that only 135MB of overlay volume is full!
    Memory consumed by directory structure: 35.6 MB
    Memory consumed by file data: 135 MB
    d) The CPU usage is normal
    I don't know what exactly is full? Memory has free space, FBWF overlay volume has free space, then which memory is full?
    p.s.: I checked my answer file and paging file is disabled as required.

  • System hanging when it runs out of memory

    Hello,
    my system has a finite amount of RAM and swap (it doesn't matter, to my purpose, if it's 16GB or 128MB, I'm not interested in increasing it anyway).
    Sometimes my apps completely use all the available memory. I would expect that in these cases the kernel kills some apps to keep working correctly. The OOM Killer exists just for this, doesn't it?
    What happens, instead, is that the system hangs. Even the mouse stops working. Sometimes it manages to get back to life in a few seconds/minutes, other times hours pass by and nothing changes.
    I don't want to add more memory, I just want that the kernel kills some application when it's running out of memory.
    Why isn't this happening?
    Right now I'm writing a bash script that will kill the most memory-hungry process when available memory gets below 10%, because I'm sick of freezing my machine.
    But why do I have to do this? Why do I need an user space tool polling memory usage and sentencing applications according to a cheap policy? What the hell is wrong with my OOM Killer, why isn't it doing is job?!

    Alright, you won, now quit pointing out my ignorance
    Your awkish oom killer is a lot cooler than mine, switching to it, thanks!
    I did some testing (initially just to test the oom killing script) and found out that if a program tries to allocate all the memory it can, it gets eventually killed by linux's oom killer. If instead it stops allocating new memory when there are less than 4MB of free memory (or similar values) the OOM won't do anything, and the system will get stuck, like if a forkbomb was running.
    That's it, this program with MINSIZE=1 will be killed, while with MINSIZE=4MB will force me to hard reboot:
    #include <string.h>
    #include <stdlib.h>
    #define MINSIZE (1024*1024*4) // 4MB
    int main( )
    int block = 1024*1024*1024; // 1GB
    void *p;
    while( 1 ) {
    p = malloc( block );
    if( p ) {
    memset( p, 85, block );
    else if( block > MINSIZE ) {
    block /= 2;
    return 0;
    Guess I'd need to go deeper to understand why Linux' oom killer works like that, but I won't (assuming the oom killing script will behave).

  • Lightroom 5 permanently runs out of memory

    Lightroom 5 on Windows 7 32 Bit and 8 Gigabytes of memory (more than the 32 Bit system can use) permanently runs out of memory when doing some more complex edits on a RAW file, especially when exporting to 16 Bit TIFF. The RAW files were created by cameras with 10 up to 16 megapixel sensors with bit depths between 12 and 14.
    After exporting one or two images to 16 Bit uncompressed TIFF an error message "Not enough memory" will be displayed and only a Lightroom restart solves that - for the next one to two exports. If an image has much brush stroke edits, every additional stroke takes more and more time to see the result until the image disappears followed by the same "Not enough memory" error message.
    A tab character in the XMP sidecar file is *not* the reason (ensured that), as mentioned in a post. It seems that Lightroom in general does not allocate enough memory and frees too less/late allocated.
    Please fix that bug, it's not productive permanently quit and restart Lightroom when editing/exporting a few RAW files. Versions prior to Lightroom 4 did not have that bug.
    P.S. Posting here, because it was not possible to post it at http://feedback.photoshop.com/photoshop_family/topics/new It's very bad design, to let a user take much time to write and then say: "Log in", but a log in with the Adobe ID and password does not work (creating accounts on Facebook etc. is not an acceptable option, Adobe ID should be enough). Also a bugtracker such as Bugzilla would be a much better tool for improving a software and finding relevant issues to avoid duplicate postings.

    First of all: I personally agree with your comments regarding the feedback webpage. But that is out of our hands since this is a user-to-user forum, and there is nothing we users can do about it.
    Regarding your RAM: You are running Win7 32-bit, so 4 GB of your 8 GB of RAM sit idle since the system cannot use it. And, frankly, 4 GB is very scant for running Lr, considering that the system uses 1 GB of that. So there's only 3 GB for Lr - and that only if you are not running any other programs at the same time.
    Since you have a 8 GB system already, why don't you go for Win7 64-bit. Then you can also install Lr 64-bit and that - together with 8 GB of RAM - will bring a great boost in Lr performance.
    Adobe recommends to run Lr in the 64-bit version. For more on their suggestion on improving Lr performance see here:
    http://helpx.adobe.com/lightroom/kb/performance-hints.html?sdid=KBQWU
    for more: http://forums.adobe.com/thread/1110408?tstart=0

  • How can I avoid running out of memory when creating components dynamically

    Hello everyone,
    Recently, I am planning to design a web application. It will be used by all middle school teachers in a region to make examination papers and it must contain the following main functions.
    1)Generate test questions dynamically. For instance, a teacher who logs on the web application will only see a select one menu and a Next Quiz button. The former is used for determining the number of options for the current multiple/single choice question. The later is dedicated to creating appropriate input text elements according to the selected option number. That is to say, if the teacher selects 4 in the menu and presses the Next Quiz button, 5 input text form elements will appear. The first one is for the question to be asked such as "1.What is the biggest planet in the solar system?", the others are optional answers like a)Uranus. b) Saturn. c)Jupiter. d)Earch. Each answer stands for an input text elements. When the teacher fills in the fourth answer, another select one menu and Next Quiz button will emerge on the fly just under this answer, allowing the teacher to make the second question. The same thing repeats for the following questions.
    2)Undo and Redo. Whenever a teacher wants to roll back or redo what he has done, just press the Undo or[i] Redo button. In the previous example, if the teacher selects the third answer and presses the Delete button to drop this answer, it will delete both the literal string content[i] and the input text element, changing the answer d to c automatically. After that, he decides to get back the original answer c, Jupiter, he can just click the Undo button as if he hadn�ft made the deleting operation.
    3)Save the unfinished working in the client side. If a teacher has done half of his work, he can choose to press the Save button to store what he has done in his computer. The reason for doing so is simply to alleviate the burden of the server. Although all finished test papers must be saved in a database on the server, sometimes the unfinished papers could be dropped forever or could form the ultimate testing papers after several months. So if these papers keep in the server, it will waste the server computer�fs room. Next time the teacher can press the Restore button on the page to get the previously stored part of the test paper from his own computer and continue to finish the whole paper.
    4)Allow at least 1,000 teachers to make test papers at the same time. The maximum question number per examination paper is 60.
    Here are my two rough solutions,
    A.Using JSF.
    B.Using JavaScript and plain JSP[b] without JSF.
    The comparison of the two solutions:
    1)Both schemas can implement the first and the second requirements. In JSF page I could add a standard panelGird tag and use its binding attribute. In the backing bean, the method specified by the binding attribute is responsible for generating HtmlInput objects and adding them to the HtmlPanelGird object on the fly. Every HtmlInput object is corresponding to a question subject or an optional answer. The method is called by an actionListener, which is registered in the Next Quiz commandButton, triggering by the clicking on this button in the client side. Using JSF can also be prone to managing the HtmlInput objects, e.g. panelGird.getChildren().add(HtmlInput) and panelGird.getChildren().remove(HtmlInput) respond to the undoing operation of deleting an optional answer and the redoing operation of the deleting action respectively. I know JavaScript can also achieve these goals. It could be more complex since I don�ft know well about JavaScript.
    2)I can not find a way to meet the third demand right now. I am eager to know your suggestion.
    3)Using JSF, I think, can�ft allow 1,000 teachers to do their own papers at the same time. Because in this scenario, suppose each questionnaire having 60 questions and 4 answers per question, there will be approximately 300,000 HtmlInput objects (1,000X60X(4+1)) creating on the server side. The server must run out of memory undoubtedly. To make things better, we can use a custom component which can be rendered as a whole question including its all optional answers. That is to say, a new custom component on the server side stands for a whole question on the client side. Even so, about 60,000(1,000X60) this type of custom components will be created progressively and dynamically, plus other UISelectOne and UICommand objects, it also can�ft afford for most servers. Do I have to use JavaScript to avoid occupying the server's memory in this way? If so, I have to go back and use JavaScript and plain JSP without JSF.
    Thank you in advance!
    Best Regards, Ailsa
    2007/5/4

    Thank you for your quick response, BalusC. I really appreciate your answer.
    Yes, you are right. If I manually code the same amount of those components in the JSF pages instead of generating them dynamically, the server will still run out of memory. That is to say, JSF pages might not accommodate a great deal of concurrent visiting. If I upgrade the server to just allow 1,000 teachers making their own test papers at the same time, but when over 2,000 students take the same questionnaire simultaneously, the server will need another upgrading. So I have to do what you have told me, using JS+DOM instead of upgrading the server endlessly.
    Best Regards, Ailsa

  • Oracle 9i running out of memory

    Folks !
    I have a simple 3 table schema with a few thousand entries each. After dedicating gigabytes of hard disk space and 50% of my 1+ GB memory, I do a few simple Oracle Text "contains" searches (see below) on these tables and oracle seems to grow some 25 MB after each query (which typically return less than a dozen rows each) till it eventually runs out of memory and I have to reboot the system (Sun Solaris).
    This is on Solaris 9/Sparc with Oracle 9.2 . My query is simple right outer join. I think the memory growth is related to Oracle Text index/caching since memory utilization seems pretty stable with simple like '%xx%' queries.
    "top" shows a dozen or so processes each with about 400MB RSS/SIZE. It has been a while since I did Oracle DBA work but I am nothing special here. Databse has all the default settings that you get when you create an Oracle database.
    I have played with SGA sizes and no matter how large or small the size of SGA/PGA, Oracle runs out of memory and crashes the system. Pretty stupid to an Enterprise databas to die like that.
    Any clue on how to arrest the fatal growth of memory for Oracle 9i r2?
    thanks a lot.
    -Sanjay
    PS: The query is:
    SELECT substr(sdn_name,1,32) as name, substr(alt_name,1,32) as alt_name, sdn.ent_num, alt_num, score(1), score(2)
    FROM sdn, alt
    where sdn.ent_num = alt.ent_num(+)
    and (contains(sdn_name,'$BIN, $LADEN',1) > 0 or
    contains(alt_name,'$BIN, $LADEN',2) > 0)
    order by ent_num, score(1), score(2) desc;
    There are following two indexes on the two tables:
    create index sdn_name on sdn(sdn_name) indextype is ctxsys.context;
    create index alt_name on alt(alt_name) indextype is ctxsys.context;

    I am already using MTS.
    Atached is the init.ora file below.
    may be I should repost this article with subject "memory leak in Oracle" to catch developer attention. I posted this a few weeks back in Oracle Text groiup and no response there either.
    Thanks for you help.
    -Sanjay
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # Cache and I/O
    db_block_size=8192
    db_cache_size=33554432
    db_file_multiblock_read_count=16
    # Cursors and Library Cache
    open_cursors=300
    # Database Identification
    db_domain=""
    db_name=ofac
    # Diagnostics and Statistics
    background_dump_dest=/space/oracle/admin/ofac/bdump
    core_dump_dest=/space/oracle/admin/ofac/cdump
    timed_statistics=TRUE
    user_dump_dest=/space/oracle/admin/ofac/udump
    # File Configuration
    control_files=("/space/oracle/oradata/ofac/control01.ctl", "/space/oracle/oradata/ofac/control02.ctl", "/space/oracle/oradata/ofac/control03.ctl")
    # Instance Identification
    instance_name=ofac
    # Job Queues
    job_queue_processes=10
    # MTS
    dispatchers="(PROTOCOL=TCP) (SERVICE=ofacXDB)"
    # Miscellaneous
    aq_tm_processes=1
    compatible=9.2.0.0.0
    # Optimizer
    hash_join_enabled=TRUE
    query_rewrite_enabled=FALSE
    star_transformation_enabled=FALSE
    # Pools
    java_pool_size=117440512
    large_pool_size=16777216
    shared_pool_size=117440512
    # Processes and Sessions
    processes=150
    # Redo Log and Recovery
    fast_start_mttr_target=300
    # Security and Auditing
    remote_login_passwordfile=EXCLUSIVE
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=25165824
    sort_area_size=524288
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_retention=10800
    undo_tablespace=UNDOTBS1

  • Running out of memory after latest update

    First of all:
    Why doesn't anybody answer my questions from Dez. 26th?? They are not that hard, I believe...
    After I installed the update No. 5, my system runs out of memory after a certain time.
    I'm working an an 1,7Centrino with 1GB memory....
    Is it bc of the update? Do RUN change so many things?
    Hope for an answer this time...
    Mark.

    Hi Mark
    Aplogies for not responding to your earlier post on Debugging Rowset. I am still working on that. I am sure I can give you something todday if there is any straight solution.
    OK coming to the OutOfMemoryExceptions, yes this has been observed because of preview feature added in Updaet 5. Look @ http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=50422 for more details.
    Thanks
    Srinivas

  • Running Out of Memory Since Yosemite

    Let me start by saying I was originally part of the Yosemite Beta and was running into the same issue.
    After running my system for >20-25 minutes a menu pops up and says I've run out of memory and it has paused my programs.  Looking at my Activity Monitor, it says my Mail is running at 64+ GB of memory.  When I restart my system, Mail ranges from 64 MB - 120 MB, then it some how creeps up to 64 GB and crashes.
    When the final release of Yosemite was released I did a complete clean install, thinking that maybe that was the issue.  Tonight I received the same error.  After searching online I didn't really find anything of help.  I'm hoping someone in this community can help.
    Thanks.
    My System:
    rMBP- 2.6 GHz i7 - 16 GB ram - 1TB SSD

    I'm having the exact same issue, on both a  2013 MacBook Air, and on a 2009 iMac. I've used activity monitor, and can observe the mail app increasing in memory usage from 200mb during normal conditions to a sudden rise to 60+GB. Same activity monitor screens as in this post. If I force quite the mail app, everything returns to normal, but this happens at least once every hour.  So my assumption is that 1) yes it is the mail.app, 2) it's happening to quite a few people, 3) it's happening on a range of recent as well as older machines, 4) it was introduced with Yosemite, 5) it's not a "plugin" as someone suggested in other posts, 6) no help from clearing cache, clean installs, deleting preferences or container folders in the library.
    I would lIke to think Apple will address this issue, but find it alarming that someone in this thread has raised 12 tickets about it in beta without receiving a response. For those of us affected, we might be in for a long wait.
    Apple, please help!

  • Running out of memory despite having set je.maxMemory to a moderate value

    I have set je.maxMemory to 20MB (je.maxMemory=20000000) and allowed a max heap size of 512MB (-Xms256M -Xmx512M).
    After two hours of running my web service, I'm running out of memory. After having profiled my service (using Yourkit Java Profiler 1.10.6), I can see the following:
    Name                                               Objects ShallowSize  RetainedSize
    byte[]                                               16711   124124880     124124880
    com.sleepycat.je.tree.BIN                              181       24616     116254200
    com.sleepycat.je.tree.Node[]                           187       98736     115743184
    com.sleepycat.je.tree.LN                              7092      226944     115253600
    java.util.concurrent.ConcurrentHashMap$HashEntry       554       17728      78328944
    java.util.concurrent.ConcurrentHashMap$HashEntry[]    1053       34728      77489632
    java.util.concurrent.ConcurrentHashMap                 117        5616      71812072
    java.util.concurrent.ConcurrentHashMap$Segment[]       118       10304      71807912
    java.util.concurrent.ConcurrentHashMap$Segment        1052       42080      71798808
    com.sleepycat.je.tree.IN                                 6         672      45592352
    java.lang.String                                    135888     4348416      14152664The memory profiler claims further, that com.sleepycat.je.tree.BIN is responsible for 71% of all heap memory.
    In any case, com.sleepycat.je.tree.BIN claims ~ 116MB of heap memory, which is by any goodwill, exceeded the limit of 20MB.
    How can this be?
    How is JE ensuring that the limit is not exceeded? Is there a timer (thread) running which once a while checks the memory used and then cleans up ; or is memory usage checked creating a com.sleepycat.je.tree.BIN object?
    My environment:
    BDB JE 4.0.92 - used as cache loader within Jboss Cache (3.2.7.GA), running on a JBOSS Application Server, Java 1.6 (IBM) on Linux. Further details are listed in the system properties below (except some deleted security items).
    System properties:
    (java.lang.String, int, java.lang.StringBuffer, int)=contains
    DestroyJavaVM helper thread=(java.lang.String, java.security.KeyStore$Entry, java.security.KeyStore$ProtectionParameter)
    base.collection.name=CD2JAVA
    bind.address=10.12.25.130
    catalina.base=/work/ocrgws_test/server0
    catalina.ext.dirs=/work/ocrgws_test/server0/lib
    catalina.home=/work/ocrgws_test/server0
    catalina.useNaming=false
    com.arjuna.ats.arjuna.objectstore.objectStoreDir=/work/ocrgws_test/server0/data/tx-object-store
    com.arjuna.ats.jta.lastResourceOptimisationInterface=org.jboss.tm.LastResource
    com.arjuna.ats.tsmx.agentimpl=com.arjuna.ats.internal.jbossatx.agent.LocalJBossAgentImpl
    com.arjuna.common.util.logger=log4j_releveler
    com.arjuna.common.util.logging.DebugLevel=0x00000000
    com.arjuna.common.util.logging.FacilityLevel=0xffffffff
    com.arjuna.common.util.logging.VisibilityLevel=0xffffffff
    com.ibm.cpu.endian=little
    com.ibm.jcl.checkClassPath=
    com.ibm.oti.configuration=scar
    com.ibm.oti.jcl.build=20100326_1904
    com.ibm.oti.shared.enabled=false
    com.ibm.oti.vm.bootstrap.library.path=/opt/ibm/java-x86_64-60/jre/lib/amd64/compressedrefs:/opt/ibm/java-x86_64-60/jre/lib/amd64
    com.ibm.oti.vm.library.version=24
    com.ibm.util.extralibs.properties=
    com.ibm.vm.bitmode=64
    common.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar
    epo.jboss.deploymentscanner.extradirs=/work/ocrgws_test/app/
    external.cert.ldap.* = ***************
    file.encoding=UTF-8
    file.separator=/
    flipflop.activation.time=16:30
    hibernate.bytecode.provider=javassist
    ibm.signalhandling.rs=false
    ibm.signalhandling.sigchain=true
    ibm.signalhandling.sigint=true
    ibm.system.encoding=UTF-8
    jacorb.config.log.verbosity=0
    java.assistive=ON
    java.awt.fonts=
    java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
    java.awt.printerjob=sun.print.PSPrinterJob
    java.class.path=/work/ocrgws_test/config:/usr/local/jboss-eap-4.3-cp07/bin/run.jar:/opt/ibm/java-x86_64-60/lib/tools.jar
    java.class.version=50.0
    java.compiler=j9jit24
    java.endorsed.dirs=/usr/local/jboss-eap-4.3-cp07/lib/endorsed
    java.ext.dirs=/opt/ibm/java-x86_64-60/jre/lib/ext
    java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8-20100401_55940 (JIT enabled, AOT enabled)
    J9VM - 20100401_055940
    JIT - r9_20100401_15339
    GC - 20100308_AA_CMPRSS
    java.home=/opt/ibm/java-x86_64-60/jre
    java.io.tmpdir=/tmp
    java.jcl.version=20100408_01
    java.library.path=/opt/ibm/java-x86_64-60/jre/lib/amd64/compressedrefs:/opt/ibm/java-x86_64-60/jre/lib/amd64:/usr/lib64/mpi/gcc/openmpi/lib64:/usr/lib
    java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
    java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
    java.net.preferIPv4Stack=true
    java.protocol.handler.pkgs=org.jboss.net.protocol
    java.rmi.server.codebase=http://10.12.25.130:8083/
    java.rmi.server.hostname=10.12.25.130
    java.rmi.server.randomIDs=true
    java.runtime.name=Java(TM) SE Runtime Environment
    java.runtime.version=pxa6460sr8-20100409_01 (SR8)
    java.security.krb5.conf=/usr/local/jboss/etc/krb5.conf
    java.specification.name=Java Platform API Specification
    java.specification.vendor=Sun Microsystems Inc.
    java.specification.version=1.6
    java.util.prefs.PreferencesFactory=java.util.prefs.FileSystemPreferencesFactory
    java.vendor.url=http://www.ibm.com/
    java.vendor=IBM Corporation
    java.version=1.6.0
    java.vm.info=JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8-20100401_55940 (JIT enabled, AOT enabled)
    J9VM - 20100401_055940
    JIT - r9_20100401_15339
    GC - 20100308_AA_CMPRSS
    java.vm.name=IBM J9 VM
    java.vm.specification.name=Java Virtual Machine Specification
    java.vm.specification.vendor=Sun Microsystems Inc.
    java.vm.specification.version=1.0
    java.vm.vendor=IBM Corporation
    java.vm.version=2.4
    javax.management.builder.initial=org.jboss.mx.server.MBeanServerBuilderImpl
    javax.net.ssl.trustStore=/usr/local/jboss/etc/ldap.truststore
    javax.net.ssl.trustStorePassword=password
    jboss.bind.address=10.12.25.130
    jboss.home.dir=/usr/local/jboss-eap-4.3-cp07
    jboss.home.url=file:/usr/local/jboss-eap-4.3-cp07/
    jboss.identity=30df88bc0a52e350x6e2ff59cx136c17794d5x-8000757
    jboss.lib.url=file:/usr/local/jboss-eap-4.3-cp07/lib/
    jboss.messaging.controlchanneludpaddress=239.1.200.4
    jboss.messaging.datachanneludpaddress=239.1.200.4
    jboss.partition.name=ocrgws_test_Partition
    jboss.partition.udpGroup=239.1.200.4
    jboss.remoting.domain=JBOSS
    jboss.remoting.instanceid=30df88bc0a52e350x6e2ff59cx136c17794d5x-8000757
    jboss.remoting.jmxid=luu002t.internal.epo.org_1334685694459
    jboss.remoting.version=22
    jboss.security.disable.secdomain.option=true
    jboss.server.config.url=file:/work/ocrgws_test/server0/conf/
    jboss.server.data.dir=/work/ocrgws_test/server0/data
    jboss.server.home.dir=/work/ocrgws_test/server0
    jboss.server.home.url=file:/work/ocrgws_test/server0/
    jboss.server.lib.url=file:/work/ocrgws_test/server0/lib/
    jboss.server.log.dir=/work/ocrgws_test/server0/log
    jboss.server.name=luu002t_ocrgws_test_server0
    jboss.server.temp.dir=/work/ocrgws_test/server0/tmp
    jboss.tomcat.udpGroup=239.1.200.4
    jbossmx.loader.repository.class=org.jboss.mx.loading.UnifiedLoaderRepository3
    je.maxMemory=20000000
    jgroups.bind_addr=10.12.25.130
    jmx.console.bindcredential=3bpwdmpc
    jmx.console.binddn=cn=jbossauth-ro,ou=accounts,ou=auth,dc=epo,dc=org
    jmx.console.rolesctxdn=ou=roles-test,ou=jboss,ou=applications,ou=internal,dc=epo,dc=org
    jndi.datasource.name=java:MainframeDS
    jnp.disableDiscovery=true
    jxe.current.romimage.version=15
    jxe.lowest.romimage.version=15
    line.separator=
    mainframelogin.password=720652a1e842fc7f
    mainframelogin.username=test_t
    org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger
    org.apache.tomcat.util.http.ServerCookie.VERSION_SWITCH=true
    org.epo.jboss.application.home=/work/ocrgws_test
    org.hyperic.sigar.path=/work/ocrgws_test/server0/./deploy/hyperic-hq.war/native-lib
    org.jboss.ORBSingletonDelegate=org.jacorb.orb.ORBSingleton
    org.omg.CORBA.ORBClass=org.jacorb.orb.ORB
    org.omg.CORBA.ORBSingletonClass=org.jboss.system.ORBSingleton
    org.w3c.dom.DOMImplementationSourceList=org.apache.xerces.dom.DOMXSImplementationSourceImpl
    os.arch=amd64
    os.name=Linux
    os.version=2.6.32.46-0.3-xen
    package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.,sun.beans.
    package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,org.apache.jasper.
    path.separator=:
    poll.interval.milliseconds=300000
    program.name=run.sh
    server.loader=
    shared.loader=
    spnego.config=/usr/local/jboss/etc/spnego.properties
    sun.arch.data.model=64
    sun.boot.class.path=/usr/local/jboss-eap-4.3-cp07/lib/endorsed/xercesImpl.jar:/usr/local/jboss-eap-4.3-cp07/lib/endorsed/xalan.jar:/usr/local/jboss-eap-4.3-cp07/lib/endorsed/serializer.jar:/opt/ibm/java-x86_64-60/jre/lib/amd64/compressedrefs/jclSC160/vm.jar:/opt/ibm/java-x86_64-60/jre/lib/annotation.jar:/opt/ibm/java-x86_64-60/jre/lib/beans.jar:/opt/ibm/java-x86_64-60/jre/lib/java.util.jar:/opt/ibm/java-x86_64-60/jre/lib/jndi.jar:/opt/ibm/java-x86_64-60/jre/lib/logging.jar:/opt/ibm/java-x86_64-60/jre/lib/security.jar:/opt/ibm/java-x86_64-60/jre/lib/sql.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmorb.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmorbapi.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmcfw.jar:/opt/ibm/java-x86_64-60/jre/lib/rt.jar:/opt/ibm/java-x86_64-60/jre/lib/charsets.jar:/opt/ibm/java-x86_64-60/jre/lib/resources.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmpkcs.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmcertpathfw.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmjgssfw.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmjssefw.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmsaslfw.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmjcefw.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmjgssprovider.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmjsseprovider2.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmcertpathprovider.jar:/opt/ibm/java-x86_64-60/jre/lib/ibmxmlcrypto.jar:/opt/ibm/java-x86_64-60/jre/lib/management-agent.jar:/opt/ibm/java-x86_64-60/jre/lib/xml.jar:/opt/ibm/java-x86_64-60/jre/lib/jlm.jar:/opt/ibm/java-x86_64-60/jre/lib/javascript.jar:/tmp/yjp201202191932.jar
    sun.boot.library.path=/opt/ibm/java-x86_64-60/jre/lib/amd64/compressedrefs:/opt/ibm/java-x86_64-60/jre/lib/amd64
    sun.io.unicode.encoding=UnicodeLittle
    sun.java.command=org.jboss.Main -b 10.12.25.130 -Djboss.server.home.dir=/work/ocrgws_test/server0 -Djboss.server.home.url=file:/work/ocrgws_test/server0 -Djboss.server.name=luu002t_ocrgws_test_server0 -Djboss.partition.name=ocrgws_test_Partition -Depo.jboss.deploymentscanner.extradirs=/work/ocrgws_test/app/ -Dorg.epo.jboss.application.home=/work/ocrgws_test
    sun.java.launcher.pid=17781
    sun.java.launcher=SUN_STANDARD
    sun.java2d.fontpath=
    sun.jnu.encoding=UTF-8
    sun.rmi.dgc.client.gcInterval=3685000
    sun.rmi.dgc.server.gcInterval=3685000
    system=java.io.ObjectStreamField
    tomcat.util.buf.StringCache.byte.enabled=true
    user.country=US
    user.dir=/work/ocrgws_test
    user.home=*****************
    user.language=en
    user.name=***********
    user.timezone=Europe/Berlin
    user.variant=

    The memory profiler claims further, that com.sleepycat.je.tree.BIN is responsible for 71% of all heap memory. In any case, com.sleepycat.je.tree.BIN claims ~ 116MB of heap memory, which is by any goodwill, exceeded the limit of 20MB. >
    I'm not sure whether the profiler is reporting live objects only (referenced) or all objects (including those not yet reclaimed). If the latter, it isn't telling you how much memory is actually referenced by the JE cache.
    Please look at the JE stats to see what the cache usage is, from JE's point of view.
    If you believe there is a bug in JE cache management, you'll need to write a small standalone test to demonstrate it and submit it to us, since we don't know of any such bug. Also note that we'll have difficulty supporting JE 4.0 (without a support contract anyway). Please use JE 5.0, or at least 4.1.
    Eviction occurs as objects are allocated, as well as in background threads. Eviction in background threads and concurrent eviction were greatly improved in JE 4.1.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Running out of memory... what to do?

    I am using a mid-2012 non-retina 13" MacBook Pro that I upgraded with a large SSD and 16 gigs of RAM, but I find myself running out of memory every day. I am developing a DirectX11 game engine in a virtualized Windows 7 environment, and my memory needs apparently exceed the 16GB I have. Is there any way to add more memory to my MacBook Pro, or can any Apple notebook hold more than 16 gigs of RAM? (officially or unofficially)
    I can't afford a Mac Pro (a shame since it would have been right at home in my chain of Thunderbolt devices) but if I could upgrade my MacBook Pro with 32GB of memory or more, that would be a life saver. I am starting to think it is unreasonable of me to except my consumer notebook to do the work of a professional workstation, but I figured it couldn't hurt to ask around.
    Thank you for your time!
    -Faye

    FayeCS wrote:
    Is there any way to add more memory to my MacBook Pro, or can any Apple notebook hold more than 16 gigs of RAM? (officially or unofficially)
    I'm sorry, but 16 GB of RAM is the maximum amount of RAM MacBooks Pro can use.
    As you are using Windows in a virtual machine, this RAM problem would be solved if you install Windows through Boot Camp. By doing this, your Mac will run faster because you will not be using all the RAM, apart from getting the maximum performance in Windows.
    Your Mac supports 64-bit Windows 7, Windows 8 and Windows 8.1, so you can install any of them. Then, follow the steps to install Windows in your computer > http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf
    I do not recommend to use Windows in virtual machines if you want to do tasks like game design because they require that your GPU and CPU work at the best performance.

  • Workfow Iterate to subprocess runs out of memory

    I have a workflow that returns all suspended tasks and then calls a subprocess for each task. The subprocess decides whether the task needs to be deleted and if so it processes the task in various ways before deleting the taskinstance.
    I have no issues when there are not too many tasks returned by the query but when the workflow returns 2000+ items, I run out of memory.
    What is the best way to workflow to call the subprocess without running out of memory?
    Do I need to cleanup something at the end of subprocess?
    Do I need to add something in the workflow to beakup the list of tasks into smaller chunks?
    <Activity id='3' name='ProcessTasks'>
    <Action id='0' name='processTasks' process='processTheTask'>
    <Iterate for='taskInstanceName' in='mytasks'/>
    <Argument name='taskInstanceName' value='$(taskInstanceName)'/>
    </Action>
    Edited by: user1937458 on Mar 14, 2012 3:12 PM

    I didnt think that this would put that much stress on the system.
    1) Use IDM best practice to generate low memory tasks, use exposedVariables and extendedVariables in manual actions to generate low memory tasks, that will save lots of memory.
    No manual action. This is a scheduled task.
    2) Run this workflow on dedicated server which is responsible to run this task only.
    I have run this when no one else was using the system but that did not help either.
    3) You can put some more conditions to get the limited return data which your server can handle in one go.
    we normally have 8000 tasks in the system. About 5000 are completed so I can ignore those in the workflow. The rest need to be looked at to determine if we need to update the request. Let's say that I can use a rule to determine that in the workflow before the subprocess is called and I end up with a list of 500 taskinstance names, I think that the process will still run out of memory unless there is some other solution.
    2000 task names in a list should not take up that much space. I am pretty sure that the subprocess which determines if the task needs to be deleted is chewing up resources. This is going to be a scheduled task with no manual actions.
    My thinking was that workflow calls the subprocess and the subprocess does a lot of work as far as canceling a request, disabling accounts in some cases, auditing and notifying users that their request was cancelled. Upon return to the workflow to get the next taskinstance name, there is probably some variable that keeps getting larger with each iteration.
    I have run smaller lists and the flow diagram that returns at the end shows the flowchart for every item that was deleted so that is probably 1 place where the variable keeps getting larger.
    Is there a way to clean everything so that each subprocess acts as if it was the 1st and only time it was getting called?
    I tried the following at the end of the subprocess but that did not help:
    <Action id='0' name='CleanUp'>
    <expression>
    <set name='WF_CASE_RESULT'/>
    </expression>
    </Action>
    I will try to debug and see what variables are getting larger and larger but any other suggestions are appreciated.

  • Target has run out of memory on LM3s8962

    I'm using the LM3s8962 evaluation kit to record data from the ADC's.  I have the system set up so that I use the elemental nodes of the four adc's in a while loop, and replace the values in four different arrays.  The arrays are initialize (1x1000 elements) before entering the loop.  This works fine.
    THE PROBLEM:  When I try to make the arrays larger (i.e. initial arrays larger than 1000 points, 4 individual arrays), I get the following error:
    Error: Memory allocation failed. The target has run out of memory. [C:\Program Files (x86)\National Instruments\LabVIEW 2011\CCodeGen\libsrc\blockdiagram\CCGArrSupport2.c at line 253: 2 3
    OR
    Error: Memory allocation failed. The target has run out of memory. [C:\Program Files (x86)\National Instruments\LabVIEW 2011\CCodeGen\libsrc\blockdiagram\CCGArrSupport2.c at line 173: 2 3
    Any suggestions?

    Th0r wrote:
    It looks like you're filling up the flash memory on the LM3S8962 with all of these array initializations.  According to page 263 of the LM3S8962 datasheet, that microcontroller has 256 KB of flash memory which you can use to fill up with your code.  In addition to your array initializations, some of this space is taken up by the LabVIEW Embedded Module-specific code as well.  What datatype are you using in these arrays?  Does this error occur upon building or running your code?  Thanks for any additional information you can provide!  
    That's probably it.  The error occurs when building the code, before it's actually able to run.  If reduce the array size, I'm able to run the code no problem.  At the moment,  I'm using a long 32 bit integer, which I know realize I can reduce significantly, as my ADC only reads at 10 bits.  Do you know if there's a way that I can preallocate the array to a place other than flash?
    I've found a fix around it since I last posted, in which I set up a buffer (smaller) and then save the buffer values on the SD card.  This works well and I can sample for long periods of time, but it does slow down my overall sampling rate, so I'd like to fix the above problem nonetheless. 

  • Aperture runs out of memory generating previews

    Aperture 3.2.3
    65K photos in library
    OSX 10.7.3
    Model Identifier:          MacPro1,1
    Processor Name:          Dual-Core Intel Xeon
    Processor Speed:          2.66 GHz
    Total Number of Cores:          4
    L2 Cache (per Processor):          4 MB
    Memory:          10 GB
    After moving my photoes to an external drive as referenced images, and a library rebuild, Aperture is attempting to recreatea all of my previews.  After generateing a couple of hunderd previews, it runs out of memory and I can see the following errors in the system console:
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
    5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
    5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
    5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
    5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
    Inactive memory quickly uses up all available memory and is not released.  Quitting Aperture only releases half of the inactive memory.
    Any ideas on how to get previews generated without running out of memory?  I've tried running aperture in 32-bit mode, with no difference in behavior.

    Are Previews being generated as you import, or later?  I am asking because I can identify with memory issues when editing numerous images from my D800 in succession (which are huge), but i am not seeing it while importing.
    Ernie

  • CS6 runs out of Memory quickly

    A project runs out of memory evertime I render on exactly the same frame.
    It basically sucks about 3% of memory with each rendered frame till there's nothing left and than prompts an error-message.
    I tried to:
    - activate disk cache
    - reduce bitmap-footage size
    - enabled "purge cache every 5 frames" on the secret preferences (the percentage-growth of ram-usage continues unimpressed)
    - disable layer cache on the secret preferences
    - deactivated multi-processor rendering to free up more ram.
    Nothing.
    Is there any issue or solution known?
    I use
    System:
    Adobe After Effects CS6 11.0.2.11
    OSX 10.8.5
    16 GB RAM

    I downloaded the Update Patch "AfterEffectsTrial-11.0.4-mul-AdobeUpdate" and 11.0.1 - 11.0.3 too.
    I don't know why there's a "trial" in the Filename, I downloaded it from here: http://www.adobe.com/support/downloads/product.jsp?product=13&platform=Mac
    All Patches prompt an Error-Messagebox with german Text.
    "Update fehlgeschlagen. Updates konnten nicht angewendet werden. Dieser Patch ist für Sie nicht geeignet."
    Translated
    "Update failed. Updates could not be executed. This patch isn't adequate for you."
    Followed by some lines about using the help files or the support-website, with no specific url or any error-details.

  • GC isn't working: WLS runs out of memory and dies

    Periodically webservers just runs out of memory and dies. It looks like the garbage collection isn't working correctly and it never gets kicked off,
    Where can I configure the GC in weblogic?
    Have the min and max set to 512m,on WL92mp1, JDK 150_06. 40 - 50 concurrent users and this is a Financials system.
    Full thread dump Java HotSpot(TM) Server VM (1.5.0_04-b05 mixed mode):
    "NwWriter" daemon prio=5 tid=0x1abc9008 nid=0x1220 in Object.wait() [0x1fbdf000..0x1fbdfc1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x19e40930> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x19e40930> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1d644e48 nid=0x2f8 runnable [0x1fb9f000..0x1fb9fc9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1cf5e388 nid=0x1098 in Object.wait() [0x1f7df000..0x1f7dfa1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0def6e90> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0def6e90> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1ced8be0 nid=0x12c4 runnable [0x1f79f000..0x1f79fa9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1ed1c408 nid=0x1494 in Object.wait() [0x1fadf000..0x1fadfc1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0dee6e30> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0dee6e30> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1abc8b80 nid=0x8ec runnable [0x1fa9f000..0x1fa9fc9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1bf71bd8 nid=0x134 in Object.wait() [0x1fa5f000..0x1fa5fa1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0dee9db8> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0dee9db8> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1c6a7d98 nid=0x10cc runnable [0x1fa1f000..0x1fa1fa9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1c5d2008 nid=0x8b4 in Object.wait() [0x1f6df000..0x1f6dfb1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0dee2370> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0dee2370> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1c88ed98 nid=0x8a0 runnable [0x1f69f000..0x1f69fb9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x006a2b58 nid=0x270 in Object.wait() [0x1f9df000..0x1f9dfc1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0decaf68> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0decaf68> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1c958920 nid=0x1680 runnable [0x1f99f000..0x1f99fc9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1d9c0428 nid=0x17a8 in Object.wait() [0x1f85f000..0x1f85fb1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0decfa98> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0decfa98> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1abede28 nid=0x11d0 runnable [0x1f81f000..0x1f81fb9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1c7b8540 nid=0x11f8 in Object.wait() [0x1fd9f000..0x1fd9fb1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0de98618> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0de98618> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1bf85510 nid=0x370 runnable [0x1fd5f000..0x1fd5fb9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1c391b48 nid=0x1768 in Object.wait() [0x1fd1f000..0x1fd1fa1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0de9ff48> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0de9ff48> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1be90440 nid=0x10d4 runnable [0x1fcdf000..0x1fcdfa9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1d2d0bd0 nid=0x1020 in Object.wait() [0x1f75f000..0x1f75fd1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0de5d3c0> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0de5d3c0> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1d3472d0 nid=0x10e0 runnable [0x1f71f000..0x1f71fd9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1bf71a30 nid=0x1b0 in Object.wait() [0x1f95f000..0x1f95fd1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0de11e90> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0de11e90> (a bea.jolt.OutQ)
         at bea.jolt.NwWriter.run(NwHdlr.java:3980)
    "NwReader" daemon prio=5 tid=0x1ac06ab8 nid=0x17ec runnable [0x1f91f000..0x1f91fd9c]
         at java.net.SocketInputStream.socketRead0(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:129)
         at java.io.DataInputStream.readFully(DataInputStream.java:176)
         at bea.jolt.NwReader.run(NwHdlr.java:3625)
    "NwWriter" daemon prio=5 tid=0x1bddfde8 nid=0x133c in Object.wait() [0x1ff9f000..0x1ff9fb1c]
         at java.lang.Object.wait(Native Method)
         - waiting on <0x0d4a71f0> (a bea.jolt.OutQ)
         at java.lang.Object.wait(Object.java:474)
         at bea.jolt.OutQ.getFromQ(OutQ.java:89)
         - locked <0x0d4a71f0> (a bea.jolt.OutQ)
         at bea.jolt.NwWrite

    There's nothing wrong with how GC works. If you don't give it anything to collect, it won't collect anything. You are simply not allowing enough memory to get anything done. As the other responder said, bump up the max mem to at least 1g. If it still fails, set it even higher. I can't tell what platform you're on, but if you're on Windows, you may be limited to about 1536m.

Maybe you are looking for