Diagnostics
Symptom
14:20:42.136 [main] WARN edaprint.log - No CONNECT packet received from 10.2.3.65 (10.2.3.65), Port: 18295, probable cause: IP-Probe
Problem
Attempts to stop or restart the Windows Service for the Reporting Server will not complete successfully resulting in the error messages above in the stdout.log file.
The service remains in the stopping phase for at least 10 minutes and will not stop until the edapsrv.exe process is manually stopped. Also, while the service is stopping, the edapth.exe will often exhibit higher than normal CPU usage.
Solution
An application delivery controller is used to direct incoming requests to the Reporting Server. The application delivery controller periodically checks the Reporting Server to see if port 8123 is up or down so it knows whether or not to send traffic to it. The JSCOM3 listener is listening on port 8123 which triggers numerous messages in the edatemp\jscom3_1\stdout.log file. These messages seem to be impacting the shutdown process.
Updating the configuration of the application delivery controller so that it does not access the JSCOM3 port resolved the issue.