JMC-6100 and JMC-6152 Trigger Alerts

[Ken Dobson]

Hi All,

I was having a quick look at
https://bugs.openjdk.java.net/projects/JMC/issues/JMC-6100 which seem to be
a duplicate of https://bugs.openjdk.java.net/projects/JMC/issues/JMC-6152 .
It seems as if that is actually how it is intended to work as of right now,
as dumping an hprof file shouldn't provide an alert in JMC, just dump the
file to the location you've chosen which occurs correctly. The alert that
occurs the second time you turn the trigger on is an error for trying to
create a file that already exists as you had previously created it.

I was wondering if someone could provide some insight into whether we would
like to change this in some way, such as appending a timestamp to the hprof
to ensure file names aren't duplicated in case a user wanted to dump an
hprof more than once.
As well, logging a a trigger alert to a text file currently overwrites the
previous file so that is another option. That being said it seems odd to me
to keep just the most recent trigger alert rather than appending an alert
so that there's a log of the previous alerts.

Any insight into whether this is intended and why or whether this requires
changes would be appreciated.

Thanks,

Ken Dobson