NATSTimeoutException when we supply a non existing or wrong cluster id about stan.net HOT 5 CLOSED

Hi all, I created a PR for this, #111 , does this look like it'll help? After further thought, I didn't want to change the exception because that would be a breaking change in the API.

from stan.net.

I have encountered this one as well and it can be somewhat difficult to track down if you are not aware of the importance of cluster id. However a NATSTimeoutException, IMO, is the correct exception. An error message saying that this could be because of the IP/Hostname, Port OR cluster id might help narrowing this down earlier.

from stan.net.

This issue seems to be a common one. Would something like a ClusterUnavailableException with the cluster name in the message sound reasonable?

from stan.net.

thanks for your answers guys
yes it make more sense to have an exception that contain a cluster as we need to separate exception between nats streaming connection (IStanConnection) and nats connection (IConnection) because nats connection doesn't really care about the cluster ID
Thanks

from stan.net.

yes it will diffenetly help and better than the previous exception
thanks Colin for this enhancement

from stan.net.