Too low initial heap size

Hi,
Any idea why following line is giving too low initial heap size error in server startup.
$JAVA_HOME/bin/java $JAVA_VM -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=6 -Xms2048m -Xmx2048m -Xrs -verbose:gc
This error is coming when I am adding -XX:NewSize=256m -XX:MaxNewSize=256m parameters.
Thanks in advance.
Regards,
Chintan.

Just a thought: maybe you should use both,
initial-heap-size="128m" max-heap-size="256m"
I think the Client JVM defaults to max 64m, so setting the initial heap to 128m would set initial bigger than max, which leads to an error.
hope that helps...
Patric

Similar Messages

Invalid initial heap size Problem with sdk1.4.2_03

Hi,
ich habe a troubling error with the java version 1.4.2_03.
I use an Ant Task to start a Weblogic Server (J2EE Server). For this, I use the following Ant code :
-----ANT CODE------------------------------------------------------------------------------------------------------------------------
<java classname="weblogic.Server" fork="true" failonerror="true" dir="${weblogic.domain.dir}">
<sysproperty key="bea.home" value="${bea.home.dir}"/>
<sysproperty key="weblogic.Name" value="${weblogic.admin.server.name}"/>
<sysproperty key="weblogic.management.username" value="${weblogic.user.name}"/>
<sysproperty key="weblogic.management.password" value="${weblogic.user.password}"/>
<sysproperty key="weblogic.ProductionModeEnabled" value="false"/>
<sysproperty key="java.security.policy" value="${weblogic.home.dir}\server\lib\weblogic.policy"/>
<sysproperty key="weblogic.security.SSL.trustedCAKeyStore" value="${weblogic.home.dir}\server\lib\cacerts"/>
<jvmarg value="-Xms32m -Xmx200m"/>
<classpath>
<pathelement path="${windows.classpath.wls}"/>
</classpath>
</java>
-----/ANT CODE------------------------------------------------------------------------------------------------------------------------
This Task perfectly works with the sdk java version 1.4.1_05, but I have the following message with the sdk java version 1.4.2_03 :
-----ERROR MESSAGE---------------------------------------------------
Invalid initial heap size: -Xms32m -Xmx200m
Could not create the Java virtual machine.
-----/ERROR MESSAGE---------------------------------------------------
The following parameter is anymore correct : <jvmarg value="-Xms32m -Xmx200m"/>
I have tried with a lot of possibilty, 64-200, 128-200, 128-128, 256-256, 512-512, nothing works.
I have tried without this parameter, this works fine.
I have tried with the weblogic server without the Ant Task, and this works fine too.
I think this is a bug in the JVM 1.4.2_03.
What do you think about this problem ??? Do you have some solution ???
I have also tried with another version of ant, I have the same problem. This works with JVM 1.4.1_05 and not with JVM 1.4.2_03.
If you have an idea, please, help.
Thanks

If you can start a 1.4.2 JVM with all these parameters independently (i.e. not from Ant) and it works, but from Ant it doesn't work, it's more likely that the problem is somehow related to interaction between Ant and the JVM, rather than the JVM itself. So I would suggest trying some Ant forum first - I think it would also work faster than if you try to submit this bug to Sun.

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.

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

Invalid initial heap size in JVM 1.4.2_04 on Solaris 9 machine

Hi,
While running this command.
# java -Xms8096m -Xmx8096m newserver.sh
I am getting the following error:
Invalid initial heap size: -Xms5000m
Could not create the Java virtual machine
I tried with - server option also. But same error. Can any one tell me what is the limit of heap size allowed in Solaris 9? Plz tell me work around for this.
Thanks,
Vasanth.

cvringer wrote:
I really hate this responses. If you bother others with your problems, at least take the trouble of informing others about the solution. You made this whole post worthless.Reply #2 answers the question. You need a 64-bit VM.
I'm locking this zombie thread.
Kaj

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...

"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 do I know if my image resolution is too low now that the yellow triangle warning is gone?

I am creating a book in iPhoto 11 for the first time. In older versions, I would get a yellow triangle indicating my image quality was too low for that size image. Based on other threads, it looks like iPhoto no longer gives the warning. What is the best way to know if the image will print okay? Is there a workaround so I can check the quality of the image prior to printing out the book?

I noticed that there's not resolution waring also. Create a PDF file of the book and look at the pages at full sized with Preview and determine if the photos are sharp enough for you.
I ran a test with two images, one 4000 x 3000 pixels and the other 230 x 200 pixels in a 2 photo per page book page and then created a pdf of the book, Modern Lines theme. This is a screenshot of the page in Preview at View ➙ View Full Sized:
This screenshot is of the same photo in a different 2 photo per page layout in the same theme. It does look more like I expected:
Right click on the image and select Show in New Window from the Contextual menu. I'm really surprised the first example of the small image looked as good as it did. I expected a very pixelated image like the second example but iPhoto upsized it rather nicely. So iPhoto can upsize a small photo to some degree but I don't recommend relying on it for such small images. And it is a very, very, very small image. Soif your image is reasonably large you should be OK. But check it in the PDF file.
OT

How to set max-heap-size outside the jnlp file?

Due to bug_id=6631056 It may not be possible to specify max-heap-size within
the JNLP file for certain jnlp java applications.
Are there other possibilities to specify this Jvm parameter?
In the ControlPanel there is the possibility to specify Xmx for applets but not for jnlp.
I have tried to add properties like
"deployment.javaws.jre.0.args=Xmx\=128M" without success
Many thanks

Even in JNLP also you can specify the max heap size
<j2se version="1.5+" initial-heap-size="128m" max-heap-size="512m"/>
Thanks,
Suresh
[http://sureshdevi.co.in|http://sureshdevi.co.in]

How to set the heap size of JVM

please let me know that how to set the heap size of JVM

C:\>java -X
    -Xmixed           mixed mode execution (default)
    -Xint             interpreted mode execution only
    -Xbootclasspath:<directories and zip/jar files separated by ;>
                      set search path for bootstrap classes and resources
    -Xbootclasspath/a:<directories and zip/jar files separated by ;>
                      append to end of bootstrap class path
    -Xbootclasspath/p:<directories and zip/jar files separated by ;>
                      prepend in front of bootstrap class path
    -Xnoclassgc       disable class garbage collection
    -Xincgc           enable incremental garbage collection
    -Xbatch           disable background compilation
    -Xms<size>        set initial Java heap size
    -Xmx<size>        set maximum Java heap size
    -Xss<size>        set java thread stack size
    -Xprof            output cpu profiling data
    -Xrunhprof[:help]|[:<option>=<value>, ...]
                      perform JVMPI heap, cpu, or monitor profiling
    -Xdebug           enable remote debugging
    -Xfuture          enable strictest checks, anticipating future default
    -Xrs              reduce use of OS signals by Java/VM (see documentation)look at the -Xm? lines
    -Xms<size>        set initial Java heap size
    -Xmx<size>        set maximum Java heap sizeThis can be used e.g. like this:java -Xms8M -Xmx32M MyProgwhich runs MyProg in a java VM with the initial heap size of 8 MB and a maximum heap size of 32 MB.
- Marcus

Java.lang.OutOfMemoryError:class Your Java heap size might be set too high.

I am getting the below error while deploying some soa applications in WLS 10.3 on solaris platform.As a workaround,
the server instance has to be restarted everytime i make the deployments when i face this OOM situations.
usually i face this issue after first deployment onwards.
So, everytime i make the next deployment the server instance has to be restarted before that.
The server is configured with 1Gb JVM and runs on JRockit jrrt-4.0.0-1.6.0.
MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
fMemoryError -XXcompressedRefs:enable=true"
Can anybody please provide any pointers to track/solve this issue?
Log extract:
####<Oct 10, 2010 4:27:31 PM PST> <Error> <Deployer> <BOX1> <SERVER2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1256893524756> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1256893524756' for task '3'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.OutOfMemoryError: class allocation, 21977184 loaded, 20M footprint in check_alloc (classalloc.c:213) 1412 bytes requested.
Java heap 1G reserved, 1G committed
Paged memory=18014398507524232K/16781304K.
Your Java heap size might be set too high.
Try to reduce the Java heap
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:335)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:288)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1058)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1129)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:542)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:435)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Its running on Solaris 10 platform.The server is configured with 1Gb JVM and JRockit jrrt-4.0.0-1.6.0.
MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
fMemoryError -XXcompressedRefs:enable=true"
Let me know if you need any more information to track this issue.

Does the jvm allocate complete max heap size initially?

Does the JVM allocate the memory for the entire max heap size up front, or does it start with the specified minimum size and increase and grab more later if needed?
The reason this is being posted is because we have a number of jboss servers that are being run. Some don't require large heap sizes, others do. If we use the same large max heap size for all would all the memory get allocated up front, or possibly a smaller initialization portion?

I have done the test with Solaris, Linux and WinXP.
Test with -Xms512M
Have written a simple java program to which the minimum heap size was set to -Xms512m then the program was executed on Solaris and WinXP platforms. The usage of memory of the Java process was 6 MB in WinXP and 9 MB in Solaris, rather than 512 MB. The JVM is not allocating the configured minimum size of 512 MB at the start of the process execution.
Reason:
If you ask the OS for 512 MB it'll say "here it is", but pages won't actually be allocated until your app actually touches them.
If the allocation is not being made initially during the start of the process, the concept of minimum heap size is not required.
But the garbage collection log shows the minimum heap size as what was configured using -Xms option.
Test with -Xms1024M
The JVM arguments was set to : -Xms1024m -Xmx1024m, but the used memory observed using Windows perfmon was 573M.
6.524: [Full GC 6.524: [Tenured: 3081K->10565K(967936K), 0.1949291 secs] 52479K->10565K(1040512K), [Perm : 12287K->12287K(12288K)], 0.1950893 secs] Reason:
Optimization is something that the operating systems do. The JVM allocates the memory in it's address space and initializes all data structures to your -Xms. In any way that the JVM can measure, the allocation from the OS is complete. But the OS doesn't physically assign a page to the app until the first store instruction. Almost all modern OSs do this.
Hope this is helpful.

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).

Too large java heap error while starting the domain.Help me please..

I am using weblogic 10.2,after creating the domain, while starting the domain,I am getting this error.Can anyone help me.Please treat this as urgent request..
<Oct 10, 2009 4:09:24 PM> <Info> <NodeManager> <Server output log file is "/nfs/appl/XXXXX/weblogic/XXXXX_admin/servers/XXXXX_admin_server/logs/XXXXX_admin_server.out">
[ERROR] Too large java heap setting.
Try to reduce the Java heap size using -Xmx:<size> (e.g. "-Xmx128m").
You can also try to free low memory by disabling
compressed references, -XXcompressedRefs=false.
Could not create the Java virtual machine.
<Oct 10, 2009 4:09:25 PM> <Debug> <NodeManager> <Waiting for the process to die: 29643>
<Oct 10, 2009 4:09:25 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 10, 2009 4:09:25 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Thanks Kevin.
Let me try that.
Already more than 8 domains were successfully created and running fine.Now the newly created domain have this problem.I need 1GB for my domain.Is there any way to do this?

Iseries Settings for JAVA (Heap sizes)

I am new to SAP, not to Iseries. The notes 717376 and 990892 give me insight as to what needs chging but not the how to change it.
I want to know if I can set the heap sizes directly in the IFS and How. Our consultants are not ISeries strong... I can not get the Config tool to work, and Visual Admin is too
foreign for me to find where the sizing is.
PI takes way to long to start up and my guess is we need initial heapsize to be set and max increased.
thank you

Hi
I am not sure about iSeries but the configuration of parameters in SAP Java stack always affect the Java system performance. The few steps to change parameters are as follows:
Main point is you have to use the configtool only. You cannot use Visual Administrator to change the memory parameters.
Open the ConfigTool ( usr/sap/<SID>/DVEBMGS<sys nr>/j2ee/configtool file would be configtool.sh)
Then at the left hand pane you would get the Server and Instances (local and global : these are used for the cluster environment; local means that you are logged into the current instance....global means that you want to change the settings for whole of the Java stack)
If you click on them like Instance_<instance number>; right hand side you would get all the parameters where you can change these settings.
Follow the notes instructions.
It would ask for the restart of the SAP server
check this link
http://www-03.ibm.com/systems/i/advantages/sapj2ee/tuning.html

Too low initial heap size

Similar Messages

Maybe you are looking for