[GLASSFISH-18439] Statement-leak-timeout and statement-leak-reclaim values do not persist in domain.xml when created with asadmin add-resources Created: 01/Mar/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: jdbc
Affects Version/s: 3.1.2_dev
Fix Version/s: None

Type: Bug Priority: Major
Reporter: emailnbw Assignee: sfelts
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Windows 7 x64, Glassfish 3.1.2_b23, JDK 1.7.0_u3 x64

Attachments: XML File glassfish-resources.xml     Text File jdbc-rm-statement-leak.patch    
Tags: asadmin


This looks like an issue that is very related to GLASSFISH-18026 which was marked as resolved. In this case if I try to create a jdbc-connection-pool using the command 'asadmin add-resources glassfish-resources.xml' and the jdbc-connection-pool element in that XML file have the statement-leak-timeout-in-seconds and statement-leak-reclaim attributes set the resultant JDBC connection pool created will not. I've attached a sample persistence.xml file which demonstrates this.

Comment by ancoron [ 27/Aug/12 ]

Attached a patch jdbc-rm-statement-leak.patch for review and inclusion. it fixes the problem at the source - the resources manager.

Comment by ancoron [ 27/Aug/12 ]

The above patch applies to the 3.1.2 tag but should (with path modification) also apply to trunk.

Comment by emailnbw [ 01/Jul/13 ]

Has this been fixed in GF4 FCS?

Generated at Sat Feb 25 17:01:04 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.