AutoSys Workload Automation

Hi everyone,

I need configure the MinPermGen / MaxPermGen because it cause errors in the server.

Please, how can i change the windows service properties file these parameters?

Thanks

Susana Duymovich

Hi,

Are you referring to Java Heap for the DE?

If so, what are the errors you are seeing?  

Please contact support as there may be some other issues present as well.

For Windows, change the parameter in  'windows.service.properties', by default, it is 1GB.

jvmproperty_3=-Xmx1024M

You can change it accordingly.

Thank you,

Nitin Pande

CA Technologies

Thanks for the answer, exactly I had already configured the java memory -Xms1024m -Xmx5120m but I do not have the configuration option of the PermGen. According to the error of the logs file the problem is with the configuration of the PermGen space. 

20170831 08:05:37.256 [dm:controlobject] [INFO] DM.AgentHeartBeat: Pinging agent INFP10S2
20170831 08:05:39.503 [essential] [ERROR] RMI TCP Connection(idle): Uncaught Exception in Thread[RMI TCP Connection(idle),5,RMI Runtime]

java.lang.OutOfMemoryError: PermGen space
20170831 08:05:39.503 [essential] [INFO] Thread-14627: New StatusMessage: [date: Thu Aug 31 08:05:39 COT 2017, type: Log message, loggerName: essential, level: ERROR, threadName: RMI TCP Connection(idle), message: Uncaught Exception in Thread[RMI TCP Connection(idle),5,RMI Runtime], stackTrace: [java.lang.OutOfMemoryError: PermGen space]]

20170831 08:05:39.503 [essential] [ERROR] RMI TCP Connection(idle): Uncaught Exception in Thread[RMI TCP Connection(idle),5,RMI Runtime]

java.lang.OutOfMemoryError: PermGen space
20170831 08:05:39.503 [essential] [INFO] Thread-14628: New StatusMessage: [date: Thu Aug 31 08:05:39 COT 2017, type: Log message, loggerName: essential, level: ERROR, threadName: RMI TCP Connection(idle), message: Uncaught Exception in Thread[RMI TCP Connection(idle),5,RMI Runtime], stackTrace: [java.lang.OutOfMemoryError: PermGen space]]

20170831 08:05:39.752 [dm:controlobject] [INFO] DM.AgentHeartBeat: Pinging agent W77SSUNAT
20170831 08:05:43.200 [ws:connections] [INFO] WSS_reactor_12: Connection closed (10.0.50.60:57984->150.50.2.89:7500)
java.io.EOFException
        at cybermation.workstationserver.nio.ReadExpert.read(ReadExpert.java:164)
        at cybermation.workstationserver.nio.ReadWriteHandler.handleRead(ReadWriteHandler.java:159)
        at cybermation.workstationserver.nio.Reactor.dispatchEvents(Reactor.java:184)
        at cybermation.workstationserver.nio.Reactor.access$000(Reactor.java:39)
        at cybermation.workstationserver.nio.Reactor$3.run(Reactor.java:403)
        at java.lang.Thread.run(Thread.java:745)

Thanks for your help

Susana Duymovich

Hi Susana,

What version of CA WA (dSeries) are you at? I see r11.3 SP3 and onwards uses Java 1.8, and PermGen has been removed (and replaced with Metaspace) since Java 8.

If you are on pre-11.3SP3 release, then please consider upgrading at the earliest.

For the time being, you may try the following in the windows.service.properties file (please back up the file before modification)

jvmproperty_11=-XX:MaxPermSize=512m

This instructs the JVM to not exceed 512MB for the PermGen space (default max is 64MB (32bit Java) and 83MB (64bit Java - 30% more as per Oracle).

You may also benefit from the following additional settings:

jvmproperty_12=-XX:+UseConcMarkSweepGC
jvmproperty_13=-XX:+CMSClassUnloadingEnabled

If you enable CMSClassUnloadingEnabled, GC will sweep PermGen too and remove classes which are no longer used. However, this option will work only when UseConcMarkSweepGC is enabled.

Please test these thoroughly on a development environment before implementing on production.

Thanks,

Chandru

Hi chandru,

Thanks for your answer, the cawa version is 11.3. SP3 and the java version is 1.7

I changed the windows.service.properties file:

# JVM properties
javapath=D:/Program Files/CA/WorkloadAutomation_R11.3_SP3/jre/bin
jvm=server
jvmproperty_1=-Dlax.root.install.dir=D:/Program Files/CA/WorkloadAutomation_R11.3_SP3
jvmproperty_2=-Xms4M
jvmproperty_3=-Xmx1024M
jvmproperty_4=-Duser.language=en
jvmproperty_5=-Dlog4j.configuration=file:///D:/Program Files/CA/WorkloadAutomation_R11.3_SP3/conf/server.log4j.xml
jvmproperty_6=-Dlog.directory=D:/Program Files/CA/WorkloadAutomation_R11.3_SP3/logs
jvmproperty_7=-Dlog4j.configuratorClass=com.cybermation.espresso.log.LogConfigurator
jvmproperty_8=-Djava.library.path=D:/Program Files/CA/WorkloadAutomation_R11.3_SP3/lib
jvmproperty_9=-Djdk.lang.Process.allowAmbigousCommands=true
jvmproperty_10=-XX:MaxPermSize=512m
jvmproperty_11=-XX:+ UseConcMarkSweepGC
jvmproperty_12=-XX:+ CMSClassUnloadingEnabled
#The jvmproperty_9 is provided to bypass the sctricter implementation of the methods of the class "java.lang.Runtime" from the released JDK 7u21. Need to remove this once the replacement of the existing code done using the class java.lang.ProcessBuilder to launch a separate jvm instance for the report execution.

Regards

Susana Duymovich