Bug 1219071 - [GSS] (6.4.z) Datasources are created with a idle-timeout-minutes set to 0
Summary: [GSS] (6.4.z) Datasources are created with a idle-timeout-minutes set to 0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.2
Assignee: Dominik Pospisil
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks: 1219165 1222380
TreeView+ depends on / blocked
 
Reported: 2015-05-06 14:16 UTC by Stephen Fikes
Modified: 2019-07-11 09:06 UTC (History)
9 users (show)

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:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-667 0 Major Resolved Add data-source adds certain attributes to non-default zero values 2016-05-17 03:16:17 UTC

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.


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