Bug 1106492

Summary:	WebSockets implementation should provide a way to increase TIMEOUT value also for APR connector
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Radim Hatlapatka <rhatlapa>
Component:	Web	Assignee:	Rémy Maucherat <rmaucher>
Status:	CLOSED EOL	QA Contact:	Michael Cada <mcada>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bsutter, jdoyle, mumeno, myarboro, pslavice
Target Milestone:	---
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1104139	Environment:
Last Closed:	2019-08-19 12:49:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1104139, 1104206
Bug Blocks:

Description Radim Hatlapatka 2014-06-09 13:18:03 UTC

Creating clone of the BZ to not loose tracking that this should also be fixed for APR connector.

+++ This bug was initially created as a clone of Bug #1104139 +++

Description of problem:
My understanding is that there is no ways to change the default timeout of 20 seconds in the current implementation. This is extremely short.

Apache Tomcat WebSocket specification provides a way to do this by setting the property org.apache.tomcat.websocket.BLOCKING_SEND_TIMEOUT in the user properties collection attached to the WebSocket session. It also allows for other configurations, such as binary buffer size and text buffer size.

More information about configuration options is located in the following locations:
http://tomcat.apache.org/tomcat-7.0-doc/web-socket-howto.html
http://tomcat.apache.org/tomcat-8.0-doc/web-socket-howto.html


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Rémy Maucherat on 2014-06-03 08:18:14 EDT ---

Tomcat uses an infinite timeout for upgraded connections, so trying that for NIO2 (APR is more complex for timeout and I cannot immediately do it).
r2441

Comment 1 Rémy Maucherat 2014-06-11 08:41:56 UTC

After reviewing, trying r2454 to duplicate the new NIO2 behavior.

Comment 2 Martin Velas 2014-08-04 13:23:58 UTC

Issue is still valid for EAP 6.3.0.ER10.

Comment 3 Rémy Maucherat 2014-09-04 13:45:43 UTC

Same as BZ1104139, this should not be related to the connector, the FutureToSendHandler timeout occurs in the websocket implementation.