NetBeans and Heap Size

I'm trying to write a program using NetBeans and I keep getting OutOfMemoryErrors. I have 2GB of RAM and I've attempted to modify the netbeans.conf file to increase the heap size at startup. The changes I've made aren't being reflected in the memory manager tool (it still indicates a maximum size of ~50MB). The pertinent code from the config file is as follows:
netbeans_default_options="-J-Xms512m -J-Xmx1024m -J-XX:PermSize=128m -J-XX:MaxPermSize=512m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true -J-XX:NewSize256m"
Assuming my memory usage won't exceed these limits, any suggestions as to how to make sure the changes are being implemented?

I would subscribe to the netbeans user mail list, and pose your question to that list. The Sun Netbeans gurus live there.
I would also use a seperate email account to subscribe to the list as it generates alot of messages daily. If thats not an option, definatly try to set up a rule that seperates messages from the list from your regular email.
The main netbeans top level mail list web page is here with all the instructions to subscribe and unsubscribe.
Good luck,
JJ

Similar Messages

NT Service and Heap size

Can someone tell me if there is a way to :
(1) verify and modify heap size in nt service?
(2) in multi server mode, there are two nt services for weblogic
domains, is it needed to change heap size for weblogicAdmin service for
heap size increase? What will happen if PIA is 1024MB heap size and
weblogicAdmin is 256MB?
Thanks in advance/T

Nicolas, test show that once the nt service is installed, modifying heap
size in setenv.cmd and run setenv.cmd file reinstall nt service does not
change the heap size already in registry. So, test shows that I can
modify the heap size directly in registry and restart service?. Am i doing something wrong here.. can i correct and only to modify and existing heap size in
registry?
Please let me know what else should I do once the old heap
size in already in registry and not the new heap size when reinstalled NT service.
other question, long the weblogic tuning, I found the following from bea site. During the peak time, we may have 40000 unique users per day. Should I also consider increase maxUserPort? The weblogic domains are hosted on windows 2003 servers.
Windows Tuning Parameters
For Windows platforms, the default settings are usually sufficient. However, under sufficiently heavy loads it may be necessary to adjust the MaxUserPort and TcpTimedWaitDelay. These parameters determine the availability of user ports requested by an application.
By default, ephemeral (that is, short-lived) ports are allocated between the values of 1024 and 5000 inclusive using the MaxUserPort parameter. The TcpTimedWaitDelay parameter, which controls the amount of time the OS waits to reclaim a port after an application closes a TCP connection, has a default value of 4 minutes. During a heavy loads, these limits may be exceeded resulting in an address in use: connect exception. If you experience address in use: connect exceptions try setting the MaxUserPort and TcpTimedWaitDelay registry values under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters key:
MaxUserPort = dword:00004e20 (20,000 decimal)
TcpTimedWaitDelay = dword:0000001e (30 decimal)
Increase the value of the MaxUserPort parameter if the exception persists.
For more information about Windows 2000 tuning options, see:
§ The Microsoft Windows 2000 TCP/IP Implementation Details.
§ The Windows 2000 Performance Tuning white paper.
thanks
T

Large heap sizes, GC tuning and best practices

Hello,
I’ve read in the best practices document that the recommended heap size (without JVM GC tuning) is 512M. It also indicates that GC tuning, object number/size, and hardware configuration play a significant role in determining what the optimal heap size is. My particular Coherence implementation contains a static data set that is fairly large in size (150-300k per entry). Our hardware platform contains 16G physical RAM available and we want to dedicate at least 1G to the system and 512M for a proxy instance (localstorage=false) which our TCP*Extend clients will use to connect to the cache. This leaves us 14.5G available for our cache instances.
We’re trying to determine the proper balance of heap size vs num of cache instances and have ended up with the following configuration. 7 cache instances per node running with 2G heap using a high-units value of 1.5G. Our testing has shown that using the Concurrent Mark Sweep GC algorithm warrants no substantial GC pauses and we have also done testing with a heap fragmentation inducer (http://www.azulsystems.com/e2e/docs/Fragger.java) which also shows no significant pauses.
The reason we opted for a larger heap was to cut down on the cluster communication and context switching overhead as well as the administration challenges that 28 separate JVM processes would create. Although our testing has shown successful results, my concern here is that we’re straying from the best practices recommendations and I’m wondering what others thoughts are about the configuration outlined above.
Thanks,
- Allen Bettilyon

Hello,
I’ve read in the best practices document that the recommended heap size (without JVM GC tuning) is 512M. It also indicates that GC tuning, object number/size, and hardware configuration play a significant role in determining what the optimal heap size is. My particular Coherence implementation contains a static data set that is fairly large in size (150-300k per entry). Our hardware platform contains 16G physical RAM available and we want to dedicate at least 1G to the system and 512M for a proxy instance (localstorage=false) which our TCP*Extend clients will use to connect to the cache. This leaves us 14.5G available for our cache instances.
We’re trying to determine the proper balance of heap size vs num of cache instances and have ended up with the following configuration. 7 cache instances per node running with 2G heap using a high-units value of 1.5G. Our testing has shown that using the Concurrent Mark Sweep GC algorithm warrants no substantial GC pauses and we have also done testing with a heap fragmentation inducer (http://www.azulsystems.com/e2e/docs/Fragger.java) which also shows no significant pauses.
The reason we opted for a larger heap was to cut down on the cluster communication and context switching overhead as well as the administration challenges that 28 separate JVM processes would create. Although our testing has shown successful results, my concern here is that we’re straying from the best practices recommendations and I’m wondering what others thoughts are about the configuration outlined above.
Thanks,
- Allen Bettilyon

"Incompatiable initial and maximum heap sizes specified" error

Hi,
Using the command below:
java -jar -Xms128m myjar.jar
I get the following errors:
"Error occurred during initialization of VM"
"Incompatiable initial and maximum heap sizes specified"
but if I take off the initial heap size parameter, just run:
java -jar myjar.jar
it works fine apart from that the heap size is not desired.
Can anyone please tell me what's the cause of the problem here? I'm suspecting the JVM has been configured to restrict manual adjustment of heap sizes...
Many thanks.

Hi,
Using the command below:
java -jar -Xms128m myjar.jar
I get the following errors:
"Error occurred during initialization of VM"
"Incompatiable initial and maximum heap sizes
specified"
but if I take off the initial heap size parameter,
just run:
java -jar myjar.jar
it works fine apart from that the heap size is not
desired.
Can anyone please tell me what's the cause of the
problem here? I'm suspecting the JVM has been
configured to restrict manual adjustment of heap
sizes...
Many thanks.It turns out that I need to also specify the maximum heap size as well. Thanks.

How to increase Memory and Java Heap Size for Content Server

Hi,
My content server is processing requests very slowly. Over performance is not good. I have 2 GB of RAM any idea what files I can modify to increase the Java Heap Size for the Content Server. If I increase the RAM to 4 or 6 GB where do I need to make changes for the Java Heap Size and what are the recommended values. I just have Content Server Running on the linux box. Or how do I assign more memory to the user that owns the content server install.
Thanks

You might find these interesting:
http://blogs.oracle.com/fusionecm/2008/10/how_to_-javatuning.html
http://download.oracle.com/docs/cd/E10316_01/cs/cs_doc_10/documentation/admin/performance_tuning_10en.pdf
Do you have access to metalink? This has about everything you could want:
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9940589543422282072::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,788210.1,1,1,1,helvetica
Or search for "788210.1" in metalink knowledgebase if that link doesn't work and look for the FAQ on configuring Java for Content Servers

Heap size and 3 table update

I am new to this area so sorry if my questions will sound stupid to somebody. Recently I started developing an application using Toplink, ADF Databinding, struts and JSP. Curretnly the application is using 1 view built on 3 tables.
QUESTION 1: First time when I tried to test the browse page I got the error messages from JDeveloper saying "JBO-29000: Unexpected exception caught: java.lang.OutOfMemoryError, msg=null". So I limited number of records selected by the view just to 500 and the query worked. I guess it is somehow related to java heap size. How can I change the heap size. The application is run locally on my PC.
QUESTION 2: In this application I am trying to update 3 tables at the same time using a view. But when I try do it I am getting error saying "data manipulation operation non legal on this view error code 1732". Is there any way I can do this simultaneous update of 3 tables through the view?
Thanks in advance for any help, advice or hint

The switch -Djbo.debugoutput=console should produce messages in the debug output window like [694] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[695] **PCollManager.resolveName** tabName=PS_TXN
[696] Getting a connection for internal use...
[697] Creating internal connection...
[698] Trying connection: DataSource='com.evermind.sql.OrionCMTDataSource@20e'...
[699] Column count: 4
[700] ViewObject: BenutzerSessionView1 close prepared statements...
[701] ViewObject: BenutzerSessionView1 Created new QUERY statement
[702] BenutzerSessionView1>#q computed SQLStmtBufLen: 250, actual=222, storing=252
[703] SELECT BenutzerSession.BENUTZER_ID, BenutzerSession.SESSION_ID, BenutzerSession.ANMELDEZEIT, BenutzerSession.LETZTER_ZUGRIFF FROM BENUTZERSESSION BenutzerSession WHERE (BenutzerSession.SESSION_ID=?)
[704] Bind params for ViewObject: BenutzerSessionView1
[705] Binding param 1: 998949578152
[706] Column count: 19
[707] ViewObject: BenutzerView1 close prepared statements...What I did is build a VO from 3 EO. Not every attribute of the EO are used in the VO and the EO are associated via their PK. I started my implementation from the toystore demo (take a look add the accounts VO or ReviewOrder VO and the ToyStorService prepareToCreateNewAccount(...)).
P.S. I'm from Germany

Incompatible initial and maximum heap sizes specified

At first my program was crashing, saying;
java.lang.OutOfMemoryError: Java heap space
So I added this vm argument: -Xms128M
Now, i get this message:
Incompatible initial and maximum heap sizes specified
What do I do?

At first my program was crashing, saying;
java.lang.OutOfMemoryError: Java heap space
So I added this vm argument: -Xms128M
Now, i get this message:
Incompatible initial and maximum heap sizes
specified
What do I do?Specify a maximum heap size (-Xmx) as well (and make that be greater than or equal to the minimum size).

JPDA Initial Heap Size

Please tell me how to change the default initial and max heap size for JPDA / debugee programs.
The typical non-standard options do not seem to work -
-Xms128m -Xmx256m
I am also using the following options -
-agentlib:jdwp=transport=dt_socket,server=y,address=8000
with JDK 5 (build 1.5.0_06-b05) and NB 5 (200601251500)
Thanks,
Jeff

You may want to post this question on NetBeans forums (http://www.netbeans.org/community/lists/top.html) especially [email protected] (http://www.netbeans.org/servlets/SummarizeList?listName=nbusers), where the debugger experts are...
btw, have you tried '-J-Dnetbeans.debugger.jpda.transport=dt_shmem' startup option?
According to http://www.netbeans.org/kb/41/using-netbeans/configuring.html#performance_switches:
Force the IDE to use the shared memory connection when starting a debugging session with the Debug >Start command. This parameter has no effect when you attach the debugger to an already running process.
This may use the -X parameters passed to ide itself...

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.

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.

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.

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.

Problem increasing heap size using Java Control Panel

I am running a web-based bioinformatics package which uses a Java applet as the client application. It mostly works fine, but some large clustering processes don't complete, they just cycle endlessly. The user manual advises increasing heap space "by entering the following command in the Java Control Panel or Java Plug-in dialog: -Xms128M -Xmx256M." I can open the Java Control Panel OK and enter the necessary command in the Java Runtime Parameters box, but after clicking OK then Apply, the Runtime Parameters box is empty again and there is no increase in the heap size allocation. In other words, the change doesn't take effect.
I have already tried: adjusting one parameter at a time (max heap size first, then min); changing uppercase to lowercase M (-Xmx256m); restarting the browser after the change; rebooting my PC - none of these has helped.
Technical details: it's Java 6 standard edition, build 1.6.0_10-rc-b28; browser is Internet Explorer 7; operating system is Vista (Service Pack 1); PC is a 2.4 GHz processor with 2 GB RAM (so I have plenty available to allocate to Java). I have local admin privilege on my PC.
Help would be much appreciated, as I really need to complete these cluster analyses. I'm a biologist not a developer, so ideally I need a solution that doesn't involve major programming, though I'm OK with registry edits and use of the command line. Thanks in advance.

The failure to retain the parameters is a bug, per hdong in this [Java,net thread|http://forums.java.net/jive/thread.jspa?threadID=44540&tstart=0] dated August 14
"I did a little more research and found out that the problem is only with "-rc" or "-beta" versions of plugin. When 1.6.0_10 is finally released, the version string will be "1.6.0_10". Plugin works fine to set/get jvm parameters when version string is "1.6.0_10".
I am surprised that this issue was not discovered earlier. It was probably because the internal test binary use "1.6.0_10" as version string.
Yeah, it is a bug that will affect many manny developers. It will be fixed as soon as possible."

JVM heap size limit under Windows

Hi,
I'm looking either for some help with a workaround, or
confirmation that the information I've found is still the case for the
current state of Java.
Development machine is Win XP Pro, 2G RAM.
Biggest heap I can allocate is about 1.6G, and that is not large enough for this
app.
I have a Swing application that
1) must run on Win XP, 32 bit
2) must implement an editor (similar to Excel but with fewer features) to handle large csv files
( up to about 800Mb).
3) Strong preference for Java 5, though higher could conceivably be supported.
Research so far tells me that this is the result of process memory limitations
of Windows and the JVM, and that I might be able to squeeze a little more heap with
Windows' rebase command, but probably not enough and I would start running the
risk of conflicts with other applications on my users' systems. Ugh.
Also I read of the Windows /3GB switch, but posts say that the JDK's available are not
built to be able to use that feature. I havent had a chance to add memory to
test that yet. However, I'm also under the impression that I should be able to
allocate a heap larger than physical RAM ... except for that process size limit.
So ... my information is basically that I'm stuck with a limit of about 1.6G for
heap size, regardless of the RAM on my computer.
Can anyone confirm whether that is still correct, preferably with a pointer to some
official reference ?
Or better yet, point me toward a workaround?
Thanks!
-tom

>
Some bookmarks I have on this topic.
http://sinewalker.wordpress.com/2007/03/04/32-bit-windows-and-jvm-virtual-memory-limit/
http://stackoverflow.com/questions/171205/java-maximum-memory-on-windows-xp
The first link pulled together what I found in lots of bits and pieces elsewhere, nice to have a coherent summary :)
The second link offered a bit of insight into the jvm that I hadn't seen yet .
Thanks!

How to set the maximum heap size on a deployed application?

I�m running a fairly large java application and am getting java.lang.OutOfMemoryError. I could increase the heap size in my development environment to eliminate this error. However, I don�t know how to set this in a deployed application. We are currently using ant to build our software.
Another question, when I execute a statement such as java �Xmx512M �cp app.jar. Is it correct to say that the application in app.jar will use to a maximum of 512MB of memory when running?
Thank you everyone for your help!

But first, when you say "a deployed environment" do you mean an executable .jar file? This is what I'm using.The term "deploy" is commonly used to refer to deploying an ear file or a war file on an application server.
I would assume that there is some entry you can include in the .jar's
Manifest.mf file to specify the maximum memory, but I can't find an example of the entry. <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6197671"></a>

NetBeans and Heap Size

Similar Messages

Maybe you are looking for