July 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1818) JacORBGenericRecoveryCreatorUnitTest fails as implname property has not been set

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1818: ----------------------------------- Summary: JacORBGenericRecoveryCreatorUnitTest fails as implname property has not been set Key: JBTM-1818 URL: https://issues.jboss.org/browse/JBTM-1818 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS, Testing Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M4 Moving the class seems to have made the test fail due to the following warning: 144 [main] ERROR jacorb.poa - Cannot create a persistent poa. The implname property has not been set. Jul 02, 2013 9:46:53 PM com.arjuna.ats.internal.jts.orbspecific.jacorb.recoverycoordinators.JacOrbRCServiceInit getRCPOA WARN: ARJUNA022081: Failed to create poa for recoverycoordinators org.omg.PortableServer.POAPackage.InvalidPolicy: IDL:omg.org/PortableServer/POA/InvalidPolicy:1.0 at org.jacorb.poa.POA.create_POA(Unknown Source) I have looked in the code and there is an @BeforeClass @AfterClass pair ArjunaJTS/jts/tests/classes/com/hp/mwtests/ts/jts/orbspecific/recovery/RecoveryEnablementUnitTest.java which set this property. This does not operate as the author expected. The property is indeed set before TestBase has chance to initialize the orb, however the class is not unloaded by JUnit until after the run, hence why the order of when JacORBGenericRecoveryCreatorUnitTest is ran is important. Presumably before it was being run after RecoveryEnablementUnitTest, whereas now it is before. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1814) Clean up idlj building

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1814?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1814: --------------------------------------- Idlj profile can be enabled with -Didlj-enabled. Jacorb profile can be disabled with -Djacorb-disabled. > Clean up idlj building > ---------------------- > > Key: JBTM-1814 > URL: https://issues.jboss.org/browse/JBTM-1814 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > We shouldn't be building JacORB if someone only wants the idlj build. Plus we should ensure that JacORB specific tests do not run if we do not build JacORB (and vice versa). -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1814) Clean up idlj building

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1814?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1814: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/362 > Clean up idlj building > ---------------------- > > Key: JBTM-1814 > URL: https://issues.jboss.org/browse/JBTM-1814 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > We shouldn't be building JacORB if someone only wants the idlj build. Plus we should ensure that JacORB specific tests do not run if we do not build JacORB (and vice versa). -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1813) org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT artefact is missing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1813?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1813: ------------------------------------- Hi Mike, As per our conversation, jbosstm/jboss-as/4_BRANCH needs updating to point to this version. If https://community.jboss.org/wiki/NarayanaReleaseProcess is not correct, please can you tweak it? Tom > org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT artefact is missing > ----------------------------------------------------------------------------------- > > Key: JBTM-1813 > URL: https://issues.jboss.org/browse/JBTM-1813 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.16.7 > > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1802 > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1803 > {code} > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > [WARNING] The POM for org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT is missing, no dependency information available > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > {code} -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1813) org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT artefact is missing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1813?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1813: -------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT artefact is missing > ----------------------------------------------------------------------------------- > > Key: JBTM-1813 > URL: https://issues.jboss.org/browse/JBTM-1813 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.16.7 > > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1802 > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1803 > {code} > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > [WARNING] The POM for org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.5.Final-SNAPSHOT is missing, no dependency information available > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > {code} -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1810) If the XAResourceRecoveryHelper returns a different XAResource and isSameRM does not function correctly for the resource manager it is possible that the _xidScans can contain older XAResources which may cache old Xids so should not be scanned

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1810?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1810: -------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/355, https://github.com/jbosstm/narayana/pull/356 (was: https://github.com/jbosstm/narayana/pull/355) > If the XAResourceRecoveryHelper returns a different XAResource and isSameRM does not function correctly for the resource manager it is possible that the _xidScans can contain older XAResources which may cache old Xids so should not be scanned > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1810 > URL: https://issues.jboss.org/browse/JBTM-1810 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.4 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.0.0.M4, 4.17.6 > > > This is evidenced in linked bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=979058 > I can see in the logs on 979058 that we are trying to call rollback on the same XID, this is coming from an older XAResource reference that has cached the Xid reference in the original scan but wasn't expired by the stale check. > It appears to have been re introduced after 4.17.3.Final as that version does not exhibit the same behavior. Fix is to revert most of: https://github.com/jbosstm/narayana/commit/fc1ce60d8b7cd0f0193350537775b1... -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1817) There is no CI run to test the HQ store against the QA suite

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1817: -------------------------------------- Summary: There is no CI run to test the HQ store against the QA suite Key: JBTM-1817 URL: https://issues.jboss.org/browse/JBTM-1817 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 5.0.0.M3, 4.17.5 Reporter: Michael Musgrove Assignee: Michael Musgrove HQ store coverage in the test suite is 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1814) Clean up idlj building

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1814?page=com.atlassian.jira.plugin.... ] Work on JBTM-1814 started by Gytis Trikleris. > Clean up idlj building > ---------------------- > > Key: JBTM-1814 > URL: https://issues.jboss.org/browse/JBTM-1814 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > We shouldn't be building JacORB if someone only wants the idlj build. Plus we should ensure that JacORB specific tests do not run if we do not build JacORB (and vice versa). -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1816) JavaIDL test wrongly excluded?

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1816?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1816: ---------------------------------- Fix Version/s: 5.0.0.M4 > JavaIDL test wrongly excluded? > ------------------------------ > > Key: JBTM-1816 > URL: https://issues.jboss.org/browse/JBTM-1816 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M4 > > > In the JTS pom.xml within the IDLJ excludes section there is: > <exclude>**/JavaIdlRecoveryUnitTest.java</exclude> > Surely we shouldn't be excluding JavaIdl tests in the JavaIdl run? Should this refer to the JacORB tests instead? -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1814) Clean up idlj building

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1814?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1814: ---------------------------------- Fix Version/s: 5.0.0.M4 > Clean up idlj building > ---------------------- > > Key: JBTM-1814 > URL: https://issues.jboss.org/browse/JBTM-1814 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > We shouldn't be building JacORB if someone only wants the idlj build. Plus we should ensure that JacORB specific tests do not run if we do not build JacORB (and vice versa). -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2013