I don't know what your load and configuration is like so it might be a bit of a canned response to your case, but 1024 does seem like a fairly low setting for a production server running a 9.x system.
Forget about what the minimum recommendations are on the manuals. Remember they are only minimum recommendations to stand up a system for it to be up and running - not necessarily to perform at its best. IF this issue has anything to do with the java heap and even if you have as low as about 50 to 100 open connection per Mid Tier server, consider raising your servers physical memory to allow a configuration of a heap size of at least about 4096 if not more. If you can share some statistics on your usage, it would give a better picture of what you might require in terms of web server sizing. Cheers Joe PS: I am assuming you have seperated your AR System application tier from your DB and Web tiers... -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Su Kaur Sent: Monday, June 27, 2016 3:06 PM To: arslist@ARSLIST.ORG Subject: Re: Remedy 9.0.01 - CPU utilization and write license issues We never had this issue on any of the pre-prod systems. May because we never had full load on any of the dev or test systems. I did change the java heap from 512 to 1024 in armonitor.cfg but it didnt fix the issue. Not sure if this heap needs to be increased in java settings or not? Regards, Kaur _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
