Issues
- Cannot track status of Remote Poller Windows serviceNMS-9750Resolved issue: NMS-9750
- Remote Poller log path incorrect when using the NSIS installerNMS-9631Resolved issue: NMS-9631Seth Leger
- OpenNMS Won't Start on WindowsNMS-9368Resolved issue: NMS-9368
- Karaf errors when installation path has white spaceNMS-8684Resolved issue: NMS-8684Seth Leger
- Vaadin dashboard cannot find default view (Windows)NMS-8115
- InvalidPathException on element/node.jsp with IPv6 interface on WindowsNMS-8085Resolved issue: NMS-8085fooker
- Stop.bat return errorNMS-8061
- Windows installer doesn't use postgres password from installer dialogNMS-7831
- OpenNMS start crash when parsing event configuration on WindowsNMS-7281Resolved issue: NMS-7281
- Ping and trace route from topology and SVG maps doesn't work on WindowsNMS-7248Resolved issue: NMS-7248
- The MIB Compiler doesn't work if OpenNMS is installed on WindowsNMS-6413Resolved issue: NMS-6413Alejandro Galue
- Can't import a requisition when OpenNMS is installed in "C:\Program Files\OpenNMS"NMS-6361Resolved issue: NMS-6361
- Failed to generate some of the reportsNMS-5509
- java.lang.NoClassDefFoundError: Files/OpenNMSNMS-5358
- Report on Windows Servers disk usageNMS-4948Resolved issue: NMS-4948Donald Desloge
- Online report creation exception on Windows environmentNMS-4624
16 of 16
Cannot track status of Remote Poller Windows service
Won't Fix
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Created November 22, 2017 at 4:56 PM
Updated July 21, 2021 at 9:38 PM
Resolved July 21, 2021 at 1:48 PM
Activity
Show:
Seth LegerNovember 22, 2017 at 5:11 PM
Bug documenting the problem:
Seth LegerNovember 22, 2017 at 5:08 PMEdited
Note that normally you can use the -wait option to prevent javaws.exe from exiting but this option doesn't work on Windows. :-/
https://docs.oracle.com/javase/7/docs/technotes/tools/share/javaws.html
The Remote Poller Windows service is currently implemented as a Commons Daemon launcher that starts
javaws.exeinexemode. Unfortunately,javaws.exelaunches the actual JNLP application in a subprocess and then exits making it impossible to track the PID and making it seem like the service is alwaysStopped.To work around this, we need to figure out how to monitor the actual PID of the JNLP application (which is launched using
jp2launcher.exe).