Mikael Mengistu

Hi @Ktirumalsetty. The error message `There were no compatible transports on the server.` Means that there there was no overlap between the transports on the server and the transports on...

I'd first recommend using a newer version of the package. There have been several updates with various fixes released since 1.0.0

https://search.maven.org/artifact/com.microsoft.signalr/signalr Here are all the released versions of the Asp.Net Core SignalR Java client

Okay yes, there is your problem. Core and Classic client and servers are not compatible. There is an older SignalR Java client but it's not supported and hasn't been updated...

The client at https://github.com/SignalR/java-client has been deprecated. While SignalR on asp.net is still supported, just that **specific client is no longer supported**. 🙁

Have you tried and run into issues using the SignalR Java client with your AspNetCore SignalR 2.1 app? It should work.

@gxh-apologize What version of the SignalR Java client are you using? And do you have websockets enabled on your back end site? Cloud providers usually have it off by default...

> there is not connectionStateChanged listener..how to get connection state changed event @hirenpatel868 In the current version of the Java client we only have two states. `Connected` and `Disconnected`. So...

@gxh-apologize One thing you could do is upgrade to the 3.0.0-preview3-19153-02 version. Note that it is a preview version though. But with this you can set the transport to LongPolling...

You would set LongPolling like this ```java HubConnection hubConnection = HubConnectionBuilder .create("http://example.com") .withTransport(TransportEnum.LONG_POLLING) .build(); ```