ID 339120 - Frame Server turns off when an additional command line render is run.

Problem summary
Frame Server turns off when an additional command line render is run.

Customer reported version
nuke.11.0v3

Customer reported platform
windows7

Steps to reproduce
1) Open Nuke. 
2) Open attached script.
3) Render "Write1" for frames 1000-1300. Make sure "Render using frame server" is ticked on.
4) Open a command prompt or powershell window.
5) Enter the following command with paths adjusted for your environment to run a command line render:
/path/to/nuke/executable -x -F 1000-1300 -X Write2 /path/to/attached/script.nk
6) Run the command from step 5 while the render from step 3 is running. 
Result: The frame server will eventually turn "off," despite the fact that it is still rendering.

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke 11.1v1 - Windows 10
Nuke 11.0v4 - Windows 10
Nuke 11.0v3 - Windows 10
Nuke 11.0v1 - Windows 10

Unable to reproduce bug in:
Nuke 11.1v1 - OSX 10.10.5, Centos 7.3
Nuke 11.0v4 - OSX 10.10.5, Centos 7.3
Nuke 11.0v3 - OSX 10.10.5, Centos 7.3
Nuke 11.0v1 - OSX 10.10.5, Centos 7.3

Earliest version tested
Nuke 11.0v1 - This feature did not exist in Nuke before this version.

Expected behaviour
Frame server should remain "on" and continue rendering if a command line render is started externally.

Actual behaviour
Frame server turns "off," though it is still rendering if a command line render is started externally.