This was an Apache Tomcat issue.
Having the same problem with 8.5.16 version it ceased when upgrading to
8.5.50.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-
Could you solve the problem ?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/After-upgrade-to-Wicket-7-6-0-WebSocket-logs-Broken-pipe-tp4676630p4678119.html
Sent from the Users forum mailing list archive at Nabble.com.
---
On 04/01/2017 10:41, Martin Grigorov wrote:
Hi,
My question was: have you updated Tomcat lately?
Maybe you have upgraded from older and working version to latest/broken one.
Ah, I understand: you might be right, then.
It seems that the features connected to web sockets are working fine
anywa
Hi,
My question was: have you updated Tomcat lately?
Maybe you have upgraded from older and working version to latest/broken one.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Jan 4, 2017 at 10:29 AM, Francesco Chicchiriccò wrote:
> On 04/01/2017 10:14,
On 04/01/2017 10:29, Francesco Chicchiriccò wrote:
On 04/01/2017 10:14, Martin Grigorov wrote:
Hi,
Have you updated Tomcat version too?
I don't see any reason why changes in Wicket Native WebSocket could
lead to
this.
In the same time there were many improvements in Tomcat WebSocket
code, an
On 04/01/2017 10:14, Martin Grigorov wrote:
Hi,
Have you updated Tomcat version too?
I don't see any reason why changes in Wicket Native WebSocket could lead to
this.
In the same time there were many improvements in Tomcat WebSocket code, and
this might led to a regression.
Hi,
this happens bo
Hi,
Have you updated Tomcat version too?
I don't see any reason why changes in Wicket Native WebSocket could lead to
this.
In the same time there were many improvements in Tomcat WebSocket code, and
this might led to a regression.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com
