Expected Behavior

Stopping the service should initiate shutdown through Jetty and cleanly terminate all instances.

Current Behavior

Jetty shutdown handlers seem to work for the most part, and logs show all 6 components being shut down. During the shutdown of the backend, errors arise because some threads are still trying to access it. The Java process never terminates (it continues to even eat up processor cycles). The service hangs indefinitely in a state of "Stopping."

Possible Solution

Steps to Reproduce (for bugs)

1. Use services.msc, command line, or procrun GUI to stop the service.

Context

Even if ignorable errors are thrown, I need the service to be fully automated. I'm only temporarily allowed remote access to the server to configure the application. Once it's running, it needs to be mostly hands-off for our IT admins (i.e., no special accommodations during maintenance reboots).

As a side note, I found a possible typo in the stop_server method in launcher.rb while I was troubleshooting this issue. There's an "f" at the end of line 197 that I don't think is supposed to be there.

Your Environment

• Version used: AS v2.8.0
• Environment name and version: IIS 10 (proxy for frontend), java version "1.8.0_191", procrun 1.2.3.0
• Operating System and version (desktop or mobile): Windows Server 2016