Kbase 18403: How to Alleviate Memory Problems Running Apptivity Server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2003 |
|
Status: Unverified
GOAL:
How to alleviate memory problems running Apptivity Server.
CAUSE:
There have been some issues reported where the Apptivity Connection Manager would lockup or an out of memory message would occur.
FIX:
When invoking Connection Manager, some extra switches may need to be set to help control memory allocations.
This is what a command line looks like that starts the connection manager.
java.exe -ms20000000 -mx40000000 -verbosegc
-classpath %CLASSPATH% progress.apptivity.server.abConnectionMgr
Where
-verbosegc print a message when garbage collection occurs
-ms<number> set the initial Java heap size
-mx<number> set the maximum Java heap size
These are all java startup parameters. The Java VM doesn't appear to work well with NT's Virtual Memory paging. Also, the -verbosegc switch can be helpful for diagnosing memory problems