[jboss-jira] [JBoss JIRA] (WFLY-10265) UT005028 ClosedChannelException in load balancer

[Robert Van Loenhout (JIRA)]

Robert Van Loenhout created WFLY-10265:
------------------------------------------

             Summary: UT005028 ClosedChannelException in load balancer
                 Key: WFLY-10265
                 URL: https://issues.jboss.org/browse/WFLY-10265
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
    Affects Versions: 11.0.0.Final
         Environment: Windows 10 or Windows Server 2016
            Reporter: Robert Van Loenhout
            Assignee: Paul Ferraro


I have installed Keycloak 3.4.3. I use a configuration with a load balancer with 2 (local) server instances.
On a Linux machine (CentOS 7) I do not see any errors in the load balancer log. However on Windows (10 and 2016) I see the following errors in the load balancer log:

{code}
2018-04-18 17:35:48,367 ERROR [io.undertow.proxy] (default I/O-4) UT005028: Proxy request to /auth/resources/3.4.3.final/admin/keycloak/templates/kc-paging.html failed: java.nio.channels.ClosedChannelException
	at io.undertow.client.ajp.AjpClientConnection$3.handleEvent(AjpClientConnection.java:122)
	at io.undertow.client.ajp.AjpClientConnection$3.handleEvent(AjpClientConnection.java:109)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameCloseListener.handleEvent(AbstractFramedChannel.java:1045)
	at io.undertow.server.protocol.framed.AbstractFramedChannel$FrameCloseListener.handleEvent(AbstractFramedChannel.java:959)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.terminated(ReadReadyHandler.java:71)
	at org.xnio.nio.NioSocketConduit.readTerminated(NioSocketConduit.java:332)
	at org.xnio.nio.NioSocketStreamConnection.notifyReadClosed(NioSocketStreamConnection.java:148)
	at org.xnio.Connection.close(Connection.java:139)
	at org.xnio.IoUtils.safeClose(IoUtils.java:152)
	at io.undertow.server.protocol.framed.AbstractFramedChannel.close(AbstractFramedChannel.java:793)
	at io.undertow.client.ajp.AjpClientConnection.close(AjpClientConnection.java:304)
	at org.xnio.IoUtils.safeClose(IoUtils.java:152)
	at io.undertow.server.handlers.proxy.ProxyHandler$IoExceptionHandler.handleException(ProxyHandler.java:770)
	at org.xnio.ChannelListeners.invokeChannelExceptionHandler(ChannelListeners.java:126)
	at io.undertow.util.Transfer$TransferListener.handleEvent(Transfer.java:193)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at io.undertow.channels.DetachableStreamSourceChannel$SetterDelegatingListener.handleEvent(DetachableStreamSourceChannel.java:231)
	at io.undertow.channels.DetachableStreamSourceChannel$SetterDelegatingListener.handleEvent(DetachableStreamSourceChannel.java:218)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at io.undertow.server.protocol.framed.AbstractFramedStreamSourceChannel$1.run(AbstractFramedStreamSourceChannel.java:282)
	at io.undertow.server.protocol.framed.AbstractFramedChannel$3.run(AbstractFramedChannel.java:231)
	at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
{code}

The application does actually seem to work fine.




--
This message was sent by Atlassian JIRA
(v7.5.0#75005)