OutOfMemoryError occured

hi,
here in my code i am using SAX to read and DOM to write.
i am passing destination file path and the document object.
i am trying to save xml file 50,000 subroot records with in the root in this fashion.
<Root>
     <subroot>
          <FirstElement>1</FirstElement>
          <SecondElement>2</SecondElement>
          <ThirdElement>3</thirdElement>
          <ForthElement>4</ForthElement>
          <FifthElement>5</FifthElement>
     </subroot>
</root>
while transforming DOMSource to StreamResult i got OutOfMemoryError.
here is the following code.
can any one help.
private void transformAndSave(File theDestinationFile, Document theDocument)
                         throws TransformerFactoryConfigurationError, TransformerConfigurationException, TransformerException, IOException {
          TransformerFactory transformerFactory = TransformerFactory.newInstance();
          Transformer transformer = transformerFactory.newTransformer();
          try {
               transformer.setOutputProperty(OutputKeys.INDENT, "yes");
               transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
               transformer.setOutputProperty(OutputKeys.STANDALONE, "yes");
               transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "4");
          } catch (Exception e) {
               // We don't want to fail just because we are unable to set a property (incase we are not using the default one).
               // So, just ignore any exceptions thrown.
          // Create a StringWriter to store the transformed result (XML document)
          StringWriter stringWriter = new StringWriter();
          StreamResult streamResult = new StreamResult(stringWriter);
          // Create a Source object for the Document which we want to transform.
          DOMSource source = new DOMSource(theDocument);
          transformer.transform(source, streamResult);
          // here i have encounterd (OutOfMemoryError)          
          // Now we have the XML contents in the StringWriter (which we passed to the StreamResult)
          // Write the XML contents to the file now.
          BufferedWriter bufferedWriter = new BufferedWriter(new FileWriter(theDestinationFile));
          bufferedWriter.write(stringWriter.toString());
          bufferedWriter.flush();
          // Close the Writer now.
          try {
               bufferedWriter.close();
          } catch (Exception e) {
               // We don't want to throw an exception if the close() fails.
               // Just ignore the exception thrown during close()
}thank you

this is because ur buffer memory can't store so large data....u need high memory configuration. check ur RAM size and if ur using eclipse then go to eclipse folder ..check the eclipse cofig file u can see like that..
-vmargs
-Xms40m
-Xmx256m
that is the min and max limit of buffer memory..u can try with incresing that..

Similar Messages

  • OutOfMemoryError occured on server

    While running Coherence, Weblogic 7.0 (ie32, linux) prints the following message upon starting:
    "OutOfMemoryError occured on server"
    From the logs below, it seems that everything is ok with memory. Also, if we don't initialize coherence cashes, everything goes fine.
    Any help will be greatly appreciated.
    Anton
    --------- wlsconsole.log ---------------------
    <WebLogicServer> <000365> <Server state changed to RUNNING>
    <Sep 17, 2004 1:17:57 PM EDT> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
    [GC 106673K->104832K(146748K), 0.0105486 secs]
    [GC 106895K->104847K(146748K), 0.0237169 secs]
    OutOfMemoryError occured on server
    OutOfMemoryError occured on server
    [GC 106895K->104870K(146748K), 0.0066090 secs]
    --------- wlsconsole.log ---------------------

    Hi Rob,
    Thanks for prompt reply.
    No, we see this error directly after Weblogic startup, but we use Coherence caches in startup classes and the standard Tangsol message
    * Tangosol Coherence(tm): Enterprise Edition is licensed
    is printed before
    <17.09.2004 19:38:42 MSD> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
    Also, there are no other cluster nodes.
    Also, we don't see this OutOfMemory
    message if we don't initialize coherence caches.

  • Error OutOfMemoryError occurs when i am printing output in Jtextarea

    I have created a swing application In which i have used Jtextarea component to print output using thread. To write output i m using append method. When thread print the output in text area. After some time i am getting an error
    Java.lang.OutOfMemoryError.
    How can i remove this error.

    I am having the same issue creating a BSO-to-ASO partition via maxl in Essbase 11.1.2. Any ideas on how to get around this.?
    OK/INFO - 1051034 - Logging in user [admin@Native Directory].
    ERROR - 1241171 - Aggregate storage applications cannot be the target of a transparent partition.
    OK/INFO - 1051037 - Logging out user [admin@Native Directory], active for 0 minutes.

  • OutOfMemoryError in 1.4.1, not in 1.3.1

    I'm having trouble diagnosing an OutOfMemoryError in my application and I would like to double-check my assumptions here, if I may. I apologize in advance for the length of this post... I figured the more information the better.
    The situation is this:
    When running the application, it will eventually generate an OutOfMemoryError.
    The OutOfMemoryError always happens during garbage collection and there is plenty of collectable garbage. What I mean to suggest is that I did not actually run out of memory.
    If I specify the minimum heap size to be larger than default (equal to the max heap size at the extreme), I effectively increase the space allowed for allocation before a garbage collection which makes for a longer garbage collection which causes the error to occur much more quickly - usually within the first 3 garbage collections.
    I am currently testing with the Windows JDK1.4.1 on Windows 2000/SP3.
    My expectation (I have not verified this yet, perhaps someone here can confirm this) is that the JVM is supposed to guarantee that any time an allocation is attempted that, if there isn't enough memory available on the heap, the GC will run and attempt to give me my memory before it throws an error. I do not believe that this is what is happening.
    The application uses several threads and my belief is that this must be some sort of race condition, incorrect or incomplete synchronization. When the OutOfMemoryError occurs during the collection, I will get anywhere from 1 to 11 (so far) threads reporting the error.
    The reason I really don't think I'm running out of memory is based on observing the output of a profiler (OptimizeIt). I start with "-Xms192m -Xmx192m". Heap usage starts out at a nominal value of 15m. Application runs under load, eventually usage gets to within 1K of the limit and a "Full GC" begins. The first couple of times, memory usage drops back to the starting value of 15m. Then it fails. Either I "sprung" a really big leak or there is some other problem.
    I have observed that, when running under 1.3.1, the GC runs while there is a LOT more room before reaching the heap limit. For example, in this case it will run when heap usage reaches around 180m. I have also noticed that, when running "-verbose:gc -XX:+PrintGCDetails", it appears that there is never a non-Full GC.
    If anyone has any suggestions on where to look for this problem, I'm all ears. I've used a profiler to determine where most of the allocations are occuring, but that just doesn't help. I'm not really running out of memory, this could be a single byte allocation for all I know that's happening when it shouldn't. I can't believe that it's a VM bug or I would have heard more about it.

    Well, as I mentioned, I am starting at only 15m of heap usage. I then climb to 192m and drop back down to 15m after the collection. Even under load, my baseline memory usage is only about 32m. There is a lot of temporary creation (I've done a lot to reduce it, which has helped, but still quite a bit).
    The duration of the GC appears to be part of the equation. If the GC lasts a long time, it is more likely to happen.
    Maybe I should also point out this: If, rather than specify "-Xms192m -Xmx192m", I use "-Xms128m -Xmx192m", I may get an OutOfMemoryError before heap size even grows to 192m.

  • OutOfMemoryError when retrieving large resultset

    In my application I have one type of object (Call it O for now) that has
    a lot of data in the database (+50000 rows). Now I need to create an
    object of class T that has a m-n binding to 40000 instances of O. In the
    database this is mapped to a link table between the table for O and T.
    Now I get an OutOfMemoryError when I perform the following code to add
    one T to the aforementioned O:
    PersistenceManager pm = VRFUtils.getPM(getServlet());
    T t = new T();
    //Fill arbitrary fields
    t.setToelichting(mtForm.getToelichting());
    //Add T to a set of O's
    Set os = new HashSet();
    Query q = pm.newQuery(O.class,"aangemaakt==parmaanmaak");
    q.declareParameters("java.util.Date parmaanmaak");
    os.addAll(q.execute(field));
    t.setOs(os);
    //Make T persistent
    pm.currentTransaction().begin();
    pm.makePersistent(toelichting);
    pm.currentTransaction().commit();
    pm.close();
    After debugging I've found that the OutOfMemoryError occurs even when I
    don't make anything persistent, but simply run the query that retrieves
    40000 records and do a c.size() on the result.
    I'm running Kodo against MySQL using Optimistic transactions.
    What I must appreciate, is that the OutOfMemoryError does not upset the
    rest of the Kodo system.
    Please advise,
    Martin van Dijken
    PS: The c.size() issue I've been able to resolve using KodoQuery's
    setResult("count(this)"), but I can't think of anything like that, that
    would apply to this situation.

    As you may know, Kodo has several settings that allow you to use large
    result sets without running out of memory (assuming your driver supports
    advanced features):
    http://www.solarmetric.com/Software/Documentation/latest/docs/ref_guide_dbsetup_lrs.html
    Kodo also allows you to apply these settings to persistent fields, so
    that the entire collection or map field does not reside in memory:
    http://www.solarmetric.com/Software/Documentation/latest/docs/ref_guide_pc_scos.html#ref_guide_pc_scos_proxy_lrs
    Unfortunately, you are trying to create a relation containing more
    objects than your system can handle, apparently, and when creating a
    relation you pretty much have to load all the related objects into
    memory at once right now.
    In the next beta release of 3.1, there is a solution to this problem.
    Our next release no longer holds hard references to objects that have
    been flushed. So by using the proper large result set settings as noted
    above, and by making your relation a large result set relation also as
    noted above, and by adding only a few hundred objects at a time from the
    query result to the relation and then manually flushing, you should be
    able to perform a transaction in which all the queried objects are
    transferred from the query result to the large result set relation
    without exhausting memory.

  • JEditorPane and OutOfMemoryError

    Hello,
    I'm using a JEditorPane to display a set of html pages. I have two main problems, which a general search tells me is quite common. First of all the CSS isn't recognised, so highlighted text is displayed as plain text. But more importantly, I Get OutOfMemoryErrors for loading relatively small pages - if the file contains only text there is no problem loading it, however if one or more images are embedded in the html more often than not an OutOfMemoryError occurs. The files are each less than 100KBs, but there could be anything form 1 to more than 10 in a single file.
    Has anyone found a way to resolve especially the second problem?
    Aba-Sah
    Exception in thread "Image Fetcher 3" java.lang.OutOfMemoryError: Java heap space
         at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41)
         at java.awt.image.Raster.createPackedRaster(Raster.java:458)
         at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015)
         at sun.awt.image.ImageRepresentation.createBufferedImage(ImageRepresentation.java:223)
         at sun.awt.image.ImageRepresentation.setPixels(ImageRepresentation.java:475)
         at sun.awt.image.ImageDecoder.setPixels(ImageDecoder.java:120)
         at sun.awt.image.JPEGImageDecoder.sendPixels(JPEGImageDecoder.java:97)
         at sun.awt.image.JPEGImageDecoder.readImage(Native Method)
         at sun.awt.image.JPEGImageDecoder.produceImage(JPEGImageDecoder.java:119)
         at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:246)
         at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
         at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
    Exception in thread "Image Fetcher 1" java.lang.OutOfMemoryError: Java heap space
         at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41)
         at java.awt.image.Raster.createPackedRaster(Raster.java:458)
         at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015)
         at sun.awt.image.ImageRepresentation.createBufferedImage(ImageRepresentation.java:223)
         at sun.awt.image.ImageRepresentation.setPixels(ImageRepresentation.java:475)
         at sun.awt.image.ImageDecoder.setPixels(ImageDecoder.java:120)
         at sun.awt.image.JPEGImageDecoder.sendPixels(JPEGImageDecoder.java:97)
         at sun.awt.image.JPEGImageDecoder.readImage(Native Method)
         at sun.awt.image.JPEGImageDecoder.produceImage(JPEGImageDecoder.java:119)
         at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:246)
         at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
         at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
    Exception in thread "Image Fetcher 0" java.lang.OutOfMemoryError: Java heap space
         at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41)
         at java.awt.image.Raster.createPackedRaster(Raster.java:458)
         at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015)
         at sun.awt.image.ImageRepresentation.createBufferedImage(ImageRepresentation.java:223)
         at sun.awt.image.ImageRepresentation.setPixels(ImageRepresentation.java:475)
         at sun.awt.image.ImageDecoder.setPixels(ImageDecoder.java:120)
         at sun.awt.image.JPEGImageDecoder.sendPixels(JPEGImageDecoder.java:97)
         at sun.awt.image.JPEGImageDecoder.readImage(Native Method)
         at sun.awt.image.JPEGImageDecoder.produceImage(JPEGImageDecoder.java:119)
         at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:246)
         at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
         at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
    Exception in thread "Image Fetcher 2" java.lang.OutOfMemoryError: Java heap space
         at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41)
         at java.awt.image.Raster.createPackedRaster(Raster.java:458)
         at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015)
         at sun.awt.image.ImageRepresentation.createBufferedImage(ImageRepresentation.java:223)
         at sun.awt.image.ImageRepresentation.setPixels(ImageRepresentation.java:475)
         at sun.awt.image.ImageDecoder.setPixels(ImageDecoder.java:120)
         at sun.awt.image.JPEGImageDecoder.sendPixels(JPEGImageDecoder.java:97)
         at sun.awt.image.JPEGImageDecoder.readImage(Native Method)
         at sun.awt.image.JPEGImageDecoder.produceImage(JPEGImageDecoder.java:119)
         at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:246)
         at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
         at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)

    thanks, it seems fine with 512M, all the images are able to load without it breaking.

  • Java.lang.OutOfMemoryError: PermGen space

    <Oct 25, 2011 12:15:53 AM IST> <Error> <netuix> <BEA-423405> <An exception [java.lang.OutOfMemoryError: PermGen space] w
    as thrown while rendering the content at [jsp/changemgmt/ChangeManager.jsp].
    javax.servlet.ServletException: java.lang.OutOfMemoryError: PermGen space
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:341)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
    at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:523)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:444)
    at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.ja
    va:119)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.OutOfMemoryError: PermGen space
    at sun.misc.Unsafe.defineClass(Native Method)
    at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:63)
    at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:399)
    at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <Oct 25, 2011 12:15:53 AM IST> <Error> <netuix> <BEA-423137> <There was an error loading the requested URI /jsp/changemg
    mt/ChangeManager.jsp.>
    <Oct 25, 2011 12:16:14 AM IST> <Error> <HTTP> <BEA-101017> <[ServletContext@22272290[app:consoleapp module:console path:
    /console spec-version:2.5]] Root cause of ServletException.
    java.lang.OutOfMemoryError: PermGen space
    >
    <Oct 25, 2011 12:16:15 AM IST> <Error> <HTTP> <BEA-101107> <[ServletContext@22272290[app:consoleapp module:console path:
    /console spec-version:2.5]] Problem occurred while serving the error page.
    java.lang.OutOfMemoryError: PermGen space
    >
    Exception in thread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'"
    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "[ACTIVE] ExecuteThread: '1' fo
    r queue: 'weblogic.kernel.Default (self-tuning)'"
    Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'"
    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "[ACTIVE] ExecuteThread: '0' fo
    r queue: 'weblogic.kernel.Default (self-tuning)'"
    Exception in thread "[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'"
    Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "[ACTIVE] ExecuteThread: '3' fo
    r queue: 'weblogic.kernel.Default (self-tuning)'"
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Java HotSpot(TM) Client VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal UNKNOWN to handler-
    the VM may need to be forcibly terminated
    Environment:
    OS: Windows Vista
    Weblogic 10.3.5
    JDK: java version "1.7.0"
    Java(TM) SE Runtime Environment (build 1.7.0-b147)
    Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing)
    I created a new domain and when access the Admin console I get the " OutOfMemory " Error
    I revisited the domain creation steps and identified that when selecting the available JDK it shows " JRockit SDK 1.7.0 @ E:\Development\Java\jdk1.7.0"
    But if I do a java-version I get Sun JDK
    java version "1.7.0"
    Java(TM) SE Runtime Environment (build 1.7.0-b147)
    Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing)
    Start-up Argument
    JAVA Memory arguments: -Xms512m -Xmx512m
    WLS Start Mode=Production
    CLASSPATH=D:\BEA_HOME\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\BEA_HOME\patch_ocp360\profiles\default\sys_manifest_classpath\weblogic_patch.jar;E:\DEVELO~1\Java\JDK17~1.0\lib\tools.jar;D:\BEA_HOME\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\BEA_HOME\WLSERV~1.3\server\lib\weblogic.jar;D:\BEA_HOME\modules\features\weblogic.server.modules_10.3.5.0.jar;D:\BEA_HOME\WLSERV~1.3\server\lib\webservices.jar;D:\BEA_HOME\modules\ORGAPA~1.1/lib/ant-all.jar;D:\BEA_HOME\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\BEA_HOME\WLSERV~1.3\common\derby\lib\derbyclient.jar;D:\BEA_HOME\WLSERV~1.3\server\lib\xqrl.jar;.;C:\Program Files\Java\jre7\lib\ext\QTJava.zip
    PATH=D:\BEA_HOME\patch_wls1035\profiles\default\native;D:\BEA_HOME\patch_ocp360\profiles\default\native;D:\BEA_HOME\WLSERV~1.3\server\native\win\32;D:\BEA_HOME\WLSERV~1.3\server\bin;D:\BEA_HOME\modules\ORGAPA~1.1\bin;E:\DEVELO~1\Java\JDK17~1.0\jre\bin;E:\DEVELO~1\Java\JDK17~1.0\bin;D:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Broadcom\Broadcom 802.11\Driver;C:\Program Files\QuickTime\QTSystem\;D:\BEA_HOME\WLSERV~1.3\server\native\win\32\oci920_8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Starting WLS with line:
    E:\DEVELO~1\Java\JDK17~1.0\bin\java -Xms512m -Xmx512m -Dweblogic.Name=MyAdmin -Djava.security.policy=D:\BEA_HOME\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.ProductionModeEnabled=true -da -Dplatform.home=D:\BEA_HOME\WLSERV~1.3 -Dwls.home=D:\BEA_HOME\WLSERV~1.3\server -Dweblogic.home=D:\BEA_HOME\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=D:\BEA_HOME\patch_wls1035\profiles\default\sysext_manifest_classpath;D:\BEA_HOME\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
    <Oct 25, 2011 12:24:20 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Oct 25, 2011 12:24:20 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Oct 25, 2011 12:24:21 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 21.0-b17 from Oracle Corporation>
    <Oct 25, 2011 12:24:22 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    Any possible pointers to the issue. Is it a issue with incompatible JDK 1.7 with weblogic 10.3.5.

    I just checked on the Oracle Support site. Oracle WebLogic Server 10.3.5.0.0 is certified with Oracle JDK (1.6.0_24+). There are other JDKs listed but they're all in the Java 6 family, no Java 7.
    Also, Oracle WebLogic Server 12.1.1.0.0 shows as certified with Oracle JDK 1.6.0_29+.
    Of course, this is all as of this writing.
    D

  • Java.lang.OutOfMemoryError : GC Overhead Limit Exceeded on SOA server

    Hi All,
    We are facing to this java.lang.OutOfMemoryError : GC Overhead Limit Exceeded on issue and we have increased the physical memory of the server to 16GB.
    Modules running in this machine are,
    Oracle DB
    Weblogic Admin server - 10.3.6.0
    Imaging - 11.1.1.6.0
    UCM
    and SOA server
    We can see all these components using only 50% of the memory. But when we trigger BPM instances it triggers above error and system gets really slow.
    PermGen arguments are,
    USER_MEM_ARGS=-Xms1024m -Xmx1536m -XX:PermSize=1024m -XXMaxPermSize=1024m
    JAVA Memory arguments: -Xms1024m -Xmx1536m -XX:PermSize=1024m -XXMaxPermSize=1024m
    This is our Development Environment and planning to give a user demo on this week... ;( but system is really slow....
    What we are to do???
    Quick responses greatly appreciated ...
    Thanks

    You have misspelled the max perm parameter. -XXMaxPermSize=1024m should be -XX:MaxPermSize=1024m
    Not sure if that's the whole issue though.
    Also take a memory dump and see what type of objects that fill upp your memory.
    jmap -dump:format=b,file=$heap_file $proid
    Also look at the parameters for generating a dump when OutOfMemoryError occurs:
    -XX:HeapDumpPath=domain1.hprof
    -XX:+HeapDumpOnOutOfMemoryError

  • Handling java.lang.OutOfMemoryError

    Hi all,
    I've got these huge text files (approx 23MB in size) for which I am writing a simple text parsing program. I'm using a BufferedReader to read information in line by line.
    BufferedReader rdr = new BufferedReader(new FileReader(myBigFile));Eventually, that information is going into a database, but I'd like to "scrub" it if I could while its in memory.
    Due to the file sizes, keeping 23MB of text in memory is probably not going to happen ... right? I'm lead to believe that my only option is to handle the records I've read before reading too much in from the file.
    I know i'm not encountering an infinite loop or anything. So I guess I should ask if anyone else has any tips on handling this error? Like what kind of operating restrictions am I under when an OutOfMemoryError occurs? ... How much more room do I have in the execution Stack? or do I even need to worry about this stuff? Could I halt the program execution and wait for the garbage collector to help me out?
    I'm not in Kansas anymore with this one

    Woah I thought that wasn't allowed. That (at least
    with XP) that the JVM is running as its own self
    contained process thread and thatit could never be
    allocated more memory ..... or was that CPU cycles?The current default size is 64meg. With your file size it is going to be a push to get it all into memory. As noted you can increase the size via the command line.
    Note however that there is no point to this unless you actually need to have the entire file in memory. For instance if you need to jump back and forth between the beginning and end.
    Not that Processing blocks within the file is not a sufficient reason to do this. You simply read a block rather than a single line.

  • OutOfMemoryError in UIX/BC4J Application

    Hi there,
    in have an application that runs fine in JDevelopers embedded OC4J and on IAS running on Linux.
    When deployed to an IAS running in HP-UX it simply seems not to start, but if found in the application.log, that an OutOfMemoryError occurred.
    What possible issues for HP-UX are known, that could cause this?
    How can I track down the point, at which the error occurs exactly?
    Thanks,
    Sven Luedtke

    Sven -- are there other applications running / deployed to the OC4J instance -- these may be contributing to consumption of a bit more memory. Offhand I don't have a figure, but the OC4J in 9iAS has a few additional class libraries installed as system libs, so it likely uses more memory than the OC4J standalone or JDev embedded installs.
    What you can try doing is bumping up the heapsize of the OC4J instance you are using. This can be done using OEM and setting the Java Properties field of the instance to contain
    -Xmx256m ....
    where 256m indicates the the JVM has a max heap space allocation of 256m.
    cheers
    -steve-

  • Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g

    Hello friends.
    Can you help solve this case:
    I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
    link of the complete log
    http://textbin.com/1c824
    Part of the log**************************************
    With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
    ####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
    weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    Thanks

    Hi Kevin,
    Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
    Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
    at java.lang.reflect.Proxy.defineClass0(Native Method)
    at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
    at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
    at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.security.Security.runAs(Security.java:41)
    at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
    CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    java.lang.OutOfMemoryError: PermGen space
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Thanks
    Edited by: JLK on Oct 2, 2011 11:35 PM
    Edited by: JLK on Oct 2, 2011 11:37 PM

  • Java.lang.NullPointerException at com.sun.mail.iap.Response.parse

    I am getting this error when I try to download a message using IMAP from exchange server
    java.lang.NullPointerException
         at com.sun.mail.iap.Response.parse(Response.java:99)
         at com.sun.mail.iap.Response.<init>(Response.java:68)
         at com.sun.mail.imap.protocol.IMAPResponse.<init>(IMAPResponse.java:31)
         at com.sun.mail.imap.protocol.IMAPResponse.readResponse(IMAPResponse.java:105)
         at com.sun.mail.imap.protocol.IMAPProtocol.readResponse(IMAPProtocol.java:153)
         at com.sun.mail.iap.Protocol.command(Protocol.java:215)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:882)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:874)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:656)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:645)
    This error occurs intermittantly. I placed one large mail (around 600 MB) and few normal size mails on exchange server. In few testing runs, this error occured while downloading the large mail as well as one normal mail. In one test run, all mails got downloaded successfully.
    Could anyone please suggest the cause and resolution?
    Thanks.

    I turned on the session debugging. I am running my application on Linux, so the debugging info was moved to a log file. This log file is very large (around 1GB) and I am unable to open it.
    One more thing: I am trying Message.writeTo() method to download the message. If an OutOfMemoryError occurs, I catch it and try to download the message using GetInputStream. NullPointerException is occuring in both the cases.
    Exception stack trace with writeTo():
    java.lang.NullPointerException
         at com.sun.mail.iap.Response.parse(Response.java:99)
         at com.sun.mail.iap.Response.<init>(Response.java:68)
         at com.sun.mail.imap.protocol.IMAPResponse.<init>(IMAPResponse.java:31)
         at com.sun.mail.imap.protocol.IMAPResponse.readResponse(IMAPResponse.java:105)
         at com.sun.mail.imap.protocol.IMAPProtocol.readResponse(IMAPProtocol.java:153)
         at com.sun.mail.iap.Protocol.command(Protocol.java:215)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:882)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:874)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:656)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:645)
         at com.sun.mail.imap.IMAPMessage.writeTo(IMAPMessage.java:536)
    Exception stack trace with getInputStream():
    java.lang.NullPointerException
         at com.sun.mail.iap.Response.parse(Response.java:99)
         at com.sun.mail.iap.Response.<init>(Response.java:68)
         at com.sun.mail.imap.protocol.IMAPResponse.<init>(IMAPResponse.java:31)
         at com.sun.mail.imap.protocol.IMAPResponse.readResponse(IMAPResponse.java:105)
         at com.sun.mail.imap.protocol.IMAPProtocol.readResponse(IMAPProtocol.java:153)
         at com.sun.mail.iap.Protocol.command(Protocol.java:215)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:882)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:874)
         at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:653)
         at com.sun.mail.imap.protocol.IMAPProtocol.peekBody(IMAPProtocol.java:637)
         at com.sun.mail.imap.IMAPMessage.loadHeaders(IMAPMessage.java:1055)
         at com.sun.mail.imap.IMAPMessage.getAllHeaders(IMAPMessage.java:642)
    First I try to download the headers in case of an OutOfMemoryError. The above trace shows that.
    Could anyone point out the problem and help resolving it?

  • Exception in static block + re-instantiating

    Hello All,
    I have got a number of unit tests and one that is running is causing an exception in a static block of a class which is expected. It throws an ExceptionInInitializerError which I catch in the unit test.
    But then another test is running using the same class and this time it should pass and create an instance of the same class as before.
    But instead I receive a java.lang.NoClassDefFoundError with no class name. Why? Can't I instantiate a class again once the initialisation had failed?
    Regards
    Jonas

    It's part of the VM Specification.
    See [2.17.5 Detailed Initialization Procedure|http://java.sun.com/docs/books/jvms/second_edition/html/Concepts.doc.html#24237]
    The first time,
    10. Otherwise, the initializers must have completed abruptly by throwing some exception E. If the class of E is not Error or one of its subclasses, then create a new instance of the class ExceptionInInitializerError, with E as the argument, and use this object in place of E in the following step. But if a new instance of ExceptionInInitializerError cannot be created because an OutOfMemoryError occurs, then instead use an OutOfMemoryError object in place of E in the following step.After that,
    5. If the Class object is in an erroneous state, then initialization is not possible. Release the lock on the Class object and throw a NoClassDefFoundError.

  • Getting HeapDump on out of memory error when executing method through JNI

    I have a C++ code that executes a method inside the jvm through the JNI.
    I have a memory leak in my java code that results an out of memory error, this exception is caught in my C++ code and as a result the heap dump is not created on the disk.
    I am running the jvm with
    -XX:+HeapDumpOnOutOfMemoryError
    -XX:HeapDumpPath=C:\x.hprof
    Any suggestions?
    Thanks

    I'll rephrase it then.
    I have a java class named PbsExecuter and one static method in it ExecuteCommand.
    I am calling this method through JNI (using CallStaticObjectMethod). sometimes this method causes the jvm to throw OutOfMemoryError and I would like to get a heap dump on the disk when this happens in order to locate my memory leak.
    I've started the jvm with JNI_CreateJavaVM and I've put two options inside the JavaVMInitArgs that is used to create the Jvm. -XX:+HeapDumpOnOutOfMemoryError and -XX:HeapDumpPath=C:\x.hprof
    which supposed to create a heap dump on the disk when OutOfMemoryError occurs.
    Normally if I would execute normal java code, when this exception would occur and I wouldn't catch it the Jvm would crash and the heap dump would be created on the disk.
    Since I need to handle errors in my C++ code I am use ExceptionOccured() and extracts the exception message from the exception it self and write it.
    For some reason when I execute this method through JNI it doesn't create the dump.

  • Getting error on starting the osb10.3.1

    Hi all,
    I have installed OSB10.3.1. i have only configured Admin server and there is no managed servers. When I start the admin server it gets started but after a few seconds it gives the following error.
    [ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "DoSManager" java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Exception in thread "[STANDBY] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    Can anyone suggest what can be the issuue with this.
    Thanks in Advance!!

    Hi Viji,
                It seem's some memory(RAM) problem is strucking, can you try to shut down the OS and try to start the server?
    Regards,
    Hari.

Maybe you are looking for

  • Web help is not working in ie11

    Hi, I have asp.net application and a adobe robo help 7.I have  the WebHelp folder after generate ouput. if run the help help in ie11.. am geeting error at xmldoc.load(). But the same is working in other browser, such as ie 8 and firefox. Thanks & Reg

  • My phone is not working with 3g only wifi

    I just got the new Iphone 5s and I have the mobile Carrier and the 3G on and the roming..but when I have no wifi it dosent work I can oly phone call and text... but I cant use whats app or any social media and my phone has unlimited internet. what is

  • Sales Order Line item status with Resource Related Billing

    Hi The Resource related billing is done based on the costs accumulated on account assigned WBS Element. The WBS Element system status is set 'Finally Billed'. The overall status of Sales Order line item is still 'open' and does show up in 'Open Order

  • Wireless Connection with Sony PSP

    I cannot my Sony PSP to the WRT54G using the wireless connection. What are the setting I need?

  • Skinning Cell Renderer for ComboBox

    How does one change styles for the CellRenderer of a ComboBox? Flash help gives a nice example on how to skin CellRenderer styles for Datagrid and TileList components, but doesn't mention anything on how to do the same for a ComboBox. The code exampl