Maybe a bit confusing. This issue is marked as "Wont Fix", and yet is now marked as fixed in 2.3.1AS? I think if it is Won't fix, it should have a "blank" fix version...
-Marshall On 1/4/2011 5:21 PM, Jerry Cwiklik (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Jerry Cwiklik updated UIMA-1789: > -------------------------------- > > Fix Version/s: 2.3.1AS > > Assigned Fix Version > >> deployAsyncService script should use -XX:+HeapDumpOnOutOfMemoryError >> -------------------------------------------------------------------- >> >> Key: UIMA-1789 >> URL: https://issues.apache.org/jira/browse/UIMA-1789 >> Project: UIMA >> Issue Type: Improvement >> Components: Async Scaleout >> Reporter: Jörn Kottmann >> Priority: Minor >> Fix For: 2.3.1AS >> >> >> In case a user application needs to much memory an OuOfMemoryError stops the >> UIMA AS service. It would >> be nice if the VM would just dump the memory for further analysis and stops >> afterwards. >> For a sun vm this can be achieved with this command line option: >> -XX:+HeapDumpOnOutOfMemoryError >> Can this be done in our script, does it also work with other VMs ?
