[jboss-jira] [JBoss JIRA] (JBAS-9539) ${jdbc.maxPoolSize} value in *-ds.xml file always read as 0 in JBOSS 6.1

[Karthick Narayanan (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-9539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777648#comment-12777648 ] 

Karthick Narayanan commented on JBAS-9539:
------------------------------------------

It looks like the fix is the following changeset which was already fixed in JBOSS 5.1 patch but didn't made to JBOSS 6.1 final version.

https://source.jboss.org/changelog/JBossAS6?cs=109885

Can we have this patch added to JBOSS 6.1-final?
                
> ${jdbc.maxPoolSize} value in *-ds.xml file always read as 0 in JBOSS 6.1
> ------------------------------------------------------------------------
>
>                 Key: JBAS-9539
>                 URL: https://issues.jboss.org/browse/JBAS-9539
>             Project: Application Server 3  4  5 and 6
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: 6.1.0
>         Environment: CentOS/Windows
>            Reporter: Karthick Narayanan
>            Assignee: Jesper Pedersen
>              Labels: regression
>
> I’ve recently started using JBoss 6.1.0 and ran into an issue with setting min and max pool size in oracle-ds.xml. I tried two approaches (for both max and min pool size): 
> 1. as a hardcoded number like <max-pool-size>5</max-pool-size>
> 2. as a configurable variable like <max-pool-size>${jdbc.maxPoolSize}</max-pool-size>
> While the first approach worked fine the second one didn't. When the max and min pool sizes were set as configurable variables, the Java.sql.DataSource object created had max-pool-size=0 and min-pool-size=0. All the other settings (being set as configurable variables) in the same xml config file worked as expected. When I did further investigation I found that,
> Org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer class reads all the oracle*-ds.xml files and sets the max/min pool size values to 0 even though I specified <max-pool-size>${jdbc.maxPoolSize}</max-pool-size>. It is not going and reading the value from the property file.
> This had been working fine in JBoss 4.2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira