[JBoss JIRA] (JBTM-2642) ArjunaJTS CosTransactions idl is not spec compliant
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2642:
--------------------------------------
Summary: ArjunaJTS CosTransactions idl is not spec compliant
Key: JBTM-2642
URL: https://issues.jboss.org/browse/JBTM-2642
Project: JBoss Transaction Manager
Issue Type: Bug
Components: JTS
Reporter: Michael Musgrove
Assignee: Michael Musgrove
The copy of CosTransactions.idl in our source tree does not match any of the OTS spec versions, in partciular the enum ordering of Status values is different so we get the wrong status when asking foreign application servers for the status of a transaction.
I checked versions 1.0 and 1.1 (http://www.omg.org/spec/OTS/) and versions 1.3 and 1.4 (http://www.omg.org/spec/TRANS/), I could not locate version 1.2. The idl used by other application servers seems to match versions 1.3 and 1.4:
{code}
enum Status {
StatusActive,
StatusMarkedRollback,
StatusPrepared,
StatusCommitted,
StatusRolledBack,
StatusUnknown,
StatusNoTransaction,
StatusPreparing,
StatusCommitting,
StatusRollingBack
};
{code}
whereas we are using
{code}
enum Status { StatusActive, StatusMarkedRollback, StatusPrepared,
StatusCommitted, StatusRolledBack, StatusUnknown,
StatusPreparing, StatusCommitting, StatusRollingBack,
StatusNoTransaction };
{code}
Notice that the enum position of StatusNoTransaction is different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2638) Initiate connection in JmsXAResourceRecoveryHelper.getXAResources instead of recover
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2638?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris updated JBTM-2638:
----------------------------------
Summary: Initiate connection in JmsXAResourceRecoveryHelper.getXAResources instead of recover (was: Should throw XAException instead of AssertionError in JmsXAResourceRecoveryHelper)
> Initiate connection in JmsXAResourceRecoveryHelper.getXAResources instead of recover
> ------------------------------------------------------------------------------------
>
> Key: JBTM-2638
> URL: https://issues.jboss.org/browse/JBTM-2638
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> Initially I've added assertions in JmsXAResourceRecoveryHelper to check if the recovery scan was started and delegate was initialised. However, XARecoveryModule only catches XAException, so if assertion fails periodic recovery cannot handle it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2578) Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6
by Daniel Simko (JIRA)
[ https://issues.jboss.org/browse/JBTM-2578?page=com.atlassian.jira.plugin.... ]
Daniel Simko resolved JBTM-2578.
--------------------------------
Resolution: Won't Fix
Fixed in our script (narayana_tests_eap70.sh). This script adjusts DB hosts to IPv6 machines in our lab.
> Make "junit-jdbc-ncl-testsuite" testsuite of Narayana/qa compatible with IPv6
> -----------------------------------------------------------------------------
>
> Key: JBTM-2578
> URL: https://issues.jboss.org/browse/JBTM-2578
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Reporter: Hayk Hovsepyan
> Assignee: Daniel Simko
> Priority: Critical
>
> Currently JDBC tests from "junit-jdbc-ncl-testsuite" testsuite of narayana/qa tsts fail while running on pure IPv6 machine.
> The reason is that it is designed to connect to databases via IPv4 protocol, and there are hostnames of DB's specified in project.
> It needs to be modified to connect to databases via IPv6 addresses protocol and run tests on pure Ipv6 machine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2641) Add localisation to JMS module warnings
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-2641:
-------------------------------------
Summary: Add localisation to JMS module warnings
Key: JBTM-2641
URL: https://issues.jboss.org/browse/JBTM-2641
Project: JBoss Transaction Manager
Issue Type: Bug
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Priority: Minor
Fix For: 5.next
Warning messages in JMS modules should be localised same as other modules in ArjunaJTA.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2640) Add username and password to JmsXAResourceRecoveryHelper
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2640?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Gytis Trikleris created pull request #990 in GitHub
---------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
> Add username and password to JmsXAResourceRecoveryHelper
> --------------------------------------------------------
>
> Key: JBTM-2640
> URL: https://issues.jboss.org/browse/JBTM-2640
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: JTA
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> In some scenarios user name and password might be needed during the recovery of JMS resources. For those cases JmsXAResourceRecoveryHelper should be able to take username and password as an argument and use them when creating connections.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2640) Add username and password to JmsXAResourceRecoveryHelper
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-2640:
-------------------------------------
Summary: Add username and password to JmsXAResourceRecoveryHelper
Key: JBTM-2640
URL: https://issues.jboss.org/browse/JBTM-2640
Project: JBoss Transaction Manager
Issue Type: Bug
Components: JTA
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.next
In some scenarios user name and password might be needed during the recovery of JMS resources. For those cases JmsXAResourceRecoveryHelper should be able to take username and password as an argument and use them when creating connections.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (JBTM-2634) Create Narayana Spring Boot starter quickstart
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-2634?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-2634:
---------------------------------------
Yes, I already have a text ready. Just waiting for one Narayana JMS PR to be reviewed.
> Create Narayana Spring Boot starter quickstart
> ----------------------------------------------
>
> Key: JBTM-2634
> URL: https://issues.jboss.org/browse/JBTM-2634
> Project: JBoss Transaction Manager
> Issue Type: Sub-task
> Components: Demonstrator, JTA
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> Create a demonstrator application for Narayana Spring Boot starter before raising pull request to Spring. This would allow to make a better review of the Narayana Spring Boot integration on the forum.
> Quickstart should have a simple example of JTA and crash recovery.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months