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.
Verified for EAP 6.4.2.CP.CR1.
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.