Default Heap Size

Dear all,
Please tell me what is the default heap memory size when we start the jvm (using the java command) ?

Google ( [sun java default heap size|http://www.google.com/search?q=sun+java+default+heap+size] )

Similar Messages

What is the best way to verify default heap size in Java

Hi All,
What is the best way to verify default heap size in Java ? does it vary over JVM to JVM . I was reading this article http://javarevisited.blogspot.sg/2011/05/java-heap-space-memory-size-jvm.html , and it says default size is 128 MB but When I run following code :
public static void main(String args[]) {
int MB = 1024*1024;
System.out.println(Runtime.getRuntime().totalMemory()/MB);
It print "870" i.e. 870 MB.
I am bit confused, what is the best way to verify default heap size in any JVM ?
Edited by: 938864 on Jun 5, 2012 11:16 PM

938864 wrote:
Hi Kayaman,
Sorry but I don't agree with you on verification part, Why not I can verify it ? to me default means value when I don't specify -Xms and -Xmx and by the way I was testing that program on 32 bit JRE 1.6 on Windows. I am also curious significant difference between 128MB and 870MB I saw, do you see anything obviously wrong ?That spec is outdated. Since Java 6 update 18 (Sun/Oracle implementation) the default maximum heap space is calculated based on total memory availability, but never more than 1GB on 32 bits JVMs / client VMs. On a 64 bits server VM the default can go as high as 32gb.
The best way to verify ANYTHING is to address multiple sources of information and especially those produced by the source, not some page you find on the big bad internet. Even wikipedia is a whole lot better than any random internet site IMO. That's common sense, I can't believe you put much thought into it that you have to ask in a forum.

Overriding the default heap size of 64mb

I run the java program on my pc on windows xp
I need to increase the heap size, currently I launch the jar file using a batch file, the contents of the batch file are:
java -Xms64m -Xmx512m -jar Lines.jar
I have set the min and max heap size and when I click on the .bat file it launches the jar file with tose heap settings
But I do not want to launch the jar file in this way(I don't want to use a batch file), is there anyway to override the default heap size for the java program to 512mb so that every time I launch the jar file the heap size is 512mb??
Edited by: muddy777 on Sep 23, 2009 6:30 PM

Vikash.SunJava wrote:
set this in some machine startup like a scheduled task at machine startup
java -Xms64m -Xmx512m
This this will be default JVM settings.Huh?

What is the default heap size in a oc4j instance

Hi There,
I am wondering what is the default heap size for an oc4j instance if you don't specify -Xms and -Xmx?
Thanks,
Xingsheng

If you're using the Sun JDK 1.4 I believe the max is 64MB. Not sure about 5.0. It's really dependent on the JVM you're using, not OC4J.
Jason

Any way to increase the default Heap size for all Java VMs in Solaris 8

Hello,
I have a java product that deals with large databases under Solaris 8. It is a jar file, started by a cron job every night. Some nights it will fail because it runs out of Heap memory depending on the amount of records it has to deal with. I know that I could increase the java VM heap size with "java -jar -mx YY JARFILE" command but I have other java products that are showing the same behavior, and I would like to correct them all in one shot if possible.
What I would like to do is find a system or configuration parameter that forces all Java VMs to use a larger MAX Heap size than the default 16M specified in the Man page for Java. Is there a way to accomplish that?
TIA
Maizo

You could always download the source and modify it.

Is there a way to set new default heap size for Java?

Hi,
I have a problem with setting global heap size for installed version of Java. By global I mean that every program that will be run using that version of Java, will be using that amount of memory. for heap. I know that I can use Xmx and Xms for each program that I start, but I don't want to do this. I just want to set some kind of property for installed version of Java.

Launch Firefox and set the web page as wide as you want by dragging the hash marks at the lower right corner. Center the page on your screen where you want it. Then quit Firefox. launch Firefox again. The page should be just where on the screen and sized as you set it prior to quitting.

Default Heap Size when using jmsc.dll

We have had some crashes using Weblogic JMS (v 11.x) with one of our C-API apps.
How can I find out the xmx size being used by Java?

If you turn on JMSDEBUG (by setting it to 'y') the JMS C API may print out the JVM options. The log messages will go to the files started with "ULOG" in the directory where your app runs from. You can change the location by setting the ULOGPFX variable in your client environment.
You can override the JVM settings with JMSJVMOPTS variable.
Hope this helps.

Set the heap size

Hi,
I am wondering what's the default heap size if I don't add -ms -mx opation? I
set the two options and the following is the output from -verbosegc. what's it
means?
Thanks.
[GC 2598K->2145K(2696K), 0.0035829 secs]
[GC 2656K->2201K(2824K), 0.0036262 secs]
[Full GC 2713K->2070K(4028K), 0.1933980 secs]
[GC 2582K->2229K(4028K), 0.0046565 secs]
[GC 2741K->2373K(4028K), 0.0061002 secs]
[GC 2885K->2514K(4028K), 0.0064346 secs]
[GC 3026K->2656K(4028K), 0.0061670 secs]
[GC 3168K->2798K(4028K), 0.0054694 secs]
[GC 3310K->2940K(4028K), 0.0054521 secs]
[GC 3452K->3080K(4028K), 0.0058119 secs]
[GC 3592K->3216K(4028K), 0.0059069 secs]
[GC 3728K->3357K(4028K), 0.0057200 secs]
[GC 3869K->3496K(4028K), 0.0055719 secs]
[GC 4008K->3636K(4156K), 0.0057239 secs]
[Full GC 4148K->3649K(6544K), 0.3064887 secs]
[GC 4091K->3773K(6544K), 0.0412259 secs]
[GC 4285K->3912K(6544K), 0.0052336 secs]
[GC 4424K->4051K(6544K), 0.0055661 secs]
[GC 4563K->4189K(6544K), 0.0055543 secs]
[GC 4701K->4326K(6544K), 0.0055703 secs]
[GC 4838K->4464K(6544K), 0.0055915 secs]
[GC 4976K->4608K(6544K), 0.0059667 secs]
[GC 5120K->4746K(6544K), 0.0053261 secs]
[GC 5258K->4884K(6544K), 0.0053761 secs]
[GC 5396K->5023K(6544K), 0.0059290 secs]
[GC 5534K->5159K(6544K), 0.0054320 secs]
[GC 5671K->5301K(6544K), 0.0114341 secs]
[GC 5813K->5405K(6544K), 0.0103658 secs]
[GC 5917K->5492K(6544K), 0.0053194 secs]
[GC 6003K->5592K(6544K), 0.0107092 secs]
[GC 6104K->5694K(6544K), 0.0096887 secs]
[GC 6206K->5786K(6544K), 0.0037949 secs]
[GC 6298K->5890K(6544K), 0.0101172 secs]
[GC 6402K->5990K(6544K), 0.0041271 secs]
[GC 6502K->6097K(6672K), 0.0040678 secs]
[Full GC 6609K->6191K(10992K), 0.2664733 secs]
Tue Dec 04 15:22:10 PST 2001:<I> <T3Services> CacheManagerImpl: EMAIL TEMPLATE
C
ACHE STARTING
[GC 6849K->6361K(10992K), 0.0586387 secs]
Tue Dec 04 15:22:10 PST 2001:<I> <T3Services> CacheManagerImpl: SCHEDULE CACHE
S
TARTING
[GC 7129K->6530K(10992K), 0.0083019 secs]
[GC 7298K->6678K(10992K), 0.0058533 secs]
[GC 7446K->6807K(10992K), 0.0052940 secs]
[GC 7575K->6920K(10992K), 0.0048598 secs]

I think the default heap size is 16MB, as for the GC output:
these [GC 2598K->2145K(2696K), 0.0035829 secs]
show the collection of Objects within the eden area of the heap (Short lived Objects),
the heap size before GC was 2598K and after GC was 2145K and the time taken was
0.0035829 secs.
These outputs:
[Full GC 2713K->2070K(4028K), 0.1933980 secs]
show the details for a full GC, these are the ones to watch out for, they will
take longer and the JVM (no mater how many processors) will block during a full
GC....I.E no server response at all.
The smaller the heap size the more often a full GC will occur, however the larger
the heap, the longer the full GC will take.
One of the new options for jdk 1.3.1 is the -Xincgc option, this will do incremental
Garbage Collection, overall it will take longer than normal, but the individual
Full GCs will take less time....so the server is not hung for as long at any one
time.
Set -Xms (the minimum heap) to the same as -Xmx (max heap), this increases performance
as the JVM does not have to repeatedly assign more memory to the heap.
Gareth
"Jen" <[email protected]> wrote:
>
Hi,
I am wondering what's the default heap size if I don't add -ms -mx opation?
I
set the two options and the following is the output from -verbosegc.
what's it
means?
Thanks.
[GC 2598K->2145K(2696K), 0.0035829 secs]
[GC 2656K->2201K(2824K), 0.0036262 secs]
[Full GC 2713K->2070K(4028K), 0.1933980 secs]
[GC 2582K->2229K(4028K), 0.0046565 secs]
[GC 2741K->2373K(4028K), 0.0061002 secs]
[GC 2885K->2514K(4028K), 0.0064346 secs]
[GC 3026K->2656K(4028K), 0.0061670 secs]
[GC 3168K->2798K(4028K), 0.0054694 secs]
[GC 3310K->2940K(4028K), 0.0054521 secs]
[GC 3452K->3080K(4028K), 0.0058119 secs]
[GC 3592K->3216K(4028K), 0.0059069 secs]
[GC 3728K->3357K(4028K), 0.0057200 secs]
[GC 3869K->3496K(4028K), 0.0055719 secs]
[GC 4008K->3636K(4156K), 0.0057239 secs]
[Full GC 4148K->3649K(6544K), 0.3064887 secs]
[GC 4091K->3773K(6544K), 0.0412259 secs]
[GC 4285K->3912K(6544K), 0.0052336 secs]
[GC 4424K->4051K(6544K), 0.0055661 secs]
[GC 4563K->4189K(6544K), 0.0055543 secs]
[GC 4701K->4326K(6544K), 0.0055703 secs]
[GC 4838K->4464K(6544K), 0.0055915 secs]
[GC 4976K->4608K(6544K), 0.0059667 secs]
[GC 5120K->4746K(6544K), 0.0053261 secs]
[GC 5258K->4884K(6544K), 0.0053761 secs]
[GC 5396K->5023K(6544K), 0.0059290 secs]
[GC 5534K->5159K(6544K), 0.0054320 secs]
[GC 5671K->5301K(6544K), 0.0114341 secs]
[GC 5813K->5405K(6544K), 0.0103658 secs]
[GC 5917K->5492K(6544K), 0.0053194 secs]
[GC 6003K->5592K(6544K), 0.0107092 secs]
[GC 6104K->5694K(6544K), 0.0096887 secs]
[GC 6206K->5786K(6544K), 0.0037949 secs]
[GC 6298K->5890K(6544K), 0.0101172 secs]
[GC 6402K->5990K(6544K), 0.0041271 secs]
[GC 6502K->6097K(6672K), 0.0040678 secs]
[Full GC 6609K->6191K(10992K), 0.2664733 secs]
Tue Dec 04 15:22:10 PST 2001:<I> <T3Services> CacheManagerImpl: EMAIL
TEMPLATE
C
ACHE STARTING
[GC 6849K->6361K(10992K), 0.0586387 secs]
Tue Dec 04 15:22:10 PST 2001:<I> <T3Services> CacheManagerImpl: SCHEDULE
CACHE
S
TARTING
[GC 7129K->6530K(10992K), 0.0083019 secs]
[GC 7298K->6678K(10992K), 0.0058533 secs]
[GC 7446K->6807K(10992K), 0.0052940 secs]
[GC 7575K->6920K(10992K), 0.0048598 secs]

Setting memory heap size

Hi,
I would like to know how to set the default memory
heap size to 128 MB while installing the Java Plugin
itself.
Is there any environment variable available for setting
this?
I dont want to use the Control Panel option for setting
it.
Thanks for your help.

Hey i have the same issue, how did you solve it?
Hi Gkumarc1,
Plugin 1.3.0 (and after) reads the property filein
.java directory of user's home directory. Java
runtime parameter is saved in the property file.Here
is an example of it:
# Java(TM) Plug-in Properties
# DO NOT EDIT THIS FILE. It is machine generated.
# Use the Activator Control Panel to editproperties.
javaplugin.jre.params=-Xmx 128m
Hope this helps.
Sun-DTSIs there a way to set the default heap size on the
fly? Meaning, we want to avoid the need for our
customers to go into their control panel and make
this setting. Instead, we would like to have the
applet load with our preferred default VM size. This
would allow us to change the preferred size during
some future performance enchancements without having
to contact all of our 2,000+ external customers. Is
there something that can be put in the PARAM tag
within the HTML that specifies the
preferred/recommended default size?
Any help would be greatly appreciated.

Peformance Improvement by increasing heap size

Hi
Is there any performace benefit when I execute my Java application by increasing the default heap size using Java -ms200m -mx200m <appName>
Please support with some performance figures
Regards
Vishal

If you know the size of the heap gows to you can save some time on startup. i.e.
If you know it grows to 100 MB on startup, make this the initial size.
The only diference I have found is when using SoftReference caching. Having more heap size will allow such a cahce keep it data for longer.
I would suggest running the application with -verbosegc to soo how often it garbage collects and how long it spends do it.
If you want to improve performance use a profiles e.g. JProfiler, Optimize-It, JProbe

Configure heap size without -Xmx

Is it possible to configure java to always start with 512M head size without use the -Xmx option. In other words, can I change the default heap size from 64M to 512M or do I have to always start my java with -Xmx512M?

Hi,
Are you really asking whether you can change the maximum heap size, programmatically, from within the JVM? If you do, the answer is that you cannot do that. The JVM needs to pre-allocate a few memory spaces (generations, card table, etc.) while it's starting up and, once it's up and running and starts executing bytecodes, at least some of those memory spaces cannot be resized.
Tony, HS GC Group

How to set the default maximum size for java's heap?

Hi!
Im trying to set the default max size for the java heap - but not from the command line.
I would like to set it higher as default on my computer.. how can I do that?
thanks!

>
...You may increase the memory heap only when you're launching a new JVM.>Much like IWantToBeBig does.
OTOH, it this is an app. with a GUI, it is easier to launch it using webstart, and request extra memory in the JNLP descriptor (the webstart launch file).

The initial heap size must be less than or equal to the maximum heap size.

All,
Please help!!
I have tested my Application Client Project in WSAD on my pc and it works fine.
I have 1gb RAM on my pc. When I deploy the same app on another xp pc(same as mine but 512mb RAM) I get a heap size error. Here is the exact error:
Incompatible initial and maximum heap sizes specified:
initial size: 268435456 bytes, maximum heap size: 267380736 bytes
The initial heap size must be less than or equal to the maximum heap size.
The default initial and maximum heap sizes are 4194304 and 267380736 bytes.
Usage: java [-options] class [args...]
(to execute a class)
or java -jar [-options] jarfile [args...]
(to execute a jar file)
where options include:
-cp -classpath <directories and zip/jar files separated by ;>
set search path for application classes and resources
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version
-showversion print product version and continue
-? -help print this help message
-X print help on non-standard options
Could not create the Java virtual machine.
Press any key to continue . . .
Here is the batch file that runs my app:
@echo off
SET appClientEar=C:\corp\apps\mts\jars\MTSClientEAR.ear
set JVM_ARGS=-Xms256M -Xmx256M
set CLIENT_PROPS=C:\corp\apps\mts\jars\medicalclient.properties
set APP_ARGS=
call C:\bnsf\IBM\WebSphere\AppClient\bin\launchClientBNSF.bat "%JVM_ARGS%" %appClientEar% "-CCpropfile=%CLIENT_PROPS%" %APP_ARGS%
@pause
I have changed the value of Xms and Xmx of JVM_ARGS to different size but I sitll get error. Anyone knows what the problem is. Thanks..

Don't know why, but the "maximum heap size: 267380736 bytes" value is just slightly less than 256*1024*1024, wheras the reported initial size is equal to that.
Try setting the initial value to 255MB.

Massive memory hemorrhage; heap size to go from about 64mb, to 1.3gb usage

**[SOLVED]**
Note: I posted this on stackoverflow as well, but a solution was not found.
Here's the problem:
[1] http://i.stack.imgur.com/sqqtS.png
As you can see, the memory usage balloons out of control! I've had to add arguments to the JVM to increase the heapsize just to avoid out of memory errors while I figure out what's going on. Not good!
##Basic Application Summary (for context)
This application is (eventually) going to be used for basic on screen CV and template matching type things for automation purposes. I want to achieve as high of a frame rate as possible for watching the screen, and handle all of the processing via a series of separate consumer threads.
I quickly found out that the stock Robot class is really terrible speed wise, so I opened up the source, took out all of the duplicated effort and wasted overhead, and rebuilt it as my own class called FastRobot.
##The Class' Code:
    public class FastRobot {
         private Rectangle screenRect;
         private GraphicsDevice screen;
         private final Toolkit toolkit;
         private final Robot elRoboto;
         private final RobotPeer peer;
         private final Point gdloc;
         private final DirectColorModel screenCapCM;
         private final int[] bandmasks;
         public FastRobot() throws HeadlessException, AWTException {
              this.screenRect = new Rectangle(Toolkit.getDefaultToolkit().getScreenSize());
              this.screen = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice();
              toolkit = Toolkit.getDefaultToolkit();
              elRoboto = new Robot();
              peer = ((ComponentFactory)toolkit).createRobot(elRoboto, screen);
              gdloc = screen.getDefaultConfiguration().getBounds().getLocation();
              this.screenRect.translate(gdloc.x, gdloc.y);
              screenCapCM = new DirectColorModel(24,
                        /* red mask */    0x00FF0000,
                        /* green mask */ 0x0000FF00,
                        /* blue mask */   0x000000FF);
              bandmasks = new int[3];
              bandmasks[0] = screenCapCM.getRedMask();
              bandmasks[1] = screenCapCM.getGreenMask();
              bandmasks[2] = screenCapCM.getBlueMask();
              Toolkit.getDefaultToolkit().sync();
         public void autoResetGraphicsEnv() {
              this.screenRect = new Rectangle(Toolkit.getDefaultToolkit().getScreenSize());
              this.screen = GraphicsEnvironment.getLocalGraphicsEnvironment().getDefaultScreenDevice();
         public void manuallySetGraphicsEnv(Rectangle screenRect, GraphicsDevice screen) {
              this.screenRect = screenRect;
              this.screen = screen;
         public BufferedImage createBufferedScreenCapture(int pixels[]) throws HeadlessException, AWTException {
    //          BufferedImage image;
            DataBufferInt buffer;
            WritableRaster raster;
              pixels = peer.getRGBPixels(screenRect);
              buffer = new DataBufferInt(pixels, pixels.length);
              raster = Raster.createPackedRaster(buffer, screenRect.width, screenRect.height, screenRect.width, bandmasks, null);
              return new BufferedImage(screenCapCM, raster, false, null);
         public int[] createArrayScreenCapture() throws HeadlessException, AWTException {
                   return peer.getRGBPixels(screenRect);
         public WritableRaster createRasterScreenCapture(int pixels[]) throws HeadlessException, AWTException {
         //     BufferedImage image;
             DataBufferInt buffer;
             WritableRaster raster;
              pixels = peer.getRGBPixels(screenRect);
              buffer = new DataBufferInt(pixels, pixels.length);
              raster = Raster.createPackedRaster(buffer, screenRect.width, screenRect.height, screenRect.width, bandmasks, null);
         //     SunWritableRaster.makeTrackable(buffer);
              return raster;
    }In essence, all I've changed from the original is moving many of the allocations from function bodies, and set them as attributes of the class so they're not called every time. Doing this actually had a significant affect on frame rate. Even on my severely under powered laptop, it went from ~4 fps with the stock Robot class, to ~30fps with my FastRobot class.
##First Test:
When I started outofmemory errors in my main program, I set up this very simple test to keep an eye on the FastRobot. Note: this is the code which produced the heap profile above.
    public class TestFBot {
         public static void main(String[] args) {
              try {
                   FastRobot fbot = new FastRobot();
                   double startTime = System.currentTimeMillis();
                   for (int i=0; i < 1000; i++)
                        fbot.createArrayScreenCapture();
                   System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
              } catch (AWTException e) {
                   e.printStackTrace();
    }##Examined:
It doesn't do this every time, which is really strange (and frustrating!). In fact, it rarely does it at all with the above code. However, the memory issue becomes easily reproducible if I have multiple for loops back to back.
#Test 2
    public class TestFBot {
         public static void main(String[] args) {
              try {
                   FastRobot fbot = new FastRobot();
                   double startTime = System.currentTimeMillis();
                   for (int i=0; i < 1000; i++)
                        fbot.createArrayScreenCapture();
                   System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
                   startTime = System.currentTimeMillis();
                   for (int i=0; i < 500; i++)
                        fbot.createArrayScreenCapture();
                   System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
                   startTime = System.currentTimeMillis();
                   for (int i=0; i < 200; i++)
                        fbot.createArrayScreenCapture();
                   System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
                   startTime = System.currentTimeMillis();
                   for (int i=0; i < 1500; i++)
                        fbot.createArrayScreenCapture();
                   System.out.println("Time taken: " + (System.currentTimeMillis() - startTime)/1000.);
              } catch (AWTException e) {
                   e.printStackTrace();
    }##Examined
The out of control heap is now reproducible I'd say about 80% of the time. I've looked all though the profiler, and the thing of most note (I think) is that the garbage collector seemingly stops right as the fourth and final loop begins.
The output form the above code gave the following times:
Time taken: 24.282 //Loop1
Time taken: 11.294 //Loop2
Time taken: 7.1 //Loop3
Time taken: 70.739 //Loop4
Now, if you sum the first three loops, it adds up to 42.676, which suspiciously corresponds to the exact time that the garbage collector stops, and the memory spikes.
[2] http://i.stack.imgur.com/fSTOs.png
Now, this is my first rodeo with profiling, not to mention the first time I've ever even thought about garbage collection -- it was always something that just kind of worked magically in the background -- so, I'm unsure what, if anything, I've found out.
##Additional Profile Information
[3] http://i.stack.imgur.com/ENocy.png
Augusto suggested looking at the memory profile. There are 1500+ `int[]` that are listed as "unreachable, but not yet collected." These are surely the `int[]` arrays that the `peer.getRGBPixels()` creates, but for some reason they're not being destroyed. This additional info, unfortunately, only adds to my confusion, as I'm not sure why the GC wouldn't be collecting them
##Profile using small heap argument -Xmx256m:
At irreputable and Hot Licks suggestion I set the max heap size to something significantly smaller. While this does prevent it from making the 1gb jump in memory usage, it still doesn't explain why the program is ballooning to its max heap size upon entering the 4th iteration.
[4] http://i.stack.imgur.com/bR3NP.png
As you can see, the exact issue still exists, it's just been made smaller. ;) The issue with this solution is that the program, for some reason, is still eating through all of the memory it can -- there is also a marked change in fps performance from the first the iterations, which consume very little memory, and the final iteration, which consumes as much memory as it can.
The question remains why is it ballooning at all?
##Results after hitting "Force Garbage Collection" button:
At jtahlborn's suggestion, I hit the Force Garbage Collection button. It worked beautifully. It goes from 1gb of memory usage, down to the basline of 60mb or so.
[5] http://i.stack.imgur.com/x4282.png
So, this seems to be the cure. The question now is, how do I pro grammatically force the GC to do this?
##Results after adding local Peer to function's scope:
At David Waters suggestion, I modified the `createArrayCapture()` function so that it holds a local `Peer` object.
Unfortunately no change in the memory usage pattern.
[6] http://i.stack.imgur.com/Ky5vb.png
Still gets huge on the 3rd or 4th iteration.
#Memory Pool Analysis:
###ScreenShots from the different memory pools
##All pools:
[7] http://i.stack.imgur.com/nXXeo.png
##Eden Pool:
[8] http://i.stack.imgur.com/R4ZHG.png
##Old Gen:
[9] http://i.stack.imgur.com/gmfe2.png
Just about all of the memory usage seems to fall in this pool.
Note: PS Survivor Space had (apparently) 0 usage
##I'm left with several questions:
(a) does the Garbage Profiler graph mean what I think it means? Or am I confusing correlation with causation? As I said, I'm in an unknown area with these issues.
(b) If it is the garbage collector... what do I do about it..? Why is it stopping altogether, and then running at a reduced rate for the remainder of the program?
(c) How do I fix this?
Does anyone have any idea what's going on here?
[1]: http://i.stack.imgur.com/sqqtS.png
[2]: http://i.stack.imgur.com/fSTOs.png
[3]: http://i.stack.imgur.com/ENocy.png
[4]: http://i.stack.imgur.com/bR3NP.png
[5]: http://i.stack.imgur.com/x4282.png
[6]: http://i.stack.imgur.com/Ky5vb.png
[7]: http://i.stack.imgur.com/nXXeo.png
[8]: http://i.stack.imgur.com/R4ZHG.png
[9]: http://i.stack.imgur.com/gmfe2.png
Edited by: 991051 on Feb 28, 2013 11:30 AM
Edited by: 991051 on Feb 28, 2013 11:35 AM
Edited by: 991051 on Feb 28, 2013 11:36 AM
Edited by: 991051 on Mar 1, 2013 9:44 AM

SO came through.
Turns out this issue was directly related to the garbage collector. The default one, for whatever reason, would get behind on its collection at points, and thus the memory would balloon out of control, which then, once allocated, became the new normal for the GC to operate at.
Manually setting the GC to ConcurrentMarkSweep solved this issue completely. After numerous tests, I have been unable to reproduce the memory issue. The garbage collector does an excellent job of keeping on top of these minor collections.

Invalid initial heap size error when starting weblogic server 11g R1

I installed JDeveloper Studio 11.1.1.2.0 . When iItried to start weblogic server 11g R1, I had this message :
starting weblogic with Java version:
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1.5-3\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=C:\Oracle\Middleware\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Ddomain.home=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\config\FMWCON~1 -Doracle.server.config.dir=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.security.jps.config=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=\modules\oracle.ossoiap_11.1.1,\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=C:\DOCUME~1\Admin\APPLIC~1\JDEVEL~1\SYSTEM~1.36\DEFAUL~1\oracle\store\gmds "-Xms512m -Xmx512m" -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath weblogic.Server
Could not create the Java virtual machine.
Invalid initial heap size: -Xms512m -Xmx512m
Process exited.
Please, how can I fixe this error ?

For 2 GB machine set the parameters as below:
/ide/bin/ide.conf
AddVMOption -Xmx1232M
AddVMOption -Xms64M
/jdev/bin/jdef.conf
AddVMOption -XX:MaxPermSize=128M
For 3 GB machine set the parameters as below:
/ide/bin/ide.conf
AddVMOption -Xmx1488M
AddVMOption -Xms64M
/jdev/bin/jdef.conf
AddVMOption -XX:MaxPermSize=128M

Default Heap Size

Similar Messages

Maybe you are looking for