After some investigation this seems to be happening when HeapUsage at the affected node is almost 100%...
Memory statistics by org.apache.wicket.protocol.http.requests.RequestLogger few moments before the mentioned redirect looping: I'm confused by the following: 1) Why wicket things that URL is changing when it's not!(response handler is RequestSettingRequestHandler)... 2) What triggers these requests...It has to be Wicket, because RequestSettingRequestHandler is response. Thanks for any kind of hint or help. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
