-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Meridian-2016.1.3, 21.0.0, Meridian-2017.1.1
-
Fix Version/s: 21.0.2, Meridian-2016.1.10, Meridian-2017.1.3
-
Component/s: Remote Polling
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Sprint:Horizon - November 15th, Horizon - November 22nd, Horizon - November 30th
When using the JNLP version of the remote poller on Windows, it works as expected.
The problem is that you have to manually start it after Windows starts which is a pain, if the operator forgets to do it.
The EXE installer was designed to create a Windows Service that wraps the initialization of the JNLP version of the remote poller.
The installation wizards works, and you can start and register the poller, but when it tries to start the poller through the Windows Service, it appears to be running, but it is not communicating with OpenNMS (it appears as disconnected).
Also, stopping the service is not possible, it times out and the only way to stop it is by physically kill the Java process.
