August 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2737) Karaf build fail

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2737?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-2737. ----------------------------- Resolution: Out of Date > Karaf build fail > ---------------- > > Key: JBTM-2737 > URL: https://issues.jboss.org/browse/JBTM-2737 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project static: Unable to build assembly: Error downloading configuration files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2737) Karaf build fail

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2737?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2737: --------------------------------- It looks like the upstream issue and now it is back to work http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quicksta... > Karaf build fail > ---------------- > > Key: JBTM-2737 > URL: https://issues.jboss.org/browse/JBTM-2737 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > > [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project static: Unable to build assembly: Error downloading configuration files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2737) Karaf build fail

by Amos Feng (JIRA)

Amos Feng created JBTM-2737: ------------------------------- Summary: Karaf build fail Key: JBTM-2737 URL: https://issues.jboss.org/browse/JBTM-2737 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator Reporter: Amos Feng Assignee: Amos Feng [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:assembly (process-resources) on project static: Unable to build assembly: Error downloading configuration files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2723) Upgrade the apr to 1.5

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2723?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2723: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade the apr to 1.5 > ---------------------- > > Key: JBTM-2723 > URL: https://issues.jboss.org/browse/JBTM-2723 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #12 in GitHub --------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2614: ----------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1356589|https://bugzilla.redhat.com/show_bug.cgi?id=1356589] from ASSIGNED to POST > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.35, 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2614) JCA TransactionImporter should be thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2614?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2614: ----------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1356589|https://bugzilla.redhat.com/show_bug.cgi?id=1356589] from NEW to ASSIGNED > JCA TransactionImporter should be thread safe > --------------------------------------------- > > Key: JBTM-2614 > URL: https://issues.jboss.org/browse/JBTM-2614 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.2.12.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.35, 5.2.13.Final > > > I have a unit test that shows there's a race condition (first observed by [~dmlloyd]) in com.arjuna.ats.internal.jta.transaction.arjunacore.jca.TransactionImporterImple#importTransaction(javax.transaction.xa.Xid, int). > If two threads call this method at the same time, two separate transaction objects may be created. Here's the sequence of events: > T1: call importTransaction for XID1 > T2: call importTransaction for XID1 > T1: getImportedTransaction returns null > T2: getImportedTransaction returns null > T1: create new transaction, add to map > T2: create new transaction, add to map (overwriting T1's) > There is nothing in the documentation to indicate that this is not a valid situation or that access to the TransactionImporter has to be single-threaded in any way. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2449) SPI class ServerVMClientUserTransaction should be Serializable and Referenceable

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2449?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2449: ------------------------------------ ServerVMClientUserTransaction is still not fully serializable > SPI class ServerVMClientUserTransaction should be Serializable and Referenceable > -------------------------------------------------------------------------------- > > Key: JBTM-2449 > URL: https://issues.jboss.org/browse/JBTM-2449 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: SPI > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.0 > > > This SPI class implements UserTransaction but does not follow the JNDI conventions. The JTA specification (section 3.1) says: > bq. The implementation of the UserTransaction object must be both javax.naming.Referenceable and java.io.Serializable , so that the object can be stored in all JNDI naming contexts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2685: ----------------------------------- Comment: was deleted (was: We are currently blocked by https://issues.apache.org/jira/browse/SUREFIRE-1265 ) > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2685: ---------------------------------------- And the intended initial set of tests to run with the JDK 9 jvm are as follows (please refer to our CI run script in the master or branch git repo, scripts/hudson/narayana.sh, to see which specific tests each switch runs): BLACKTIE=0 JTA_AS_TESTS=0 XTS_AS_TESTS=0 RTS_AS_TESTS=0 QA_TESTS=0 PERF_TESTS=0 NARAYANA_TESTS=1 TXF_TESTS=1 OSGI_TESTS=1 JTA_CDI_TESTS=1 XTS_TESTS=1 txbridge=1 RTS_TESTS=1 > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 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 August 2016