[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1365:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Deploy REST-AT support as a JBossAS subsystem and module
> --------------------------------------------------------
>
> Key: JBTM-1365
> URL: https://issues.jboss.org/browse/JBTM-1365
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: REST
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 weeks
> Time Spent: 3 weeks, 1 day, 4 hours, 59 minutes
> Remaining Estimate: 0 minutes
>
> Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7.
> I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS).
> The subsystem would need to:
> * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping.
> * Deploy the coordinator endpoint.
> The module would need to contain the REST-AT coordinator code and the client libraries.
> h3. Open Issues
> Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1505) WS-BA transaction context not propagated if JTA transaction present.
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1505?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1505:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> WS-BA transaction context not propagated if JTA transaction present.
> --------------------------------------------------------------------
>
> Key: JBTM-1505
> URL: https://issues.jboss.org/browse/JBTM-1505
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: TxBridge, XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 hours
> Time Spent: 1 hour, 1 minute
> Remaining Estimate: 0 minutes
>
> With default-context-propagation enabled:
> What happens if the Client is running in a JTA transaction, then begins a WS-BA transaction before calling a WS-BA enabled service? I suspect, as it stands, we would start a WS-AT transaction as well. This will cause the JaxBaseHeaderContextProcessor to default to WS-AT as it appears first in the if-then-elseif block:
> {code}
> final CoordinationContextType coordinationContext ;
> if (atContext != null)
> {
> coordinationContext = atContext.getCoordinationContext() ;
> }
> else if (baContext != null)
> {
> coordinationContext = baContext.getCoordinationContext() ;
> }
> {code}
> I'm not yet sure how we handle this case. We certainly need a test for it though.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor.
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1719:
-------------------------------------
Summary: Improve test coverage for REST-AT multiplexor.
Key: JBTM-1719
URL: https://issues.jboss.org/browse/JBTM-1719
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: REST
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Fix For: 5.0.0.M4
Implement more unit and integration tests to cover more aspects of multiplexor functionality. Especially recovery.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1611:
-----------------------------------
Fix Version/s: 5.0.0.M4
(was: 5.0.0.M3)
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1611
> URL: https://issues.jboss.org/browse/JBTM-1611
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
> Fix For: 4.17.5, 5.0.0.M4
>
> Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch
>
>
> During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO).
> Tests which are failing:
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09
> - CrashRecovery09_Test01
> - CrashRecovery09_Test03
> - CrashRecovery09_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10
> - CrashRecovery10_Test01
> - CrashRecovery10_Test03
> - CrashRecovery10_Test05
> org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12
> - CrashRecovery12_Test03
> - CrashRecovery12_Test06
> Detailed log could be found in job:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te...
> I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84).
--
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
11 years, 9 months