[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1804:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.8.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
> 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)
9 years
[JBoss JIRA] (JBTM-2318) Too verbose startup?
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2318?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson closed JBTM-2318.
-------------------------------
> Too verbose startup?
> --------------------
>
> Key: JBTM-2318
> URL: https://issues.jboss.org/browse/JBTM-2318
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Transaction Core
> Affects Versions: 5.0.4
> Reporter: Mark Little
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.2.8.Final
>
>
> At startup of the most basic example we see ...
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService
> INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 52185
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init>
> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 52185
> Dec 17, 2014 8:23:50 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start
> INFO: ARJUNA012170: TransactionStatusManager started on port 52185 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
> There's a separate conversation to be had about whether the INFO should be there (DEBUG maybe?) but ignoring those why do we print the other lines at all?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (JBTM-2564) Run quickstarts on IPv6
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2564?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2564:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.8.Final)
> Run quickstarts on IPv6
> -----------------------
>
> Key: JBTM-2564
> URL: https://issues.jboss.org/browse/JBTM-2564
> Project: JBoss Transaction Manager
> Issue Type: Task
> Components: Demonstrator
> Environment: Pure IPv6 configured RHEL6
> Reporter: Hayk Hovsepyan
> Assignee: Michael Musgrove
> Priority: Minor
> Fix For: 5.next
>
>
> Some of JBossTS Quickstart tests fail on pure-IPv6 linux machine.
> The failure is, that IIOP OPENJDK ORB Service can not be started, possibly because of configuration issue.
> On dual-stack-IPv6 machines they pass.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2544:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.8.Final)
> RTS inbound bridge recovery does not work with JTS
> --------------------------------------------------
>
> Key: JBTM-2544
> URL: https://issues.jboss.org/browse/JBTM-2544
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: REST
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.next
>
>
> If JTS is enabled, crash scenario when system fails just before the commit does not complete correctly. Instead of being committed, resource is rolled back by XARecoveryModule.
> In JTA case, XARecoveryModule does not find any XAResourceRecords and bridge recovery is handled by InboundBridgeRecoveryModule.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years
[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-2498:
--------------------------------
Fix Version/s: 5.next
(was: 5.2.8.Final)
> Incomplete BlackTie quickstart documentation
> --------------------------------------------
>
> Key: JBTM-2498
> URL: https://issues.jboss.org/browse/JBTM-2498
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: BlackTie, Demonstrator, Documentation
> Affects Versions: 5.2.2
> Reporter: Michael Musgrove
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.next
>
>
> The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly.
> Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly.
> My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years