Our apologies for the delay in responding to your post. When the On-premise poller is restarted or upgraded, it kills the existing java process and starts a new java process, because of which an alert might be triggered, as the process arguments are changed.
Recently, we added support for configuring 'Regex' for Arguments in our Process Monitoring, so that even if the arguments change, the new process arguments are matched with the configured Regex and alerts because of changes to arguments could be avoided. In this case, you can edit the monitored Java Process and update the Arguments field as below:
This will avoid similar alerts, which are triggered when arguments change, in the future. Please let me know if this helps.