[JBoss JIRA] (JBTM-2684) Connection pooling for JBossTS Narayana
by Abhijeet Kumar (JIRA)
Abhijeet Kumar created JBTM-2684:
------------------------------------
Summary: Connection pooling for JBossTS Narayana
Key: JBTM-2684
URL: https://issues.jboss.org/browse/JBTM-2684
Project: JBoss Transaction Manager
Issue Type: Enhancement
Components: JTA
Affects Versions: 5.2.9.Final
Reporter: Abhijeet Kumar
Hi,
I'm using JBossTS (Narayana) version 5.2.9 Final. There is no supports for connection pooling through the TransactionDriver. Establishing new physical connection for every transaction will slow down my production service.
Can you please guide me to develop a custom wrapper around the TransactionalDriver of Narayana?
I'm using Apache Tomcat JDBC 8 for connection pooling. I'm also using MysQL as DBServer and MySQLXADataSource as the XADatasource for the TransactionalDriver.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1107:
----------------------------------
Fix Version/s: 5.next
(was: 5.3.3.Final)
> Recovery Support in Compensation API
> ------------------------------------
>
> Key: JBTM-1107
> URL: https://issues.jboss.org/browse/JBTM-1107
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Components: Compensations
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers would be invoked in case of the system crash.
> In addition, @CompensationScoped beans should be available during the recovery.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-1804:
----------------------------------
Fix Version/s: 5.next
(was: 5.3.3.Final)
> JTS remote tests not run and no code coverage
> ---------------------------------------------
>
> Key: JBTM-1804
> URL: https://issues.jboss.org/browse/JBTM-1804
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: JTS, Testing
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build.
> It would then be beneficial to have them instrumented by emma to get code coverage.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months
[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2115:
----------------------------------
Fix Version/s: 5.next
(was: 5.3.3.Final)
> Not all classes are under code coverage
> ---------------------------------------
>
> Key: JBTM-2115
> URL: https://issues.jboss.org/browse/JBTM-2115
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Testing
> Affects Versions: 5.0.1
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The following poms contain skipped classes for code coverage:
> ArjunaCore/arjuna/pom.xml
> ArjunaJTA/jdbc/pom.xml
> ArjunaJTA/jta/pom.xml
> ArjunaJTA/spi/pom.xml
> XTS/localjunit/pom.xml
> We should aim to test everything
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 11 months