aisling-2

Hi @mahbodsn, we're closing the PR as so far it doesn't seem to be an issue with this project directly and there's has not been new complains.

Hi @jcayzac , have you tried the suggestion from fibo above? We currently don't have an estimation to work on this, so just checking if it would be a workaround...

@harper1999 请问后来解决问题了吗？如果还需要答案的话，请提供更多信息。 “Steps to reproduce” 这一步很重要，不提供我们这边很难理解全体情况。

@Mr-Yuanhe @ZeroDY @JDYG Can you try the method suggested by @Kiuyam above please? Unfortunately we don't know when we'll be able to tackle this part of the code.

Hi @naserkaka, according to [WebSocketConnection ](https://github.com/binance/binance-connector-java/blob/master/src/main/java/com/binance/connector/client/utils/WebSocketConnection.java#L71), there's logging for when connection is opened or gets failure. We'll look into @Hazard4U PR #51 to see how we'll improve this, might take...

Hi @tring-malikans @tomw777, can you try the solution proposed by @nolimitech? In case you have further comments, please feel free to reopen this post.

Hey @guitarcrazy86, please look into https://dev.binance.vision/t/dotnet-connector-socket-samples-return-one-result/12668, seems to be the same situation with an answer there.

Hi, the swagger doesn't contain response headers. What's truly important is the response body. The response headers have little variation across responses, they're only different when dealing with an order...

Thank you @Hazard4U! We were finally able to get into this and now planning to publish it to `v3.0.0rc2`. Since this PR is already from a while ago and to...

We've now released a new version [2.0.0rc2 ](https://github.com/binance/binance-connector-java/releases/tag/2.0.0rc2) without `logback-classic` dependency, please have a try and if you encounter any problem, feel free to open a new Issue.