Log should include which parameter led to a timeout

[haerter-tss]

SecHub has multiple parameters in which timeouts can be defined. That leads to the issue that an admin cannot be sure which parameter was the reason a scanjob was canceled.

Solution:

If a timeout is reached and a job is canceled because of it the exact parameter should be mentioned in the log.

[de-jcup]

I think we need here more explicit definitions what exactly is wanted.

I will start here a list of parameters which are repsonsible for potential timeouts:

• [ ] PDSDefaultParameterKeyConstants
  • PARAM_KEY_PDS_CONFIG_PRODUCT_TIMEOUT_MAX_CONFIGURABLE_MINUTES
  • PARAM_KEY_PDS_CONFIG_PRODUCT_TIMEOUT_MINUTES
  • PARAM_KEY_PDS_CONFIG_CANCEL_MAXIMUM_WAITTIME_SECONDS
• [ ] PDSAdapter config timeout settings
  • more