on 09-16-2014 9:20 AM
Hi Experts.
In Agentry installations prior to SMP 3.0, one could adjust the heap size of the Agentry Server in the Agentry.ini file.
Parameters are:
[Java-1]
initialHeapSize=
maxHeapSize=
How do we adjust the corresponding parameters of Agentry instances of SMP 3.0 SP03/SP04 ?
Thanks.
Søren Hansen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Søren
Have you figured out how to make changes to the Agentry.ini?
Should it be done directly in the ini file?
How do you do it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Søren
Please let me know if you solve it. I am trying to do the same.
What I tried was to unzip the SAPIM-4.0.0.0.zip and edit the Agentry.ini file.
Then deploy it back in the cockpit, but I still get heap dumps referring to the old parameters.
Let me know if you manage to do it.
Best Regards
Kristoffer Engh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Steve.
I have now reproduced the error on my laptop.
On the console I now see below errors, when I get the OutOfMemory error.
Søren Hansen
Exception in thread "Timer-1" Exception in thread "Thread-20Exception in thread
"Thread-20Exception in thread "Thread-20" Exception in thread "Thread-21" Except
ion in thread "Timer-3,PC56758.domain.dk:com.sap.mobile.platform.server.agentry
.appsstarted,PC56758-57988" Exception in thread "[Timer] - Main Queue Handler" E
xception in thread "Thread-251" java.lang.OutOfMemoryError: GC overhead limit ex
ceeded
Exception in thread "pool-2-thread-1" Exception in thread "http-bio-8083-AsyncTi
meout" java.lang.OutOfMemoryError: Java heap space
Exception in thread "http-bio-8081-AsyncTimeout" Exception in thread "session-di
sposer-1" Exception in thread "Timer-5,PC56758.domain.dk:com.sap.mobile.platfor
m.server.agentry.appsstarted,PC56758-57988" Exception in thread "Timer runner-1,
PC56758.domain.dk:com.sap.mobile.platform.server.cluster.EvictionManager,PC5675
8-12568" java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space
Exception in thread "Timer-4,PC56758.domain.dk:com.sap.mobile.platform.server.s
upport.cluster.ClusterLogSettings,PC56758-19594" java.lang.OutOfMemoryError: GC
overhead limit exceeded
Exception in thread "RMI RenewClean-[10.26.59.56:1717]" SLF4J: Failed toString()
invocation on an object of type [java.lang.OutOfMemoryError]
Exception in thread "Timer-3,PC56758.domain.dk:com.sap.mobile.platform.server.a
gentry.userlogin,PC56758-28110" Exception in thread "Timer-3,PC56758.domain.dk:
com.sap.mobile.platform.server.agentry..updateApplicationMailbox,PC56758-5154" E
xception in thread "Timer-5,PC56758.domain.dk:com.sap.mobile.platform.server.on
line.admin.logsettings.cluster.ClusterLogSettings,PC56758-3818" Exception in thr
ead "Timer-4,PC56758.domain.dk:com.sap.mobile.platform.server.online.statistics
.util.OnlineClusterMessageReceiver,PC56758-35733" java.lang.OutOfMemoryError: GC
overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Timer runner-1,PC56758.domain.dk:com.sap.mobile.platform.s
erver.proxy.configuration.cluster.ClusterApplications,PC56758-33208" java.lang.O
utOfMemoryError: GC overhead limit exceeded
Exception in thread "Incoming-2,PC56758.domain.dk:com.sap.mobile.platform.serve
r.cluster.EvictionManager,PC56758-12568" java.lang.OutOfMemoryError: GC overhead
limit exceeded
Hi Steve.
I have performed a "controlled dump", meaning I have on purpose not set filters for the complex table ctPart. This is causing the dump.
So my question is not how to solve the current error, but I know from experience with Agentry servers before SMP, that once in a while you may need to adjust your heapsize. It is individual how much heap you will allow on your server.
So lets assume for now, that I wanted to download all Parts from the backend.
How can I adjust the heap size to allow this action to be performed on my server ?
Søren.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.