alanredsheep edited a comment on issue #5040:
URL: 
https://github.com/apache/dolphinscheduler/issues/5040#issuecomment-949358384


   I met the same issue on 1.3.8 & 1.3.9 (I install 1.3.8 with docker-compose 
and 1.3.9 with standalone-server) when I tried to save a workflow which 
containes any datax jobs or any sql jobs. But it works well on shell job. 
   
   What is more confusing, it works perfectly on 1.3.8 at first. Then it 
suddenly throw exception a few days later when i tried to save my change. 
   It seems like I mess up by change the datax job frequently on 
workflow-instance page. But it doesn't work when i re-install dolphinscheduler 
with new docker environment. 
   
   system : aliyun cloud linux
   (ps: It works well on my vmware machine)
   
   Here is the log in dolphinscheduler-api.log.
   ```
   [INFO] 2021-10-22 15:13:23.919 
org.apache.dolphinscheduler.api.controller.ProcessDefinitionController:[139] - 
verify process definition name unique, user:admin, project name:xxxxx, process 
definition name:xxxxx
   [WARN] 2021-10-22 15:13:53.976 org.eclipse.jetty.server.HttpChannel:[596] - 
handleException /dolphinscheduler/projects/xxxxx/process/save 
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout 
expired: 30000/30000 ms
   [WARN] 2021-10-22 15:14:12.987 org.eclipse.jetty.server.HttpChannel:[596] - 
handleException /dolphinscheduler/projects/xxxxx/process/save 
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout 
expired: 30000/30000 ms
   [WARN] 2021-10-22 15:14:32.037 org.eclipse.jetty.server.HttpChannel:[596] - 
handleException /dolphinscheduler/projects/xxxxx/process/save 
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout 
expired: 30000/30000 ms
   ```
   
   pls tell me what message more do you want to know. @chengshiwen @CalvinKirs 
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to