You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/08/24 14:48:58 UTC

[GitHub] [shardingsphere-elasticjob] TeslaCN opened a new issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

TeslaCN opened a new issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405


   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere-elastic-job-lite/issues).
   - Read documentation: [ElasticJob Doc](http://shardingsphere.apache.org/elasticjob/docs/elastic-job-lite/00-overview/).
   
   Please pay attention on issues you submitted, because we maybe need more details. 
   If no response anymore and we cannot reproduce it on current information, we will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ElasticJob did you use?
   
   ### Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?
   
   ### Expected behavior
   
   ### Actual behavior
   ```
   -------------------------------------------------------------------------------
   Test set: org.apache.shardingsphere.elasticjob.http.executor.HttpJobExecutorTest
   -------------------------------------------------------------------------------
   Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.723 sec <<< FAILURE! - in org.apache.shardingsphere.elasticjob.http.executor.HttpJobExecutorTest
   assertProcessWithGet(org.apache.shardingsphere.elasticjob.http.executor.HttpJobExecutorTest)  Time elapsed: 7.853 sec  <<< ERROR!
   org.apache.shardingsphere.elasticjob.infra.exception.JobExecutionException: java.net.SocketTimeoutException: Read timed out
   	at org.apache.shardingsphere.elasticjob.http.executor.HttpJobExecutorTest.assertProcessWithGet(HttpJobExecutorTest.java:95)
   Caused by: java.net.SocketTimeoutException: Read timed out
   	at org.apache.shardingsphere.elasticjob.http.executor.HttpJobExecutorTest.assertProcessWithGet(HttpJobExecutorTest.java:95)
   ```
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior.
   Just run `mvn install`.
   ### Example codes for reproduce this issue (such as a github link).
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] Technoboy- commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
Technoboy- commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-679228514


   Test url (https://github.com) may cause the read timeout. 


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] terrymanu commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-680971923


   > > > > Test url (https://github.com) may cause the read timeout.
   > > > 
   > > > 
   > > > So the test result is partly depended on build environment. Is there any better way?
   > > 
   > > 
   > > I think we can start an embed rest server(as you have done rest module) and request the internal api.
   > > We can do this after branch rest-api merged to master. Do you agree ?
   > 
   > That's a good idea.
   
   I prefer this way too


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] Technoboy- commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
Technoboy- commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-679490145


   
   
   
   
   > > Test url (https://github.com) may cause the read timeout.
   > 
   > So the test result is partly depended on build environment. Is there any better way?
   
   I think we can start an embed rest server(as you have done rest module) and request the internal api.
   We can do this after branch rest-api merged to master.  Do you agree ?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-679239932


   > Test url (https://github.com) may cause the read timeout.
   
   So the test result is partly depended on build environment. Is there any better way?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] TeslaCN commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
TeslaCN commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-679633524


   > > > Test url (https://github.com) may cause the read timeout.
   > > 
   > > 
   > > So the test result is partly depended on build environment. Is there any better way?
   > 
   > I think we can start an embed rest server(as you have done rest module) and request the internal api.
   > We can do this after branch rest-api merged to master. Do you agree ?
   
   That's a good idea.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] terrymanu removed a comment on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
terrymanu removed a comment on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-680971350


   How about start a embed web server (tomcat) for test URL?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] terrymanu commented on issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
terrymanu commented on issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405#issuecomment-680971350


   How about start a embed web server (tomcat) for test URL?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [shardingsphere-elasticjob] Technoboy- closed issue #1405: There is a very low probability to reproduce SocketTimeoutException when executing testcase of HttpJobExecutor

Posted by GitBox <gi...@apache.org>.
Technoboy- closed issue #1405:
URL: https://github.com/apache/shardingsphere-elasticjob/issues/1405


   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org