Bug 1219071

Summary: [GSS] (6.4.z) Datasources are created with a idle-timeout-minutes set to 0
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Stephen Fikes <sfikes>
Component: Web ConsoleAssignee: Dominik Pospisil <dpospisi>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Jelinek <pjelinek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: brian.stansberry, cdewolf, dpospisi, hbraun, hpehl, jawilson, jkudrnac, pjelinek, rhatlapa
Target Milestone: CR1   
Target Release: EAP 6.4.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Non-default timeout configuration added to all datasources created in the web console. The idle-timeout-minutes property is set to 0 which disables timeout of idle connections. Consequence: Connections from new datasource pools, unless action is taken to remove the timeout configuration (from the .xml) or specify an explicit timeout period, will not be timed out by JBoss. Fix: Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 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:    
Bug Blocks: 1219165, 1222380    

Description Stephen Fikes 2015-05-06 14:16:08 UTC 
Description of problem:
Starting in 6.3.0 and later, new datasources created from the web console are created with an explicit idle-timeout-minutes set to 0 which means no-timeout. This overrides the default 30 minute timeout and disables timeout completely.


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


How reproducible:
Consistently

Steps to Reproduce:
* Create a new datasource

Actual results:
New datasource is created with explicitly disabled timeout period (i.e. idle-timeout-minutes = 0)

Expected results:
Timeout configuration should only be present if added by the user.

Additional info:
This leads to failures in cases where, since connections no longer timeout, they are timed out from the database server and consequently application errors occur. Users do not expect the documented defaults to be ignored.

There may be other non-default properties that should also be removed - it seems like multiple timeout-related properties were added along with disabling idle-timeout-minutes.
Comment 11 Pavel Jelinek 2015-06-19 10:28:29 UTC 
Verified for EAP 6.4.2.CP.CR1.
Comment 12 Petr Penicka 2017-01-17 10:17:02 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 13 Petr Penicka 2017-01-17 10:17:03 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.