Java heap space java.lang.OutOfMemoryError coming in weblogic server

Question

Hi All,
I am getting following out of memory exception on BCC server start up.
<Nov 13, 2013 3:17:09 AM IST> <Critical> <Health> <BEA-310003> <Free memory in the server is 1,134,688 bytes. There is danger of OutOfMemoryError>
Exception in thread "Timer-2" java.lang.OutOfMemoryError: Java heap space
        at java.util.AbstractCollection.toArray(AbstractCollection.java:119)
        at java.util.ArrayList.<init>(ArrayList.java:131)
        at javax.jmdns.impl.DNSCache.getCacheNodes(DNSCache.java:223)<Nov 13, 2013 3:17:28 AM IST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
        at javax.jmdns.impl.tasks.RecordReaper.run(RecordReaper.java:48)
        at java.util.TimerThread.mainLoop(Timer.java:512) java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
        at java.util.TimerThread.run(Timer.java:462)
        at java.lang.reflect.Array.newArray(Native Method)
Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: Java heap space
        at java.lang.reflect.Array.newInstance(Array.java:52)   at java.lang.reflect.Array.newArray(Native Method)
        at java.lang.reflect.Array.newInstance(Array.java:52)
        at java.util.AbstractCollection.toArray(AbstractCollection.java:159)    at java.util.AbstractCollection.toArray(AbstractCollection.java:159)
        at java.util.Collections$SynchronizedCollection.toArray(Collections.java:1569)
        at atg.service.jdbc.FakeXAResource.recover(FakeXAResource.java:430)
        at weblogic.transaction.internal.XAServerResourceInfo.recover(XAServerResourceInfo.java:1019)   at java.util.Collections$SynchronizedCollection.toArray(Collections.java:1569)
        at weblogic.transaction.internal.ServerSCInfo.recover(ServerSCInfo.java:645)
        at weblogic.transaction.internal.XAResourceDescriptor.getXidsToBeRolledBack(XAResourceDescriptor.java:1137)
        at atg.service.jdbc.FakeXAResource.recover(FakeXAResource.java:430)
        at weblogic.transaction.internal.XAResourceDescriptor.recover(XAResourceDescriptor.java:1073)
        at weblogic.transaction.internal.XAResourceDescriptor.access$100(XAResourceDescriptor.java:60)
        at weblogic.transaction.internal.XAResourceDescriptor$2.run(XAResourceDescriptor.java:823)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
        Truncated. see log file for complete stacktrace
I think this can't be issue with following variables:As I hv set them from 64m to 256, still issue coming.
WLS_MEM_ARGS_32BIT=-Xms200m -Xmx256m
MEM_PERM_SIZE_32BIT=-XX:PermSize=200m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=256m
Any suggestion.
Thanks,
Nitin.

Answer 1

making it 512 temporarily working fine, but my concern was something must have been eating all the memory.
I did run bcc with 128 MB and deployed lots of initial data too, didn't face the issue in recent past with same versions and same build size.
ATG:10.2
Weblogic: 10.3.5
JDK:1.6.0_25
One more info:
my build size is around 200 MB
I m not running productionAgent,But I didn't make that essential while setting agent.
Can that be issue that some Manager trying to hit the server continuously and eating the memory.
Can not running the agent server, eat substantial memory?
**** Warning
Wed Nov 13 04:25:21 IST 2013
1384296921718   /atg/epub/DeploymentServer
Failed to connect to agent 'ProdcutionAgent'.  This agent not allowed to be absent for a deployment.  The server will continue attempts to intialize the connection.  Set loggingDebug to true for continued exception and stacktrace logging.
@others:
BCC Server memory parameters:
WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
MEM_PERM_SIZE_32BIT=-XX:PermSize=128m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=256m
Production Server memory parameters:
WLS_MEM_ARGS_32BIT=-Xms200m -Xmx256m
MEM_PERM_SIZE_32BIT=-XX:PermSize=64m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=128m