November 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2537) Remove the need to build WildFly in IBM ORB job config

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2537: -------------------------------- Summary: Remove the need to build WildFly in IBM ORB job config (was: Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana) > Remove the need to build WildFly in IBM ORB job config > ------------------------------------------------------ > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2537: ------------------------------------- I think the problem is that WildFly can only pull in: {quote} <dependency> <groupId>org.jboss.narayana.jts</groupId> <artifactId>narayana-jts-idlj</artifactId> <version>${version.org.jboss.narayana}</version> </dependency> {quote} https://github.com/wildfly/wildfly/blob/master/pom.xml#L4435 It may work now if one of your builds is building that idlj jar but it is still incorrect as WFLY needs updating to build with narayana-jts-ibmorb artifact (and may even need a subsystem change). I think for now we should try to avoid the need to build the app server in our job and wait until WFLY can use the IBM ORB - what do you think? > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-2537 at 11/13/15 5:36 AM: ------------------------------------------------------------------ I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is available in the m2 repo. This should fix it since the build I did after the change progressed past the wildfly build and failed for an unrelated reason. I have started CI job #147 to see if we can get a clean build. was (Author: mmusgrov): I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is still in the m2 repo. > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2537: ---------------------------------------- I have updated the CI job (narayana-ibm-jdk) to build the distribution twice to ensure that the default one is still in the m2 repo. > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2537: -------------------------------- Priority: Major (was: Minor) > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2537) Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2537?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2537: -------------------------------- Summary: Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana (was: Can't build WFLY on a machine that has only built for IBM Orb) > Need to provide a WFLY option to build with IBM orb instead of OpenJDK for Narayana > ----------------------------------------------------------------------------------- > > Key: JBTM-2537 > URL: https://issues.jboss.org/browse/JBTM-2537 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > I am not sure if this might really need a WFLY change instead of JBTM? > I guess it finally caught us after an .m2 wipe? > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-ibm-jdk/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2544) RTS inbound bridge recovery does not work with JTS

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2544?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2544: ----------------------------------- Steps to Reproduce: Add "<jts/>" to the transaction subsystem configuration in standalone/configuration/standalone-rts.xml Update the openjdk subsystem: /subsystem=iiop-openjdk/:write-attribute(name=transactions,value=full) >From Narayana code base execute the following: {code} ./build.sh -f rts/at/bridge/pom.xml clean test -Parq -Dtest=InboundBridgeRecoveryTestCase#testCrashBeforeCommit {code} was: Add "<jts/>" to the transaction subsystem configuration in standalone/configuration/standalone-rts.xml >From Narayana code base execute the following: {code} ./build.sh -f rts/at/bridge/pom.xml clean test -Parq -Dtest=InboundBridgeRecoveryTestCase#testCrashBeforeCommit {code} > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2545) Use consistent naming scheme for ORB jbossts-properties files in the repo

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2545?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2545: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use consistent naming scheme for ORB jbossts-properties files in the repo > ------------------------------------------------------------------------- > > Key: JBTM-2545 > URL: https://issues.jboss.org/browse/JBTM-2545 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.next > > > This simplifies testing makes the tests more consistent. The overall effect on the user is that the default filenames are clearer rather than assuming jacorb. > Plus the fact that narayana-jacorb module has narayana-idlj file in (which is an error IMO) - and the converse is also true. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2557) Support Spring PlatformTransactionManager

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2557?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-2557. ----------------------------- Resolution: Done > Support Spring PlatformTransactionManager > ----------------------------------------- > > Key: JBTM-2557 > URL: https://issues.jboss.org/browse/JBTM-2557 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2556) Improve OSGi integration

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2556?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2556: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/938 > Improve OSGi integration > ------------------------ > > Key: JBTM-2556 > URL: https://issues.jboss.org/browse/JBTM-2556 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Amos Feng > Assignee: Guillaume Nodet > Fix For: 5.next > > > support configuration using ConfigAdmin > track org.jboss.tm.XAResourceRecovery services for recovery > In order to support correctly stopping / restarting / reconfiguring the transaction manager, we build our own class loader to load the core jars. > This ensure that all static fields will be correctly reloaded when starting again after configuration change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 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 November 2015