Closed bdhoine closed 4 years ago
Hello Barry,
Cheers, Antoine
Hi,
I tried all options u described already. The user was defined and was a valid git user with read-write permissions. The BitBucket version was 4.4, which should be compatible and if a performed the call using curl the operation succeeded.
Seems there is a bug in the AsyncHttpClient.
Maybe it has something to do with the fact that the server used a SHA1 certificate which expired on 1 january 2017, I tried with a similar certificate that expires one day before and that one does get accepted.
If I use the async-http-client artifact from org.asynchttpclient, then it works! Is it possible for me to create a pull request or will you guys update the implementation?
@acopet can you or somebody else please provide some feedback on my previous comment? the error was clearly not a configuration error and with another library it did work without tweaking the code (except a few lines for API compatibility)
Hello Barry,
Sorry for the delay, please go ahead with your contribution through a Pull Request.
Cheers, Mathieu
@mathieusimon is it possible to merge @bdhoine branch ? We have faced the same issue:
[ERROR] Unable to get SonarQube reviewer from Stash: java.util.concurrent.ExecutionException: java.net.ConnectException: https://domain.name:443
I'm facing the same issue here... It would be awesome to get this merged in.
Any update on this? I'm having the same issue.
We could handle similar issue by incrementing client's version up to 1.9.32:
<dependency>
<groupId>com.ning</groupId>
<artifactId>async-http-client</artifactId>
<version>1.9.32</version>
</dependency>
No changes except pom.xml required.
When trying to get info from my BitBucket instance I get the following stack trace when running maven in debug mode.