November 2020 - undertow-dev - Jboss List Archives

Undertow proxy handler + RequestLimit handler issue

by paroczizs

Hi Undertow Dev, we built a custom integration component based on Wildfly 11 with Undertow 1.4.18. The application contains a couple of custom and built in handlers. We found the following: There is a RequestLimit handler right at the beginning and finally the proxy handler. When the backend getting to be slow and the load is relatively high the RequestLimit handler does its job queues the request then throws the request above the queue. When the proxy times out it starts to consume the queue, in some cases the exception below occurs and we found that in this case the counter in the RequestLimit handler is not reduced and the it can stuck the way to the backend. Are there any possibility to handle the exception in a custom handler? Thank you in advance, Zsolt 2018-11-28 12:02:19,518 ERROR [io.undertow.proxy] (default I/O-2) UT005028: Proxy request to /lwi/optinus/getentityanswersservice failed: java.nio.channels.ClosedChannelException at io.undertow.client.http.HttpClientConnection$5.handleEvent(HttpClientConnection.java:194) at io.undertow.client.http.HttpClientConnection$5.handleEvent(HttpClientConnection.java:173) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.StreamConnection.invokeCloseListener(StreamConnection.java:80) at org.xnio.Connection.close(Connection.java:142) at org.xnio.IoUtils.safeClose(IoUtils.java:152) at io.undertow.util.ConnectionUtils$3.run(ConnectionUtils.java:102) at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)

6 months, 2 weeks

2
1
0 / 0

Creating a websocket proxy with undertow

by Marc Boorshtein

Using the 1.4 series, I'm trying to handle upgrade and websockets. Looking at a few examples and the code I think what I need to do is: 1. add the WebSocketServlet to the right path 2. implement WebSocketConnectionCallback that will call my remote ws:// server Am I on the right track? I haven't found an example of doing this with undertow but found something similar with jetty ( https://github.com/chipster/chipster-web-server/blob/master/src/main/java...) but I havne't found the same thing for undertow so any pointers would be appreciated. Thanks Marc Boorshtein

7 months, 2 weeks

3
4
0 / 0

Issue with Undertow Client and SSL

by Thomas Segismont

Hi, Openshift Origin uses Hawkular Metrics to store node and container data. In this scenario, Hawkular Metrics calls the Kubernetes master server over HTTPS to validate the client identity. This is implemented with Undertow Client, as part of a ServletExtension (inside Wildfly 10) [1]. Works fine in development and testing. Now the Openshit team sees errors in the logs [2][3]. I couldn't reproduce yet. Errors come in pair, first the "UT005001: An exception occurred processing the request: java.lang.IllegalStateException: XNIO000017: Buffer was already freed", and just after "XNIO001007: A channel event listener threw an exception: java.lang.NullPointerException". Does that ring a bell? I haven't been able to find a starting point by looking into the source the code. Thanks -- Thomas Segismont JBoss ON Engineering Team [1] https://git.io/vrNyP [2] https://issues.jboss.org/browse/HWKMETRICS-408 [3] https://issues.jboss.org/secure/attachment/12405779/hawkular.log

8 months, 2 weeks

4
5
0 / 0

Correctly shutting down a websocket handler

by Robin Anil

When a client disconnects, I see that onClose is not being fired. The only way this seems to be firing if client sents a close frame. Is there any way to detect disconnection and immediately close all the opened resources. Robin Robin Anil | Software Engineer

3 years, 1 month

5
5
0 / 0

[undertow-dev] undertow.io download page still lists 2.1 as latest version

by Brad Wood

This page needs updated: https://undertow.io/downloads.html *2.1* > The current stable Servlet 4.0 branch, requires JDK8 or above There has also been 7 final releases since the undertow blog was updated: https://mvnrepository.com/artifact/io.undertow/undertow-core https://undertow.io/blog/index.html Are there release notes of these versions anywhere? Thanks! ~Brad *Developer Advocate* *Ortus Solutions, Corp * E-mail: brad(a)coldbox.org ColdBox Platform: http://www.coldbox.org Blog: http://www.codersrevolution.com

5 years, 11 months

1
2
0 / 0

[undertow-dev] re. Idle timeout handling for websockets

by Sambasiva Rao Gaddipati

Hi all, We have been having issues with how undertow handles idleTimeout for websocket connections. We use undertow (2.1.1.Final) with wildfly (v 19.0) In our service, undertow serves websocket connections for many devices in the field. We want these connections to be always on. In the wildfly configuration we set the default-session-timeout to -1. This overwrites the expireTime of all sessions to -1 (which means never close the connection because it is idle). When wildfly instantiates undertow's session manger it does not enable expireOldestUnusedSessionOnMax. So the eviction policies in the session manager don't apply. Over time (as devices are connecting and disconnecting) we see that the InMemorySessionManager() builds up sessions. As a work around, we schedule a call to session.invalidate(null) after some delay when the onClose() websocket handler is called. But it seems intrusive to call the internal api of the server from the business logic. Is this a correct way of handling this. ? One other solution that we considered, was to call setMaxInactiveInterval(10) and let the session manger clean up the session on expiry. But it turns out setMaxInactiveInterval() does not update the expireTime of the session. Please let me know your thoughts. Thanks

5 years, 12 months

1
0
0 / 0

[undertow-dev] Idle timeout handling for websocket

by Samba samba01

Hi all, We have been having issues with how undertow handles idleTimeout for websocket connections. We use undertow (2.1.1.Final) with wildfly (v 19.0) In our service, undertow serves websocket connections for many devices in the field. We want these connections to be always on. In the wildfly configuration we set the default-session-timeout to -1. This overwrites the expireTime of all sessions to -1 (which means never close the connection because it is idle). When wildfly instantiates undertow's session manger it does not enable expireOldestUnusedSessionOnMax. So the eviction policies in the session manager don't apply. Over time (as devices are connecting and disconnecting) we see that the InMemorySessionManager() builds up sessions. As a work around, we schedule a call to session.invalidate(null) after some delay when the onClose() websocket handler is called. But it seems intrusive to call internals of the server from the business logic. Is this a correct way of handling this. ? One other solution that we considered, was to call setMaxInactiveInterval(10) and let the session manger clean up the session on expiry. But it turns out setMaxInactiveInterval() does not update the expireTime of the session. Please let me know your thoughts. Thanks

5 years, 12 months

1
0
0 / 0

[undertow-dev] Idle timeout handling for websocket

by Samba samba01

Hello all, We have been having issues with how undertow handles idleTimeout for websocket connections. We use undertow (2.1.1.Final) with wildfly (v 19.0) In our service, undertow serves websocket connections for many devices in the field. We want these connections to be persistent. In the wildfly configuration we set the default-session-timeout to -1. This overwrites the expireTime of all sessions to -1 (which means never close the connection because it is idle). When wildfly instantiates undertow's session manger it does not enable expireOldestUnusedSessionOnMax. So the evictions policies in the session manager don't apply. Over time (as devices are connecting and disconnecting) we see that the InMemorySessionManager() builds up sessions. As a work around, we schedule a call to session.invalidate(null) after some delay when the onClose() websocket handler is called. But it seems intrusive to call internals of the server from the business logic. Is this a correct way of handling this. ? One other solution that we considered, was to call setMaxInactiveInterval(10) and let the session manger clean up the session on expiry. But it turns out setMaxInactiveInterval() does not update the expireTime of the session.

5 years, 12 months

1
0
0 / 0

[undertow-dev] Idle timeout handling for websocket

by Samba samba01

Hello all, We have been having issues with how undertow handles idleTimeout for websocket connections. We use undertow (2.1.1.Final) with wildfly (v 19.0) In our service, undertow serves websocket connections for many devices in the field. We want these connections to be persistent. In the wildfly configuration we set the default-session-timeout to -1. This overwrites the expireTime of all sessions to -1 (which means never close the connection because it is idle). When wildfly instantiates undertow's session manger it does not enable expireOldestUnusedSessionOnMax. So the evictions policies in the session manager don't apply. Over time (as devices are connecting and disconnecting) we see that the InMemorySessionManager() builds up sessions. As a work around, we schedule a call to session.invalidate(null) after some delay when the onClose() websocket handler is called. But it seems intrusive to call internals of the server from the business logic. Is this a correct way of handling this. ? One other solution that we considered, was to call setMaxInactiveInterval(10) and let the session manger clean up the session on expiry. But it turns out setMaxInactiveInterval() does not update the expireTime of the session.

5 years, 12 months

1
0
0 / 0

[undertow-dev] Non Blocking IO from Bocking Handler?

by Adam McMahon

Hi, We are using a blocking handler to formulate the response (a simple String). And then we call exchange.getResponseSender().send(s). Since this call is from the blocking handler, does this use blocking IO? Or does it wire up with the non-blocking IO for this call? If it does use blocking IO, is there anyway to dispatch back to the Non-blocking thread to perform the call using non-blocking io? Thanks, -Adam

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

undertow-dev November 2020