[ https://issues.jboss.org/browse/JBTM-3014?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Amos Feng created pull request #1302 in GitHub
----------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> Support all the pooling parameters of the DBCP2 in the TransactionalDataSourceFactory
> -------------------------------------------------------------------------------------
>
> Key: JBTM-3014
> URL: https://issues.jboss.org/browse/JBTM-3014
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.next
>
>
> Currently we just support the minIdle, maxIdle, maxTotal and it needs to support all the configuration parameters [1].
> [1] https://commons.apache.org/proper/commons-dbcp/configuration.html
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3014?page=com.atlassian.jira.plugin.... ]
Michal Karm Babacek updated JBTM-3014:
--------------------------------------
Tester: Michal Karm Babacek
> Support all the pooling parameters of the DBCP2 in the TransactionalDataSourceFactory
> -------------------------------------------------------------------------------------
>
> Key: JBTM-3014
> URL: https://issues.jboss.org/browse/JBTM-3014
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.next
>
>
> Currently we just support the minIdle, maxIdle, maxTotal and it needs to support all the configuration parameters [1].
> [1] https://commons.apache.org/proper/commons-dbcp/configuration.html
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
Amos Feng created JBTM-3014:
-------------------------------
Summary: Support all the pooling parameters of the DBCP2 in the TransactionalDataSourceFactory
Key: JBTM-3014
URL: https://issues.jboss.org/browse/JBTM-3014
Project: JBoss Transaction Manager
Issue Type: Enhancement
Reporter: Amos Feng
Assignee: Amos Feng
Fix For: 5.next
Currently we just support the minIdle, maxIdle, maxTotal and it needs to support all the configuration parameters [1].
[1] https://commons.apache.org/proper/commons-dbcp/configuration.html
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3012?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-3012:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Cache recovery connection in Tomcat integration
> -----------------------------------------------
>
> Key: JBTM-3012
> URL: https://issues.jboss.org/browse/JBTM-3012
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Tomcat
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> The current TransactionalDataSourceFactory allocates a new XAConnection per recovery manager cycle. It would be better to close it or cache it so we don't get the possibility of a leak with perhaps some databases
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3013?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-3013:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Update Tomcat integration test to be able to use Postgres database
> ------------------------------------------------------------------
>
> Key: JBTM-3013
> URL: https://issues.jboss.org/browse/JBTM-3013
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Tomcat
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> Currently it uses H2 but it would be useful to demonstrate this working on Postgres too
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3013?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-3013:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/1299
> Update Tomcat integration test to be able to use Postgres database
> ------------------------------------------------------------------
>
> Key: JBTM-3013
> URL: https://issues.jboss.org/browse/JBTM-3013
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Tomcat
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> Currently it uses H2 but it would be useful to demonstrate this working on Postgres too
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3012?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-3012:
--------------------------------
Git Pull Request: https://github.com/jbosstm/narayana/pull/1299 (was: https://github.com/jbosstm/narayana/pull/1300)
> Cache recovery connection in Tomcat integration
> -----------------------------------------------
>
> Key: JBTM-3012
> URL: https://issues.jboss.org/browse/JBTM-3012
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Tomcat
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> The current TransactionalDataSourceFactory allocates a new XAConnection per recovery manager cycle. It would be better to close it or cache it so we don't get the possibility of a leak with perhaps some databases
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
Tom Jenkinson created JBTM-3013:
-----------------------------------
Summary: Update Tomcat integration test to be able to use Postgres database
Key: JBTM-3013
URL: https://issues.jboss.org/browse/JBTM-3013
Project: JBoss Transaction Manager
Issue Type: Task
Components: Tomcat
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.next
Currently it uses H2 but it would be useful to demonstrate this working on Postgres too
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
[ https://issues.jboss.org/browse/JBTM-3012?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-3012:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/jbosstm/narayana/pull/1300
> Cache recovery connection in Tomcat integration
> -----------------------------------------------
>
> Key: JBTM-3012
> URL: https://issues.jboss.org/browse/JBTM-3012
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: Tomcat
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.next
>
>
> The current TransactionalDataSourceFactory allocates a new XAConnection per recovery manager cycle. It would be better to close it or cache it so we don't get the possibility of a leak with perhaps some databases
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)