November 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2799) Javadoc Tomcat module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2799?page=com.atlassian.jira.plugin.... ] Work on JBTM-2799 started by Gytis Trikleris. --------------------------------------------- > Javadoc Tomcat module > --------------------- > > Key: JBTM-2799 > URL: https://issues.jboss.org/browse/JBTM-2799 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2774: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> changed the Status of [bug 1387316|https://bugzilla.redhat.com/show_bug.cgi?id=1387316] from ON_QA to VERIFIED > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.38, 5.2.20.Final, 5.4.0.Final > > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2798) Connection.isClosed throws NullPointerException or returns false after close

by Mirko Streckenbach (JIRA)

[ https://issues.jboss.org/browse/JBTM-2798?page=com.atlassian.jira.plugin.... ] Mirko Streckenbach commented on JBTM-2798: ------------------------------------------ I created a pull request with two additional testcases: https://github.com/jbosstm/narayana/pull/1092. Warning: this contains only the testcases, no fixes. I'm willing to provide the fixes. > Connection.isClosed throws NullPointerException or returns false after close > ---------------------------------------------------------------------------- > > Key: JBTM-2798 > URL: https://issues.jboss.org/browse/JBTM-2798 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.4.0.Final > Reporter: Mirko Streckenbach > > The following snippet fails with a NullPointerException: > {code} > Connection c = ConnectionManager.create(dbUrl, properties); > System.err.println("closed1=" + c.isClosed()); > c.close(); > System.err.println("closed2=" + c.isClosed()); > {code} > output: > {code} > closed1=false > java.lang.NullPointerException > at com.arjuna.ats.internal.jdbc.ConnectionImple.closeImpl(ConnectionImple.java:389) > at com.arjuna.ats.internal.jdbc.ConnectionImple.close(ConnectionImple.java:381) > at org.jboss.narayana.quickstarts.jta.Main.main(Main.java:140) > {code} > If it is modified to "use" the init the physical connect before closing, it will not throw an > exception, but returns false for isClosed after the close: > {code} > Connection c = ConnectionManager.create(dbUrl, properties); > System.err.println("closed1=" + c.isClosed()); > c.createStatement().close(); > System.err.println("closed2=" + c.isClosed()); > c.close(); > System.err.println("closed3=" + c.isClosed()); > {code} > output: > {code} > closed1=false > closed2=false > closed3=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2798) Connection.isClosed throws NullPointerException or returns false after close

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-2798?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Mirko Streckenbach created pull request #1092 in GitHub ------------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Connection.isClosed throws NullPointerException or returns false after close > ---------------------------------------------------------------------------- > > Key: JBTM-2798 > URL: https://issues.jboss.org/browse/JBTM-2798 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.4.0.Final > Reporter: Mirko Streckenbach > > The following snippet fails with a NullPointerException: > {code} > Connection c = ConnectionManager.create(dbUrl, properties); > System.err.println("closed1=" + c.isClosed()); > c.close(); > System.err.println("closed2=" + c.isClosed()); > {code} > output: > {code} > closed1=false > java.lang.NullPointerException > at com.arjuna.ats.internal.jdbc.ConnectionImple.closeImpl(ConnectionImple.java:389) > at com.arjuna.ats.internal.jdbc.ConnectionImple.close(ConnectionImple.java:381) > at org.jboss.narayana.quickstarts.jta.Main.main(Main.java:140) > {code} > If it is modified to "use" the init the physical connect before closing, it will not throw an > exception, but returns false for isClosed after the close: > {code} > Connection c = ConnectionManager.create(dbUrl, properties); > System.err.println("closed1=" + c.isClosed()); > c.createStatement().close(); > System.err.println("closed2=" + c.isClosed()); > c.close(); > System.err.println("closed3=" + c.isClosed()); > {code} > output: > {code} > closed1=false > closed2=false > closed3=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2798) Connection.isClosed throws NullPointerException or returns false after close

by Mirko Streckenbach (JIRA)

Mirko Streckenbach created JBTM-2798: ---------------------------------------- Summary: Connection.isClosed throws NullPointerException or returns false after close Key: JBTM-2798 URL: https://issues.jboss.org/browse/JBTM-2798 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.4.0.Final Reporter: Mirko Streckenbach The following snippet fails with a NullPointerException: {code} Connection c = ConnectionManager.create(dbUrl, properties); System.err.println("closed1=" + c.isClosed()); c.close(); System.err.println("closed2=" + c.isClosed()); {code} output: {code} closed1=false java.lang.NullPointerException at com.arjuna.ats.internal.jdbc.ConnectionImple.closeImpl(ConnectionImple.java:389) at com.arjuna.ats.internal.jdbc.ConnectionImple.close(ConnectionImple.java:381) at org.jboss.narayana.quickstarts.jta.Main.main(Main.java:140) {code} If it is modified to "use" the init the physical connect before closing, it will not throw an exception, but returns false for isClosed after the close: {code} Connection c = ConnectionManager.create(dbUrl, properties); System.err.println("closed1=" + c.isClosed()); c.createStatement().close(); System.err.println("closed2=" + c.isClosed()); c.close(); System.err.println("closed3=" + c.isClosed()); {code} output: {code} closed1=false closed2=false closed3=false {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2795) Quickstart can not build the karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2795?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2795: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Quickstart can not build the karaf > ---------------------------------- > > Key: JBTM-2795 > URL: https://issues.jboss.org/browse/JBTM-2795 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > {code} > [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:kar (package) on project framework: Execution package of goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:kar failed: An API incompatibility was encountered while executing org.apache.karaf.tooling:karaf-maven-plugin:4.1.0-SNAPSHOT:kar: java.lang.NoSuchMethodError: org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.getReadTimeout()I > {code} > It looks like we need to upgrade the maven and to use the build.bat -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2797) Check the Blacktie build with JDK 9

by Amos Feng (JIRA)

Amos Feng created JBTM-2797: ------------------------------- Summary: Check the Blacktie build with JDK 9 Key: JBTM-2797 URL: https://issues.jboss.org/browse/JBTM-2797 Project: JBoss Transaction Manager Issue Type: Sub-task Components: BlackTie, Build System Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2796) Investigate the Tomcat integration tests failure with the JDK 9

by Amos Feng (JIRA)

Amos Feng created JBTM-2796: ------------------------------- Summary: Investigate the Tomcat integration tests failure with the JDK 9 Key: JBTM-2796 URL: https://issues.jboss.org/browse/JBTM-2796 Project: JBoss Transaction Manager Issue Type: Sub-task Components: Application Server Integration, Build System Reporter: Amos Feng Assignee: Amos Feng Endorsed standards and standalone APIs in modular form will be supported via the concept of upgradeable modules -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2776) Investigate the arquillian tests failure with the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2776?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2776: --------------------------------- It should set the property of server.jvm.args in the j9 profile > Investigate the arquillian tests failure with the JDK 9 > ------------------------------------------------------- > > Key: JBTM-2776 > URL: https://issues.jboss.org/browse/JBTM-2776 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Labels: jdk9 > > the arquillian can not create the container -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2776) Investigate the arquillian tests failure with the JDK 9

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2776?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-2776. ----------------------------- Resolution: Done > Investigate the arquillian tests failure with the JDK 9 > ------------------------------------------------------- > > Key: JBTM-2776 > URL: https://issues.jboss.org/browse/JBTM-2776 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Labels: jdk9 > > the arquillian can not create the container -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 2016