Fix infinite socket timeout when using ApacheHCHttpCommandExecutorServiceModule (#51)

Because the Java type BasicHttpParams wasn't matching the one returned
by provider "newBasicHttpParams" (which is returning a HttpParams type), it was configuring the Apache HTTP client with default settings (including connection and socket timeout), ignoring the ones of JClouds which were must safer in this regard (JCloudsones are currently 60sec for both, while Apache HC ones are -1, so infinite). It also prevented to override those default/infinite timeout settings with JClouds ones.
1 file changed
tree: 5863b17c52d9ac517df7512f33ff4306ace400e3
  1. all/
  2. allblobstore/
  3. allcompute/
  4. allloadbalancer/
  5. apis/
  6. blobstore/
  7. common/
  8. compute/
  9. core/
  10. drivers/
  11. gson/
  12. loadbalancer/
  13. project/
  14. providers/
  15. resources/
  16. scriptbuilder/
  17. skeletons/
  18. .dir-locals.el
  19. .gitattributes
  20. .gitignore
  21. .mailmap
  22. .travis.yml
  23. CONTRIBUTING.md
  24. pom.xml
  25. README.md
README.md

jclouds

Apache jclouds is an open source multi-cloud toolkit for the Java platform that gives you the freedom to create applications that are portable across clouds while giving you full control to use cloud-specific features.

For more information about using or contributing to jclouds, please visit our website at jclouds.apache.org.

License

Copyright (C) 2009-2019 The Apache Software Foundation

Licensed under the Apache License, Version 2.0