Description
The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings.
This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl] ).
I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded.
Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the -Xdum_p and _-Xlp settings for AIX, where I personally would like to configure it to -Xdump:heap:events=gpf,opts=PHD, which is currently not possible using the configuration only. Also especially for AIX, there is LDR_CNTRL=MAXDATA=0xB0000000@DSA, which might not be desired when running with heaps larger than 3GB.
If you agree on a separation, I would make a proposal as PR. Please let me know.
Attachments
Issue Links
- duplicates
-
KARAF-6377 GCLog corrupted when executing stop
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- links to