Bug 1148565 - Management HTTP server closing idle connections prematurely.
Summary: Management HTTP server closing idle connections prematurely.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR4
: EAP 6.4.0
Assignee: Darran Lofthouse
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks: 1148532
TreeView+ depends on / blocked
 
Reported: 2014-10-01 18:11 UTC by Darran Lofthouse
Modified: 2019-08-19 12:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:43:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Darran Lofthouse 2014-10-01 18:11:18 UTC
Description of problem:

By default the forked Sun HTTP server in use for management over HTTP is supposed to allow connections to remain idle for up to 5 minutes, connections are however being terminated at 30 seconds.

Web browsers also contain their own keep alive timer but closing connections at 30 seconds they never get a chance.

As the server is closing the connection any underlying SSLSession is also being invalidated meaning that on reconnecting a new SSLSession needs to be established.

For this BZ the default idle time of 5 minutes should be restored, by default there is also a maximum of 200 idle connections anyway so this is not going to result in a DoS attack by allowing the idle connections to grow unconstrained.

Comment 2 Radim Hatlapatka 2014-10-08 15:58:43 UTC
Verified in EAP 6.4.0.DR4


Note You need to log in before you can comment on or make changes to this bug.