Skip to content

Commit 62d0b04

Browse files
authored
[Fix-17915][alert] Fix the issue of setting timeout exceptions in the HTTP alert plugin, where the unit in the code is not consistent with the page. (#17920)
1 parent 4b0427d commit 62d0b04

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http

dolphinscheduler-alert/dolphinscheduler-alert-plugins/dolphinscheduler-alert-http/src/main/java/org/apache/dolphinscheduler/plugin/alert/http/HttpSender.java

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,9 +91,9 @@ private void paramsValidator(Map<String, String> paramsMap) {
9191
throw new IllegalArgumentException("contentType is not a valid value");
9292
}
9393

94-
timeout = StringUtils.isNotBlank(paramsMap.get(HttpAlertConstants.NAME_TIMEOUT))
94+
timeout = (StringUtils.isNotBlank(paramsMap.get(HttpAlertConstants.NAME_TIMEOUT))
9595
? Integer.parseInt(paramsMap.get(HttpAlertConstants.NAME_TIMEOUT))
96-
: HttpAlertConstants.DEFAULT_TIMEOUT * 1000;
96+
: HttpAlertConstants.DEFAULT_TIMEOUT) * 1000;
9797
}
9898

9999
public AlertResult send(String msg) {

0 commit comments

Comments
 (0)