Get Attack Path feature in GUI times out

[kenmeacham]

After clicking "Get Attack Path" in the GUI, in the Consequence Explorer, it responds after about 1 min with a Gateway Timeout (using system modeller deployment) or a "Something went wrong" error (running bootTest). The results say "No threats found".

[kenmeacham]

The logs are misleading, as it appears that nothing is happening after the timeout. However, when increasing the logging level to DEBUG on modelvalidator.attackpath, and re-running, it seems that the Attack Path algorithm keeps going forever in the background, which the user is not aware of.

The testcase I tried (see below) was still running after >20 mins.

Whilst the recommendations feature has a default timeout of 900s (15 mins), there is no such timeout on the attack path, which should notmally finish quite quickly.

Currently the only way to abort the Attack Path process is to kill the SSM service..

Domain & system models below. Tested using the "AbsenceOfTreatment on Patient" consequence.

domain-network-patientharms-b132-e5cfa54-filtered.zip

OSR-USB_SJT-connected_2_LowRisk_Modified-2 - b132-e5cfa54.nq.gz

CC @mike1813, @sjt1970, @panositi