You are absolutely correct. Running with 1.1.0.Beta7-SNAPSHOT times
out
the connect attempt at 10s, as advertised.
Any idea when this is planned to be tagged for release?
Thanks.
On Mon, Aug 25, 2014 at 12:25 AM, Stuart Douglas <sdouglas(a)redhat.com
<mailto:sdouglas@redhat.com>> wrote:
This should be fixed in the 1.1 branch of Undertow. Can you try
using Undertow upstream?
Stuart
Ryan Hermanson wrote:
Is there way to cancel an outstanding
WebSocketContainer.__connectToServer(...) request ? A connection
attempt
to an offline server blocks a very long time (minutes), and
debugging
would indicate IoFuture<WebSocketChannel> seems unwilling to
respect an
interrupt/cancel from the main thread.
IoFuture<WebSocketChannel> session =
WebSocketClient.connect(__xnioWorker,
ssl, bufferPool, OptionMap.EMPTY, path, WebSocketVersion.V13,
clientNegotiation); //TODO: fix this
WebSocketChannel channel = session.get();
_________________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org <mailto:undertow-dev@lists.jboss.org>
https://lists.jboss.org/__mailman/listinfo/undertow-dev
<
https://lists.jboss.org/mailman/listinfo/undertow-dev>