java.lang.IllegalStateException: UT000004: getResponseChannel() has already been called


#1

My ShinyProxy log is full of messages like the one below.

2018-12-12 03:38:19.264 ERROR 1 --- [   XNIO-2 I/O-3] org.xnio.nio                             : XNIO000011: Task io.undertow.server.handlers.proxy.ProxyHandler$ProxyClientHandler@3303f2ff failed with an exception

java.lang.IllegalStateException: UT000004: getResponseChannel() has already been called
	at io.undertow.server.HttpServerExchange.addResponseWrapper(HttpServerExchange.java:1463) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at io.undertow.server.HttpServerExchange.addResponseCommitListener(HttpServerExchange.java:1834) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at eu.openanalytics.containerproxy.util.ProxyMappingManager$1.getConnection(ProxyMappingManager.java:70) ~[containerproxy-0.6.0.jar!/:0.6.0]
	at io.undertow.server.handlers.proxy.ProxyHandler$ProxyClientHandler.failed(ProxyHandler.java:329) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at io.undertow.server.handlers.proxy.ProxyHandler$ProxyClientHandler.queuedRequestFailed(ProxyHandler.java:341) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at io.undertow.server.handlers.proxy.ProxyConnectionPool.connect(ProxyConnectionPool.java:531) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at io.undertow.server.handlers.proxy.LoadBalancingProxyClient.getConnection(LoadBalancingProxyClient.java:301) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at eu.openanalytics.containerproxy.util.ProxyMappingManager$1.getConnection(ProxyMappingManager.java:69) ~[containerproxy-0.6.0.jar!/:0.6.0]
	at io.undertow.server.handlers.proxy.ProxyHandler$ProxyClientHandler.run(ProxyHandler.java:310) ~[undertow-core-1.4.22.Final.jar!/:1.4.22.Final]
	at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:582) [xnio-nio-3.3.8.Final.jar!/:3.3.8.Final]
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:466) [xnio-nio-3.3.8.Final.jar!/:3.3.8.Final]

What are these about and how can I fix whatever the underlying issue is?

I’m running ShinyProxy 2.0.5 in a container using Docker Swarm as a backend and OpenID for authentication.


#2

Hi @SimonG,

These errors are caused by a timing-related issue in v2.0.5.
A fix has been prepared, and is scheduled for the next release:


#3

Hi @SimonG,

The fix has been released with ShinyProxy 2.1.0 - see https://www.shinyproxy.io/downloads/

Best,
Tobias