[JBoss JIRA] (JBTM-1497) Implement JTA 1.2
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1497?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1497:
--------------------------------
Description:
TCK here, this is not necessarily the final version: https://svn.devel.redhat.com/repos/jboss-tck/standalone-tck7/jta/jtatck-1...
Old instructions (for JTA 1.1) here: https://community.jboss.org/wiki/StandaloneJTA11TCKGuide
To test the big new features (@Transactional & @TransactionScoped), we need the Java EE 7 CTS. This is not currently available, so we will need to write our own tests for now and test against the Java EE 7 CTS when it is ready.
Design discusion here: https://community.jboss.org/message/816442
was:
TCK here, this is not necessarily the final version: https://svn.devel.redhat.com/repos/jboss-tck/standalone-tck7/jta/jtatck-1...
Old instructions (for JTA 1.1) here: https://community.jboss.org/wiki/StandaloneJTA11TCKGuide
To test the big new features (@Transactional & @TransactionScoped), we need the Java EE 7 CTS. This is not currently available, so we will need to write our own tests for now and test against the Java EE 7 CTS when it is ready.
> Implement JTA 1.2
> -----------------
>
> Key: JBTM-1497
> URL: https://issues.jboss.org/browse/JBTM-1497
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTA
> Reporter: Tom Jenkinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> TCK here, this is not necessarily the final version: https://svn.devel.redhat.com/repos/jboss-tck/standalone-tck7/jta/jtatck-1...
> Old instructions (for JTA 1.1) here: https://community.jboss.org/wiki/StandaloneJTA11TCKGuide
> To test the big new features (@Transactional & @TransactionScoped), we need the Java EE 7 CTS. This is not currently available, so we will need to write our own tests for now and test against the Java EE 7 CTS when it is ready.
> Design discusion here: https://community.jboss.org/message/816442
--
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, 4 months
[JBoss JIRA] (JBTM-1601) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1601?page=com.atlassian.jira.plugin.... ]
Michael Musgrove resolved JBTM-1601.
------------------------------------
Resolution: Done
Setting a timeout factor in the job config resolves the issue
> Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 on windows machines with jacorb
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1601
> URL: https://issues.jboss.org/browse/JBTM-1601
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 4.17.3, 5.0.0.M2
> Reporter: Ondřej Chaloupka
> Assignee: Michael Musgrove
>
> I'm hitting an issue on qa tests for windows machines. I'm currently testing EAP 6.1.0.ER3.
> Testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2 is failing when it's run on windows machines. It does not matter which JDK is used. It fails on 4.17 branch and master as well.
> This happens for jacorb.
> The fails consistently occur on 5 tests from the testcase - that are from CrashRecovery02_2_Test26 till CrashRecovery02_2_Test30.
> All of them throw assertion:
> {quote}
> junit.framework.AssertionFailedError: task client1 printed Failed.
> {quote}
> These details apply to test CrashRecovery02_2_Test27:
> The client implementation is org.jboss.jbossts.qa.CrashRecovery02.Client02a and the fail comes from line 114 (branch 4.17).
> {code}
> correct = correct && (resourceTrace1 == ResourceTrace.ResourceTraceCommit);
> {code}
> Where the value of resourceTrace1 is {{ResourceTraceNone}}.
> I didn't get with investigation further so far.
> Steps for reproducing could be handy (using narayana.sh script first):
> 1. export NARAYANA_BUILD=0
> export NARAYANA_TESTS=0
> export CP_NARAYANA_AS=0
> export AS_BUILD=0
> export XTS_AS_TESTS=0
> export TXF_TESTS=0
> export XTS_TESTS=0
> export txbridge=0
> export QA_TESTS=1
> export SUN_ORB=0
> export QA_TARGET=test
> export QA_PROFILE="-Dtest=crashrecovery02_2"
> export WORKSPACE=$PWD
> 2. run naryana.sh - there was problem with paths for me so the command looks like this at the end
> {quote}
> sh scripts/hudson/narayana.sh -Demma.jar.location=c:\\tmp\\ochaloup\\ext -Demma.enabled=false -Dorson.jar.location=\\tmp\\ochaloup\\ext
> {quote}
> You can check whole stacktrace from job on jenkins:
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTS/view/JBossT...
> Do you think that you could check this?
--
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, 4 months
[JBoss JIRA] (JBTM-1650) SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon()
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1650:
--------------------------------
Priority: Major (was: Critical)
> SIGPIPE as test_tprecv_sendonly tearDown() is calling tpdiscon()
> -----------------------------------------------------------------
>
> Key: JBTM-1650
> URL: https://issues.jboss.org/browse/JBTM-1650
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 5.0.0.M3
>
>
> ==7024==
> ==7024== Process terminating with default action of signal 13 (SIGPIPE)
> ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so)
> ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6)
> ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287)
> ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325)
> ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519)
> ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147)
> ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182)
> ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219)
> ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63)
> ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182)
> ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32)
> ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15)
> ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20)
> ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77)
> ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178)
> ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97)
> ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145)
> ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96)
> ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64)
> ==7024== by 0x4E2043: main (TestRunner.cxx:27)
--
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, 4 months
[JBoss JIRA] (JBTM-1682) Create Quickstarts for using Compensations API
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1682:
-----------------------------------
Summary: Create Quickstarts for using Compensations API
Key: JBTM-1682
URL: https://issues.jboss.org/browse/JBTM-1682
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Demonstrator, TXFramework, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Priority: Critical
Fix For: 5.0.0.M3
Should cover the 3 examples covered in my JUDConn presentation and the associated blog post.
--
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, 4 months
[JBoss JIRA] (JBTM-1551) Empty '.m2/repository/org/jboss/narayana' prior to running CI
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1551?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1551:
--------------------------------
Assignee: Tom Jenkinson (was: Paul Robinson)
> Empty '.m2/repository/org/jboss/narayana' prior to running CI
> -------------------------------------------------------------
>
> Key: JBTM-1551
> URL: https://issues.jboss.org/browse/JBTM-1551
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> This ensures that no old artefacts are picked up.
> Need to wait for BT to be merged into Narayana as it relies on Narayana artefacts being present in .m2. A failed Narayana build will result in these artefacts being missing.
--
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, 4 months
[JBoss JIRA] (JBTM-1554) Create a job for PR on 5_BRANCH and 4_BRANCH
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1554:
--------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
> Create a job for PR on 5_BRANCH and 4_BRANCH
> --------------------------------------------
>
> Key: JBTM-1554
> URL: https://issues.jboss.org/browse/JBTM-1554
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 4.17.5, 5.0.0.M3
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> This will allow us to test changes to our AS fork before merging. I suggest we run all the tests that AS run on lightning, followed by all the Narayana tests.
> We should also come up with a plan for building PR on 4_BRANCH or 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent.
--
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, 4 months
[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1645:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M3)
> Allow pull requests to configure some parameters in scripts/hudson/narayana.sh
> ------------------------------------------------------------------------------
>
> Key: JBTM-1645
> URL: https://issues.jboss.org/browse/JBTM-1645
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> If the pull description has something like this:
> export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests]
> We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to.
--
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, 4 months
[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1468?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1468:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M3)
> Support pure-JTA client and server for WS-AT and REST-AT
> --------------------------------------------------------
>
> Key: JBTM-1468
> URL: https://issues.jboss.org/browse/JBTM-1468
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: REST, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.Final
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT.
> To do this we need to:
> # Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations.
> # Client side JTA->REST-AT bridge. Needs implementing.
> # Server side REST-AT->JTA bridge. Needs integrating into code base.
> # Update the TXBridge quickstarts to use this and move them out.
--
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, 4 months