-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate official release of cloudfoundry-client #252
Comments
- upgrade version to 2.0.0.RELEASE - rename application log sourceName to sourceType - rename application log sourceId to sourceInstance fix #252
Note related initiated branch by @antechrestos at https://github.com/cloudfoundry-community/autosleep/compare/feature/upgrade_client_version |
If the recent logs usage needs to be preserved (w.r.t. #187 and alternative use of firehose )
|
- upgrade version to 2.0.0.RELEASE - rename application log sourceName to sourceType - rename application log sourceId to sourceInstance fix cloudfoundry-community#252
started Indeed observing log related error traces when running acceptance tests:
Will not need to reproduce with smaller test case, such as the one provided by Benjamin |
Running @antechrestos program adapated to perform retries and measure:
I obtain the following results:
See sample into |
Same with update to the latest versions
Next:
|
Successfull capture and replay in two steps: Set up wiremock in record mode
Exceptions are now more systematic, althrough still non-deterministic
Next:
|
Well done @gberche-orange |
More details on the wiremock set up. The trick was to use wiremock as a reverse proxy for individual endpoints. This has the following limitations:
Configuring cf-java-client to go through wiremock as a forward proxy would be much simpler, however:
While jetty does support forward proxifying TLS traffic (see This would require wiremock to modify the ConnectHandler to instead:
Next steps to try to help the wiremock team for this MITM feature could be:
Alternatives for using WM in cf-java-client:
|
@antechrestos if you plan to proceed with this issue (as mentionned on the cf-java-client issue), please consider reusing upgrade_client_version-2.0.2 branch which has few commits to display jars version in traces and a unit test bug fix. |
- upgrade version to 2.0.0.RELEASE - rename application log sourceName to sourceType - rename application log sourceId to sourceInstance fix #252
Impact
Beware of some errors on recent message
The text was updated successfully, but these errors were encountered: