The workarounds are as follows:
Restart the clusters or server instances on which the stand-alone web module is deployed.
None.
