From issues at jboss.org Tue Apr 2 08:36:04 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 08:36:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3126) @LRA may begin a nested LRA without the presence of @NestedLRA In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3126: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > @LRA may begin a nested LRA without the presence of @NestedLRA > --------------------------------------------------------------- > > Key: JBTM-3126 > URL: https://issues.jboss.org/browse/JBTM-3126 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > If a JAX-RS method is invoked and the following conditions are met: > - the invoked method is annotated with LRA.Type.REQUIRES_NEW; > - the invoked method is not annotated with @Nested; > - there is an LRA context present on the incoming request > then the implementation (of the LRA spec) will begin a nested LRA which is contrary to the specified behaviour. Note that there is an [outstanding issue regarding nested LRAs|https://github.com/eclipse/microprofile-lra/issues/117] but this issue affects the implementation of the current specification and needs fixing. > In addition there is also the situation where the outbound JAX-RS request filter may override the LRA context header (this issue can be reproduced by starting an LRA and then starting a JAX-RS request with a different "LRA context header" - the expected behaviour in this case is to run the request with the context set by the user. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 08:40:01 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Tue, 2 Apr 2019 08:40:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: Ivan Straka created JBTM-3128: --------------------------------- Summary: Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB Key: JBTM-3128 URL: https://issues.jboss.org/browse/JBTM-3128 Project: JBoss Transaction Manager Issue Type: Bug Affects Versions: 5.9.0.Final Reporter: Ivan Straka Assignee: Ondrej Chaloupka Running JDBCResources Test003 against Oracle DB: rollback is not performed: *client0_output.txt* {code:java} 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService 2019-04-01 11:10:08,211 out: Failed {code} *Server1.output* {code:java} 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 2019-04-01 11:10:06,687 err: Setting up connection 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo 2019-04-01 11:10:07,244 out: Ready 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService 2019-04-01 11:10:07,876 err: Current Status = 0 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- 2019-04-01 11:10:07,971 err: Current Status = 0 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- 2019-04-01 11:10:07,982 err: Current Status = 0 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- 2019-04-01 11:10:07,994 err: Current Status = 0 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- 2019-04-01 11:10:08,013 err: Current Status = 0 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- 2019-04-01 11:10:08,024 err: Current Status = 0 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- 2019-04-01 11:10:08,034 err: Current Status = 0 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- 2019-04-01 11:10:08,045 err: Current Status = 0 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- 2019-04-01 11:10:08,056 err: Current Status = 0 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- 2019-04-01 11:10:08,070 err: Current Status = 0 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- 2019-04-01 11:10:08,097 err: Current Status = 0 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- 2019-04-01 11:10:08,124 err: Current Status = 0 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- 2019-04-01 11:10:08,183 err: Current Status = 0 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- 2019-04-01 11:10:08,191 err: Current Status = 0 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- 2019-04-01 11:10:08,202 err: Current Status = 0 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' {code} After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. This happens only on Oracle DB. Test passes with 5.2.16.Final bash command: {code:bash} ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest {code} Moreover there are another failures that happens only on Oracle DB: jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 08:40:02 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Tue, 2 Apr 2019 08:40:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Straka updated JBTM-3128: ------------------------------ Affects Version/s: 5.9.5.Final > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 11:11:06 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 11:11:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails on Windows with JDK 11 In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3129: -------------------------------------- Summary: codeCoverage profile fails on Windows with JDK 11 Key: JBTM-3129 URL: https://issues.jboss.org/browse/JBTM-3129 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The vert.x mod-stm artefact fails when running the codeCoverage profile: {quote} mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs {quote} The failure is: {quote} [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport java.lang.ExceptionInInitializerError at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) {quote} This issue only seems to affect the windows slave when running JDK 11 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 11:16:02 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 11:16:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails on Windows with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1436 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > codeCoverage profile fails on Windows with JDK 11 > ------------------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} > This issue only seems to affect the windows slave when running JDK 11 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 12:43:03 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 12:43:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3129: ----------------------------------- Summary: codeCoverage profile fails with JDK 11 (was: codeCoverage profile fails on Windows with JDK 11) > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} > This issue only seems to affect the windows slave when running JDK 11 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 12:43:04 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 12:43:04 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3129: ----------------------------------- Description: The vert.x mod-stm artefact fails when running the codeCoverage profile: {quote} mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs {quote} The failure is: {quote} [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport java.lang.ExceptionInInitializerError at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) {quote} was: The vert.x mod-stm artefact fails when running the codeCoverage profile: {quote} mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs {quote} The failure is: {quote} [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport java.lang.ExceptionInInitializerError at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) {quote} This issue only seems to affect the windows slave when running JDK 11 > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 2 12:48:01 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 2 Apr 2019 12:48:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716770#comment-13716770 ] Michael Musgrove commented on JBTM-3129: ---------------------------------------- The failure occurs when running the maven-surefire-report-plugin. The vertx mod-stm pom is the only artefact in the narayana project using this plugin. Would there be any problem if we just removed it from the build. If we decide later that the plugin is useful then we should apply it to all of the modules. > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 04:16:01 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 3 Apr 2019 04:16:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717046#comment-13717046 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- [~istraka] - it seems OK in our CI: http://narayanaci1.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/387/PROFILE=QA_JTA,jdk=jdk8.latest,label=linux/artifact/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/ > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 05:13:02 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 3 Apr 2019 05:13:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717079#comment-13717079 ] Thomas Jenkinson commented on JBTM-3129: ---------------------------------------- I am not sure why it was added initially, it looks like during initial import from [~marklittle]. For me I see no problem with making it consistent by removing it and adding back if it is desirable later: https://maven.apache.org/surefire/maven-surefire-report-plugin/ > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 09:39:03 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Wed, 3 Apr 2019 09:39:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers In-Reply-To: References: Message-ID: Ivan Straka created JBTM-3130: --------------------------------- Summary: QA tests do not work with recent Oracle and MySQL drivers Key: JBTM-3130 URL: https://issues.jboss.org/browse/JBTM-3130 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Ivan Straka Assignee: Ivan Straka Running QA tests with recent drivers fails for MySQL and Oracle: {code:java} 2019-03-27 11:10:17,440 out: Failed 2019-03-27 11:10:17,440 err: java.lang.Exception: JDBC2 driver oracle.jdbc.OracleDriver not recognised 2019-03-27 11:10:17,440 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) {code} {code:java} 2019-03-27 12:30:59,843 out: Failed 2019-03-27 12:30:59,844 err: java.lang.Exception: JDBC2 driver com.mysql.cj.jdbc.Driver not recognised 2019-03-27 12:30:59,844 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 09:40:14 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Wed, 3 Apr 2019 09:40:14 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Straka updated JBTM-3130: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1435 > QA tests do not work with recent Oracle and MySQL drivers > --------------------------------------------------------- > > Key: JBTM-3130 > URL: https://issues.jboss.org/browse/JBTM-3130 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Major > > Running QA tests with recent drivers fails for MySQL and Oracle: > {code:java} > 2019-03-27 11:10:17,440 out: Failed > 2019-03-27 11:10:17,440 err: java.lang.Exception: JDBC2 driver oracle.jdbc.OracleDriver not recognised > 2019-03-27 11:10:17,440 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} > {code:java} > 2019-03-27 12:30:59,843 out: Failed > 2019-03-27 12:30:59,844 err: java.lang.Exception: JDBC2 driver com.mysql.cj.jdbc.Driver not recognised > 2019-03-27 12:30:59,844 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 13:17:00 2019 From: issues at jboss.org (Laird Nelson (Jira)) Date: Wed, 3 Apr 2019 13:17:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean does not explicitly catch NoInitialContextException In-Reply-To: References: Message-ID: Laird Nelson created JBTM-3131: ---------------------------------- Summary: JNDIBean does not explicitly catch NoInitialContextException Key: JBTM-3131 URL: https://issues.jboss.org/browse/JBTM-3131 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.9.5.Final Reporter: Laird Nelson For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). A similar strategy needs to happen in {{JNDIBean}}. I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 13:22:01 2019 From: issues at jboss.org (Laird Nelson (Jira)) Date: Wed, 3 Apr 2019 13:22:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laird Nelson updated JBTM-3131: ------------------------------- Description: For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. I'll have a pull request to fix this shortly. was: For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). A similar strategy needs to happen in {{JNDIBean}}. I'll have a pull request to fix this shortly. Summary: JNDIBean's create() method can fail with NoInitialContextException (was: JNDIBean does not explicitly catch NoInitialContextException) > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Priority: Major > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 14:42:00 2019 From: issues at jboss.org (Laird Nelson (Jira)) Date: Wed, 3 Apr 2019 14:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Laird Nelson created pull request #1437 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Priority: Major > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 3 14:45:01 2019 From: issues at jboss.org (Laird Nelson (Jira)) Date: Wed, 3 Apr 2019 14:45:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717514#comment-13717514 ] Laird Nelson commented on JBTM-3131: ------------------------------------ Associated pull request: https://github.com/jbosstm/narayana/pull/1437 > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Priority: Major > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 4 08:03:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Thu, 4 Apr 2019 08:03:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3130: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > QA tests do not work with recent Oracle and MySQL drivers > --------------------------------------------------------- > > Key: JBTM-3130 > URL: https://issues.jboss.org/browse/JBTM-3130 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Major > > Running QA tests with recent drivers fails for MySQL and Oracle: > {code:java} > 2019-03-27 11:10:17,440 out: Failed > 2019-03-27 11:10:17,440 err: java.lang.Exception: JDBC2 driver oracle.jdbc.OracleDriver not recognised > 2019-03-27 11:10:17,440 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} > {code:java} > 2019-03-27 12:30:59,843 out: Failed > 2019-03-27 12:30:59,844 err: java.lang.Exception: JDBC2 driver com.mysql.cj.jdbc.Driver not recognised > 2019-03-27 12:30:59,844 err: at org.jboss.jbossts.qa.Utils.JNDIManager.main(JNDIManager.java:162) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 4 08:14:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Thu, 4 Apr 2019 08:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3132) Common parent maven module for Narayana quickstarts In-Reply-To: References: Message-ID: Ondrej Chaloupka created JBTM-3132: -------------------------------------- Summary: Common parent maven module for Narayana quickstarts Key: JBTM-3132 URL: https://issues.jboss.org/browse/JBTM-3132 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Testing Affects Versions: 5.9.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka It would be beneficial to create a common quickstart maven module. My intention is to have a one place where we can define: * common profiles could be defined (one of such profile is Arquillian JDK9+ which defines JVM arguments needed for smooth run of tests, see https://issues.jboss.org/projects/JBTM/issues/JBTM-3122) * common properties like arquillian version. This has benefit that quickstarts will run faster on CI as there won't be multiple versions to be downloaded. * common repositories like jboss one * unified checkstyle definition for all the quickstarts would be coded in one way which makes them easier to read The quickstarts were designed to be independent on each other. The task is not to unified them. The proposal is about creating a place where a common stuff can be placed to. Otherwise the same configuration needs to be copied to multiple places. Which is hard to maintain Other projects, e.g. WildFly, use the same approach of common parent, see https://github.com/wildfly/quickstart/blob/master/app-client/pom.xml -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 04:47:07 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 5 Apr 2019 04:47:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718390#comment-13718390 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- This is pretty strange. As Tom mentioned our CI passes the test. I wanted to simulate the run at my local machine but I failed with dballocator DB machines and with docker instance on my laptop. There is shown a bit strange error {code} com.arjuna.ats.internal.jta.transaction.jts.TransactionImple enlistResource WARN: ARJUNA024046: TransactionImple.enlistResource - XAResource.start returned XA error XAException.XAER_RMERR for transaction < 131072, 29, 36, 0000000000-1-11000500-91-5792-898-84000349, 0000000000-1-11000500-1049792-898-780004500000000 > oracle.jdbc.xa.OracleXAException at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1229) at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:246) at com.arjuna.ats.internal.jdbc.IsSameRMOverrideXAResource.start(IsSameRMOverrideXAResource.java:66) at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.enlistResource(TransactionImple.java:746) at com.arjuna.ats.internal.jdbc.ConnectionImple.registerDatabase(ConnectionImple.java:940) at com.arjuna.ats.internal.jdbc.ConnectionImple.createStatement(ConnectionImple.java:155) at org.jboss.jbossts.qa.JDBCResources01Impls.JDBCInfoTableImpl01.insert(JDBCInfoTableImpl01.java:102) at org.jboss.jbossts.qa.JDBCResources01.InfoTablePOATie.insert(InfoTablePOATie.java:39) at org.jboss.jbossts.qa.JDBCResources01.InfoTablePOA._invoke(InfoTablePOA.java:42) at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:654) at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:205) at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1700) at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1558) at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:940) at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:198) at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:712) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:474) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1237) at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:490) at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:519) Caused by: java.sql.SQLException: ORA-06550: line 1, column 14: PLS-00201: identifier 'JAVA_XA.XA_START_NEW' must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignored at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:220) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:48) at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:938) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798) at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:4901) at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:5631) at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1385) at oracle.jdbc.xa.client.OracleXAResource.doStart(OracleXAResource.java:292) at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:241) ... 18 more {code} I was investigating if that's a trouble of the database or my installation of java/orb but I'm still not able to say. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 04:48:08 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 5 Apr 2019 04:48:08 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3128: ----------------------------------- Attachment: java_xa.xa_start_new_mustbedeclared-server1_output.txt > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 04:56:02 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Fri, 5 Apr 2019 04:56:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718399#comment-13718399 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- I can't say for sure but this: https://developer.ibm.com/answers/questions/236718/why-am-i-getting-java-xaxa-start-new-must-be-decla/ suggests that perhaps the thick (rather than thin) driver is being used. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 05:23:18 2019 From: issues at jboss.org (Martin Stefanko (Jira)) Date: Fri, 5 Apr 2019 05:23:18 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3127) LRA TCK Test Failure (mixedMultiLevelNestedActivity) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Stefanko reassigned JBTM-3127: ------------------------------------- Assignee: Martin Stefanko (was: Michael Musgrove) > LRA TCK Test Failure (mixedMultiLevelNestedActivity) > ---------------------------------------------------- > > Key: JBTM-3127 > URL: https://issues.jboss.org/browse/JBTM-3127 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > This TCK failure was introduced when MP-LRA PR https://github.com/eclipse/microprofile-lra/pull/115 removed the Java Client API. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 05:34:01 2019 From: issues at jboss.org (Anonymous (Jira)) Date: Fri, 5 Apr 2019 05:34:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3127) LRA TCK Test Failure (mixedMultiLevelNestedActivity) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Martin Stefanko created pull request #1438 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRA TCK Test Failure (mixedMultiLevelNestedActivity) > ---------------------------------------------------- > > Key: JBTM-3127 > URL: https://issues.jboss.org/browse/JBTM-3127 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > This TCK failure was introduced when MP-LRA PR https://github.com/eclipse/microprofile-lra/pull/115 removed the Java Client API. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 06:03:06 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 5 Apr 2019 06:03:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718437#comment-13718437 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- Yes, there is several tips on the internet about this situation. One is using thin driver. But I used the thin one (which is from my understanding one which is fully implemented in java, e.g. [here|https://stackoverflow.com/questions/21711085/what-is-the-difference-between-oci-and-thin-driver-connection-with-data-source-c]). Other advice is about the DB does not support XA but I tested it with other testsuite and XA works fine. Other advice talks about a subscription for Oracle but I don't think this is something which is valid here. Still under investigation... > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 06:03:07 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 5 Apr 2019 06:03:07 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718437#comment-13718437 ] Ondrej Chaloupka edited comment on JBTM-3128 at 4/5/19 6:02 AM: ---------------------------------------------------------------- Yes, there are several tips on the internet about this situation. One is using thin driver. But I used the thin one (which is from my understanding one which is fully implemented in java, e.g. [here|https://stackoverflow.com/questions/21711085/what-is-the-difference-between-oci-and-thin-driver-connection-with-data-source-c]). Other advice is about the DB does not support XA but I tested it with other testsuite and XA works fine. Other advice talks about a subscription for Oracle but I don't think this is something which is valid here. Still under investigation... was (Author: ochaloup): Yes, there is several tips on the internet about this situation. One is using thin driver. But I used the thin one (which is from my understanding one which is fully implemented in java, e.g. [here|https://stackoverflow.com/questions/21711085/what-is-the-difference-between-oci-and-thin-driver-connection-with-data-source-c]). Other advice is about the DB does not support XA but I tested it with other testsuite and XA works fine. Other advice talks about a subscription for Oracle but I don't think this is something which is valid here. Still under investigation... > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 5 06:58:02 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Fri, 5 Apr 2019 06:58:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718470#comment-13718470 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- I assume it is working with Oracle 11 and not 12 then? And when you tried with the other test suite it was definitely the same DB and using XA? https://community.oracle.com/thread/738088 > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 8 07:16:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Mon, 8 Apr 2019 07:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3133) DB2 object store tests does not work in CI In-Reply-To: References: Message-ID: Ondrej Chaloupka created JBTM-3133: -------------------------------------- Summary: DB2 object store tests does not work in CI Key: JBTM-3133 URL: https://issues.jboss.org/browse/JBTM-3133 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The DB2 object store tests does not work in CI. The error is {code} [ERROR] test(com.hp.mwtests.ts.arjuna.abstractrecords.ActivationRecordUnitTest) Time elapsed: 0.612 s <<< ERROR! java.lang.ExceptionInInitializerError at com.arjuna.ats.arjuna.coordinator.BasicAction.Begin(BasicAction.java:1377) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:76) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:65) at com.arjuna.ats.arjuna.AtomicAction.begin(AtomicAction.java:116) at com.arjuna.ats.arjuna.AtomicAction.begin(AtomicAction.java:98) at com.hp.mwtests.ts.arjuna.abstractrecords.ActivationRecordUnitTest.test(ActivationRecordUnitTest.java:46) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) Caused by: java.lang.NullPointerException at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) at com.arjuna.ats.arjuna.recovery.ActionStatusService.(ActionStatusService.java:65) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:125) at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.(TransactionStatusManager.java:58) at com.arjuna.ats.arjuna.coordinator.TxControl.createTransactionStatusManager(TxControl.java:188) at com.arjuna.ats.arjuna.coordinator.TxControl.(TxControl.java:264) ... 30 more {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 8 07:41:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Mon, 8 Apr 2019 07:41:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3133) DB2 object store tests does not work in CI In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka resolved JBTM-3133. ------------------------------------ Resolution: Done Fixed by Tom, user on DB2 was missing to run. The CI repo README was updated. > DB2 object store tests does not work in CI > ------------------------------------------ > > Key: JBTM-3133 > URL: https://issues.jboss.org/browse/JBTM-3133 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The DB2 object store tests does not work in CI. The error is > {code} > [ERROR] test(com.hp.mwtests.ts.arjuna.abstractrecords.ActivationRecordUnitTest) Time elapsed: 0.612 s <<< ERROR! > java.lang.ExceptionInInitializerError > at com.arjuna.ats.arjuna.coordinator.BasicAction.Begin(BasicAction.java:1377) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:65) > at com.arjuna.ats.arjuna.AtomicAction.begin(AtomicAction.java:116) > at com.arjuna.ats.arjuna.AtomicAction.begin(AtomicAction.java:98) > at com.hp.mwtests.ts.arjuna.abstractrecords.ActivationRecordUnitTest.test(ActivationRecordUnitTest.java:46) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > Caused by: java.lang.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68) > at com.arjuna.ats.arjuna.recovery.ActionStatusService.(ActionStatusService.java:65) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:125) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.(TransactionStatusManager.java:58) > at com.arjuna.ats.arjuna.coordinator.TxControl.createTransactionStatusManager(TxControl.java:188) > at com.arjuna.ats.arjuna.coordinator.TxControl.(TxControl.java:264) > ... 30 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 8 12:09:06 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Mon, 8 Apr 2019 12:09:06 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Jenkinson updated JBTM-3129: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > codeCoverage profile fails with JDK 11 > -------------------------------------- > > Key: JBTM-3129 > URL: https://issues.jboss.org/browse/JBTM-3129 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The vert.x mod-stm artefact fails when running the codeCoverage profile: > {quote} > mvn -B site clean install -B -Prelease,community -PcodeCoverage -Pfindbugs > {quote} > The failure is: > {quote} > [WARNING] Error injecting: org.apache.maven.plugin.javadoc.JavadocReport > java.lang.ExceptionInInitializerError > at org.apache.maven.plugin.javadoc.AbstractJavadocMojo.(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 9 03:30:02 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 9 Apr 2019 03:30:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3134) Init store failure could provide more information in the exception than just NullPointer In-Reply-To: References: Message-ID: Ondrej Chaloupka created JBTM-3134: -------------------------------------- Summary: Init store failure could provide more information in the exception than just NullPointer Key: JBTM-3134 URL: https://issues.jboss.org/browse/JBTM-3134 Project: JBoss Transaction Manager Issue Type: Enhancement Affects Versions: 5.9.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka When `StorageManager` fails with to initialize store instance the error comes as `NullPointerException`. That's not much informative. The exception should says what happens. The example of the exception thrown now is[1]. The more information then is available in the log but still exception should give some basic idea what happens not just `NullPointerException`. [1] {code} java.lang.NullPointerException at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) at com.arjuna.ats.arjuna.objectstore.StoreManager.setupStore(StoreManager.java:136) at com.hp.mwtests.ts.arjuna.abstractrecords.CadaverRecordUnitTest.test(CadaverRecordUnitTest.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 9 03:33:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 9 Apr 2019 03:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3134) Init store failure could provide more information in the exception than just NullPointer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondrej Chaloupka created pull request #1439 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Init store failure could provide more information in the exception than just NullPointer > ---------------------------------------------------------------------------------------- > > Key: JBTM-3134 > URL: https://issues.jboss.org/browse/JBTM-3134 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > When `StorageManager` fails with to initialize store instance the error comes as `NullPointerException`. That's not much informative. The exception should says what happens. The example of the exception thrown now is[1]. The more information then is available in the log but still exception should give some basic idea what happens not just `NullPointerException`. > [1] > {code} > java.lang.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.setupStore(StoreManager.java:136) > at com.hp.mwtests.ts.arjuna.abstractrecords.CadaverRecordUnitTest.test(CadaverRecordUnitTest.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 10 03:38:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 10 Apr 2019 03:38:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3134) Init store failure could provide more information in the exception than just NullPointer In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3134: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Init store failure could provide more information in the exception than just NullPointer > ---------------------------------------------------------------------------------------- > > Key: JBTM-3134 > URL: https://issues.jboss.org/browse/JBTM-3134 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > When `StorageManager` fails with to initialize store instance the error comes as `NullPointerException`. That's not much informative. The exception should says what happens. The example of the exception thrown now is[1]. The more information then is available in the log but still exception should give some basic idea what happens not just `NullPointerException`. > [1] > {code} > java.lang.NullPointerException > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:159) > at com.arjuna.ats.arjuna.objectstore.StoreManager.setupStore(StoreManager.java:136) > at com.hp.mwtests.ts.arjuna.abstractrecords.CadaverRecordUnitTest.test(CadaverRecordUnitTest.java:49) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 10 06:01:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 10 Apr 2019 06:01:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3135) Update BlackTie to build with a 64-bit C compiler on Windows In-Reply-To: References: Message-ID: Thomas Jenkinson created JBTM-3135: -------------------------------------- Summary: Update BlackTie to build with a 64-bit C compiler on Windows Key: JBTM-3135 URL: https://issues.jboss.org/browse/JBTM-3135 Project: JBoss Transaction Manager Issue Type: Task Components: BlackTie, Build System Reporter: Thomas Jenkinson Assignee: Zheng Feng Fix For: 5.next JDK11 does not provide a 32-bit compiler and our existing build system uses a 32 bit compiler on Windows so it is failing. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 10 06:10:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 10 Apr 2019 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3135) Update BlackTie to build with a 64-bit C compiler on Windows In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Thomas Jenkinson created pull request #1440 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update BlackTie to build with a 64-bit C compiler on Windows > ------------------------------------------------------------ > > Key: JBTM-3135 > URL: https://issues.jboss.org/browse/JBTM-3135 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie, Build System > Reporter: Thomas Jenkinson > Assignee: Zheng Feng > Priority: Major > Fix For: 5.next > > > JDK11 does not provide a 32-bit compiler and our existing build system uses a 32 bit compiler on Windows so it is failing. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 10 06:10:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 10 Apr 2019 06:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3105) STM TaxonomyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Thomas Jenkinson created pull request #1440 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > STM TaxonomyTest failure > ------------------------ > > Key: JBTM-3105 > URL: https://issues.jboss.org/browse/JBTM-3105 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There was test failure during a CI PR test: testIsClosedNestedParentNotVisible(org.jboss.stm.TaxonomyTest) on job > http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/jdk=jdk9.latest,label=catelyn/12/ -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 12 09:26:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 12 Apr 2019 09:26:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721782#comment-13721782 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- This was a struggle for me to get it running. To the issues {{identifier 'JAVA_XA.XA_START_NEW' must be declared}}: I found out that's caused by the incompatibility of the old JDBC driver ({{oracle14.jar}}) to new Oracle DB ({{Oracle 11+}}) and in the opposite of new JDBC driver ({{oracle7/8.jar}}) to older Oracle DB ({{Oracle 10}}). I needed to dig deep to the qa suite so I at least wrote notes here: https://developer.jboss.org/wiki/NarayanaqaTests-HowToRun [~istraka] despite I'm currently capable to run the test without configuration failures I can't reproduce the reported failure. I tried to combine different databases for the object store and for the test storage and other things. But the test passes for me. I was looking at the CI report as well but there I haven't deducted anything more. As Tom mentioned our CI passes. Probably I would need from you some more clues on how to reproduce this. (now I'm thinking about some influencing one test by other test but that's hard to check.) > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 12 10:49:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 12 Apr 2019 10:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka reassigned JBTM-3131: -------------------------------------- Assignee: Laird Nelson > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 12 10:49:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 12 Apr 2019 10:49:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3131: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1437 > JNDIBean's create() method can fail with NoInitialContextException > ------------------------------------------------------------------ > > Key: JBTM-3131 > URL: https://issues.jboss.org/browse/JBTM-3131 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.9.5.Final > Reporter: Laird Nelson > Assignee: Laird Nelson > Priority: Major > > For background, see https://github.com/jbosstm/narayana/pull/1403#issuecomment-479495649 and following. > Briefly, in the CDI integration area of {{ArjunaJTA/cdi}}, {{JNDIBean}} attempts to create an {{InitialContext}}. In application server scenarios, the relevant metadata to permit this to happen will exist, and there won't be any issues (so Wildfly etc. are fine here). In CDI SE, it is possible that such metadata _won't_ exist, and a {{NoInitialContextException}} will be thrown. > {{NarayanaTransactionManager}} uses a similar strategy, but correctly prevents {{NoInitialContextExceptions}} from being thrown (https://github.com/jbosstm/narayana/blob/54b60a4db37ca859b9742d5f6f25cc828312ab4c/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/NarayanaTransactionManager.java#L181). > The proper solution is to ensure that a {{TransactionSynchronizationRegistry}} bean is set up in a similar manner to {{NarayanaTransactionManager}}. > I'll have a pull request to fix this shortly. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 12 11:06:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Fri, 12 Apr 2019 11:06:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721862#comment-13721862 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- [~istraka] is it consistent failure? Perhaps [~ochaloup] could connect to same DB to see if it helps to use debugger? > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Sat Apr 13 03:51:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Sat, 13 Apr 2019 03:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3105) STM TaxonomyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722022#comment-13722022 ] Michael Musgrove commented on JBTM-3105: ---------------------------------------- There are two issues with the nested tests: - the transactional object is not marked with @Nested - the second thread that performs a nested update catches Exceptions with fail() in the catch block. This does not seem to cause the test to fail. The fix is twofold, catch Throwable and assert failure in the main thread (see PR for the fix) > STM TaxonomyTest failure > ------------------------ > > Key: JBTM-3105 > URL: https://issues.jboss.org/browse/JBTM-3105 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There was test failure during a CI PR test: testIsClosedNestedParentNotVisible(org.jboss.stm.TaxonomyTest) on job > http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/jdk=jdk9.latest,label=catelyn/12/ -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 03:22:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Mon, 15 Apr 2019 03:22:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722133#comment-13722133 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- My test was connecting to the same database as Ivan referred to but. Still, I'm not able to get the observed behaviour. I tried to connect to the database for object store or for the test data and I combined that in various orders. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 03:22:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Mon, 15 Apr 2019 03:22:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722133#comment-13722133 ] Ondrej Chaloupka edited comment on JBTM-3128 at 4/15/19 3:21 AM: ----------------------------------------------------------------- [~tomjenkinson] My test was connecting to the same database as Ivan referred to but. Still, I'm not able to get the observed behaviour. I tried to connect to the database for object store or for the test data and I combined that in various orders. was (Author: ochaloup): My test was connecting to the same database as Ivan referred to but. Still, I'm not able to get the observed behaviour. I tried to connect to the database for object store or for the test data and I combined that in various orders. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 09:22:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 15 Apr 2019 09:22:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3127) LRA TCK Test Failure (mixedMultiLevelNestedActivity) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3127: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA TCK Test Failure (mixedMultiLevelNestedActivity) > ---------------------------------------------------- > > Key: JBTM-3127 > URL: https://issues.jboss.org/browse/JBTM-3127 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > This TCK failure was introduced when MP-LRA PR https://github.com/eclipse/microprofile-lra/pull/115 removed the Java Client API. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 09:33:01 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 15 Apr 2019 09:33:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3062) Include a test for LRA context propagation across a "non-LRA aware" service In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-3062. ---------------------------------- Resolution: Done Duplicated by [JBTM-3035|https://issues.jboss.org/browse/JBTM-3035] > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.jboss.org/browse/JBTM-3062 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > If a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and service A in turn calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. A test is needed for this behaviour. > This issue relates to https://github.com/eclipse/microprofile-lra/issues/7 -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 09:42:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 15 Apr 2019 09:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-3072. ---------------------------------- Resolution: Done The test is included in one of the [MP-LRA TCK tests|https://github.com/eclipse/microprofile-lra/blob/master/tck/src/main/java/org/eclipse/microprofile/lra/tck/TckLRATypeTests.java#L222] > Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose > ---------------------------------------------------------------------------------------- > > Key: JBTM-3072 > URL: https://issues.jboss.org/browse/JBTM-3072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a test that verifies the correct behaviour when a method is annotated with both REQUIRES_NEW and delayClose, ie something like: > {code} > @PUT > @Path(ActivityController.ACCEPT_WORK) > @LRA(value = LRA.Type.REQUIRES_NEW, delayClose = true) > public Response doInNewLRA( ....) {...} > {code} > The expected behaviour is: > {code} > /** > * If called outside a LRA context a new LRA will be created for the > * the duration of the method call and when the call completes it will > * be closed (this behaviour can be overridden using the > * {@link LRA#delayClose} attribute). > * > * If called inside a LRA context it will be suspended and a new LRA > * context will be created for the duration of the call. When the method > * finishes this new LRA will be closed and the original context will be > * resumed. This behaviour can be overridden using the > * {@link LRA#delayClose} attribute) in which case the original LRA > * remains suspended and the new LRA becomes the active one and only > * when that one is terminated will the original context be resumed. > */ > REQUIRES_NEW, > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 11:33:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 15 Apr 2019 11:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-3087: ------------------------------------ Re-opening to track more changes to the LRA specification > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 15 13:54:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Mon, 15 Apr 2019 13:54:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722627#comment-13722627 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- Thanks [~ochaloup], would you like a second pair of eyes on this or do you think you have enough to continue review? > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 16 01:42:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 16 Apr 2019 01:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722768#comment-13722768 ] Ondrej Chaloupka edited comment on JBTM-3128 at 4/16/19 1:41 AM: ----------------------------------------------------------------- [~tomjenkinson] I did the review but I don't understand if and where the race condition is. I tried matrix of combinations of different Oracle DBs instances (local, from lab, narayana ci one) and in different configuration (using jdbc store, using standard object store) and still the test passes without issue. I talked with [~istraka] asking him to rerun his testing to confirm how to reproduce. One of my suspicion is if previous test could influence the later one. The race condition would be then in ordering of the tests. But despite this assumption I'm not successful to reproduce it. [~tomjenkinson] if you have some idea how to reproduce the issue I would be grateful if you take a look. was (Author: ochaloup): [~tomjenkinson] I did the review but I don't understand if and where the race condition is. I tried matrix of combinations of different Oracle DBs instances (local, from lab, narayana ci one) and in different configuration (using jdbc store, using standard object store) and still the test passes without issue. I talked with [~istraka] asking him to rerun his testing to confirm how to reproduce. One of my suspicion is if previous test could influence the later one. The race condition would be then in ordering of the tests. But even here I still was not successful to reproduce it. [~tomjenkinson] if you have some idea how to reproduce the issue I would be grateful if you take a look. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 16 01:42:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 16 Apr 2019 01:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722768#comment-13722768 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- [~tomjenkinson] I did the review but I don't understand if and where the race condition is. I tried matrix of combinations of different Oracle DBs instances (local, from lab, narayana ci one) and in different configuration (using jdbc store, using standard object store) and still the test passes without issue. I talked with [~istraka] asking him to rerun his testing to confirm how to reproduce. One of my suspicion is if previous test could influence the later one. The race condition would be then in ordering of the tests. But even here I still was not successful to reproduce it. [~tomjenkinson] if you have some idea how to reproduce the issue I would be grateful if you take a look. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 16 05:20:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Tue, 16 Apr 2019 05:20:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722882#comment-13722882 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- [~istraka] I think we need to see your outputs please. For this and the preceeding test. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 16 11:33:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 16 Apr 2019 11:33:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3105) STM TaxonomyTest failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3105: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > STM TaxonomyTest failure > ------------------------ > > Key: JBTM-3105 > URL: https://issues.jboss.org/browse/JBTM-3105 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There was test failure during a CI PR test: testIsClosedNestedParentNotVisible(org.jboss.stm.TaxonomyTest) on job > http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-catelyn/jdk=jdk9.latest,label=catelyn/12/ -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 08:42:01 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Wed, 17 Apr 2019 08:42:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723678#comment-13723678 ] Ivan Straka commented on JBTM-3128: ----------------------------------- Hi, sorry for the delay. command is: {code:java} ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" onetest -Dcode.coverage=false {code} JDBCProfiles: {code:java} DB_THIN_JNDI_NumberOfDrivers=2 DB_THIN_JNDI_Driver0=oracle.jdbc.OracleDriver DB_THIN_JNDI_Driver1=com.arjuna.ats.jdbc.TransactionalDriver DB_THIN_JNDI_DatabaseUser=crashrec DB_THIN_JNDI_DatabasePassword=crashrec DB_THIN_JNDI_DatabaseName=dballo DB_THIN_JNDI_Host=oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com DB_THIN_JNDI_Port=1521 DB_THIN_JNDI_Binding=oracle_thin DB_THIN_JNDI_DatabaseURL=jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo {code} https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-JBossTS/view/full/job/eap-7.x-jbossts-qa-tests-full/DB=NONE,TARGET=junit-jdbc-ncl-testsuite,TARGET2=NONE,jdk=oracle-java-1.8,label_exp=RHEL7/13/artifact/qa/config/jdbc_profiles/default/JDBCProfiles/*view*/ Driver: http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.3.0/oracle12cR1RAC/jdbc4/ > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 08:42:01 2019 From: issues at jboss.org (Ivan Straka (Jira)) Date: Wed, 17 Apr 2019 08:42:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723679#comment-13723679 ] Ivan Straka commented on JBTM-3128: ----------------------------------- Yes, it fails consistently. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 08:44:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 17 Apr 2019 08:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka closed JBTM-3128. ---------------------------------- Resolution: Rejected This is a test issue. The trouble is in how the {{JDBCProfiles}} is configured. The test uses the {code} DB1_THIN_JNDI_NumberOfDrivers=2 DB1_THIN_JNDI_Driver0=oracle.jdbc.OracleDriver DB1_THIN_JNDI_Driver1=com.arjuna.ats.jdbc.TransactionalDriver DB1_THIN_JNDI_DatabaseUser=crash2 DB1_THIN_JNDI_DatabasePassword=crash2 DB1_THIN_JNDI_DatabaseName=dballo DB1_THIN_JNDI_Host=oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com DB1_THIN_JNDI_Port=1521 DB1_THIN_JNDI_Binding=oracle_thin1 DB1_THIN_JNDI_DatabaseURL=jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo {code} where it defines the {{DatabaseURL}} as {{jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo}}. This means the Narayana transactional jdbc driver is not used. The URL uses directly the Oracle driver. Because of that the connection is not enlisted to the transaction and then it's not rolled-back. The {{JDBCProperties}} has to configure the {{DB1_THIN_JNDI_DatabaseURL}} as {{jdbc:arjuna:oracle_thin1}}. The {{URL}} has to be defined as what the {{DB1_THIN_JNDI_Binding}} links to. > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 08:53:00 2019 From: issues at jboss.org (Thomas Jenkinson (Jira)) Date: Wed, 17 Apr 2019 08:53:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723693#comment-13723693 ] Thomas Jenkinson commented on JBTM-3128: ---------------------------------------- Thanks Ondra!! > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 08:58:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 17 Apr 2019 08:58:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723696#comment-13723696 ] Ondrej Chaloupka commented on JBTM-3128: ---------------------------------------- See https://github.com/jbosstm/narayana/blob/master/qa/config/jdbc_profiles/default/JDBCProfiles#L141 > Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB > -------------------------------------------------------------------- > > Key: JBTM-3128 > URL: https://issues.jboss.org/browse/JBTM-3128 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.0.Final, 5.9.5.Final > Reporter: Ivan Straka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: java_xa.xa_start_new_mustbedeclared-server1_output.txt > > > Running JDBCResources Test003 against Oracle DB: rollback is not performed: > *client0_output.txt* > {code:java} > 2019-04-01 11:10:07,245: Task [client0 102]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0-coverage.ec -DportOffsetId=5 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/client0 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Clients.Client03 value_1 > 2019-04-01 11:10:07,466 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:07,469 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:07,469 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:07,725 err: com.arjuna.ats.arjuna [main] ARJUNA012170: TransactionStatusManager started on port 39358 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:08,211 out: Failed > {code} > *Server1.output* > {code:java} > 2019-04-01 11:10:06,094: Task [server1 101]: starting command: /qa/tools/opt/x86_64/jdk1.8.0_last/bin/java -classpath /home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/jboss-as/build/target/jboss-eap-7.3/modules/system/layers/base/io/netty/main/netty-all-4.1.25.Final-redhat-00003.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/etc/:dbdrivers/jconn4.jar:dbdrivers/db2jcc4.jar:dbdrivers/ojdbc8.jar:dbdrivers/mssql-jdbc-6.4.0.jre8.jar:dbdrivers/mysql-connector-java-8.0.12.jar:dbdrivers/postgresql-42.2.2.jar:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/*:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/*:ext/fscontext.jar:ext/providerutil.jar:ext/jboss-profiler-jvmti.jar:ext/jboss-logging-spi.jar:tests/build/classes/:dbdrivers/selected_dbdriver/*:dbdrivers/DB2_v9.7/db2jcc.jar:dbdrivers/jConnect-6_0/classes/jconn3.jar:dbdrivers/mssql2005_sqljdbc_2.0/enu/sqljdbc4.jar:dbdrivers/mysql-connector-java-5.1.8-bin.jar:dbdrivers/oracle_10_2_0_4/ojdbc14.jar:dbdrivers/postgresql-8.3-605.jdbc4.jar:ext/log4j.jar:ext/netty.jar -Dqa.debug=true -Djava.naming.provider.url=file:///tmp -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Dperformanceprofilestore.dir=config/perf_profiles/ -Djdbcprofilestore.dir=config/jdbc_profiles -Dmemorytestprofilestore.dir=config/memory_profiles/ -Dots.server.bindname=value_1 -DCoordinatorEnvironmentBean.maintainHeuristics=NO -DRecoveryEnvironmentBean.recoveryBackoffPeriod=5 -DCoreEnvironmentBean.timeoutFactor=1 -DCoordinatorEnvironmentBean.defaultTimeout=120 -DCoordinatorEnvironmentBean.dynamic1PC=false -Dio.narayana.perf.failonregression=false -Xbootclasspath/p:dist/narayana-full-5.9.6.Final-SNAPSHOT/lib/ext/openjdk-orb.jar -Xms1024m -Xmx1024m -XX:ParallelGCThreads=2 -Demma.coverage.out.file=./testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1-coverage.ec -DportOffsetId=4 -DObjectStoreBaseDir=/home/hudson/hudson_workspace/workspace/eap-7.x-jbossts-qa-tests-full/0187c9fc/qa/testoutput/jdbcresources01_oracle_thin_jndi/JDBCResources01_abstract_Test003/server1 -DRecoveryEnvironmentBean.recoveryListener=true org.jboss.jbossts.qa.JDBCResources01Servers.Server01 DB1_THIN_JNDI value_1 > 2019-04-01 11:10:06,339 err: log4j:WARN No appenders could be found for logger (org.jboss.logging). > 2019-04-01 11:10:06,339 err: log4j:WARN Please initialize the log4j system properly. > 2019-04-01 11:10:06,339 err: log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. > 2019-04-01 11:10:06,687 err: Setting up connection > 2019-04-01 11:10:07,162 err: connection = oracle.jdbc.driver.T4CConnection at 646be2c3 > 2019-04-01 11:10:07,162 err: Database URL = jdbc:oracle:thin:@oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com:1521:dballo > 2019-04-01 11:10:07,244 out: Ready > 2019-04-01 11:10:07,795 err: 01------------------ doing insert (Name_0,Value_0) ----------------------------- > 2019-04-01 11:10:07,846 err: com.arjuna.ats.arjuna [p: default-threadpool; w: Idle] ARJUNA012170: TransactionStatusManager started on port 33107 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService > 2019-04-01 11:10:07,876 err: Current Status = 0 > 2019-04-01 11:10:07,931 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_0', 'Value_0') > 2019-04-01 11:10:07,971 err: 01------------------ doing insert (Name_1,Value_1) ----------------------------- > 2019-04-01 11:10:07,971 err: Current Status = 0 > 2019-04-01 11:10:07,971 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_1', 'Value_1') > 2019-04-01 11:10:07,982 err: 01------------------ doing insert (Name_2,Value_2) ----------------------------- > 2019-04-01 11:10:07,982 err: Current Status = 0 > 2019-04-01 11:10:07,982 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_2', 'Value_2') > 2019-04-01 11:10:07,994 err: 01------------------ doing insert (Name_3,Value_3) ----------------------------- > 2019-04-01 11:10:07,994 err: Current Status = 0 > 2019-04-01 11:10:07,994 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_3', 'Value_3') > 2019-04-01 11:10:08,013 err: 01------------------ doing insert (Name_4,Value_4) ----------------------------- > 2019-04-01 11:10:08,013 err: Current Status = 0 > 2019-04-01 11:10:08,013 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_4', 'Value_4') > 2019-04-01 11:10:08,024 err: 01------------------ doing insert (Name_5,Value_5) ----------------------------- > 2019-04-01 11:10:08,024 err: Current Status = 0 > 2019-04-01 11:10:08,024 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_5', 'Value_5') > 2019-04-01 11:10:08,034 err: 01------------------ doing insert (Name_6,Value_6) ----------------------------- > 2019-04-01 11:10:08,034 err: Current Status = 0 > 2019-04-01 11:10:08,034 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_6', 'Value_6') > 2019-04-01 11:10:08,045 err: 01------------------ doing insert (Name_7,Value_7) ----------------------------- > 2019-04-01 11:10:08,045 err: Current Status = 0 > 2019-04-01 11:10:08,045 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_7', 'Value_7') > 2019-04-01 11:10:08,056 err: 01------------------ doing insert (Name_8,Value_8) ----------------------------- > 2019-04-01 11:10:08,056 err: Current Status = 0 > 2019-04-01 11:10:08,056 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_8', 'Value_8') > 2019-04-01 11:10:08,070 err: 01------------------ doing insert (Name_9,Value_9) ----------------------------- > 2019-04-01 11:10:08,070 err: Current Status = 0 > 2019-04-01 11:10:08,070 err: INSERT INTO crash2_rhel7_medium_33452_ VALUES('Name_9', 'Value_9') > 2019-04-01 11:10:08,092 err: 01------------------ doing update (Name_3,Value_8) ----------------------------- > 2019-04-01 11:10:08,097 err: Current Status = 0 > 2019-04-01 11:10:08,097 err: UPDATE crash2_rhel7_medium_33452_ SET Value = 'Value_8' WHERE Name = 'Name_3' > 2019-04-01 11:10:08,117 err: 01------------------ doing select (Name_0) ----------------------------- > 2019-04-01 11:10:08,124 err: Current Status = 0 > 2019-04-01 11:10:08,124 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_0' > 2019-04-01 11:10:08,183 err: 01------------------ doing select (Name_1) ----------------------------- > 2019-04-01 11:10:08,183 err: Current Status = 0 > 2019-04-01 11:10:08,183 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_1' > 2019-04-01 11:10:08,191 err: 01------------------ doing select (Name_2) ----------------------------- > 2019-04-01 11:10:08,191 err: Current Status = 0 > 2019-04-01 11:10:08,191 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_2' > 2019-04-01 11:10:08,202 err: 01------------------ doing select (Name_3) ----------------------------- > 2019-04-01 11:10:08,202 err: Current Status = 0 > 2019-04-01 11:10:08,202 err: SELECT Value FROM crash2_rhel7_medium_33452_ WHERE Name = 'Name_3' > {code} > After adding some prints to JDBCResources01Clients/Client03.java I can see that value for "Name_3" is "Value_8", therefore rollback was not performed. > This happens only on Oracle DB. Test passes with 5.2.16.Final > bash command: > {code:bash} > ant -f run-tests.xml -Dtest.name=jdbcresources01_oracle_thin_jndi -Dtest.methods="JDBCResources01_abstract_Test003" -Dprofile=oracle -Djdbc.db.url="oracle-12cr1.rhev-ci-vms.eng.rdu2.redhat.com" -Djdbc.db.name=dballo -Djdbc.db.user=crashrec -Djdbc.db.password=crashrec -Djdbc.db.port=1521 onetest > {code} > Moreover there are another failures that happens only on Oracle DB: > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test003 Fail (0m13.560s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test004 Fail (0m12.856s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test009 Fail (0m13.824s) > jdbcresources01_oracle_thin_jndi JDBCResources01_abstract_Test010 Fail (0m13.889s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test003 Fail (0m13.253s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test004 Fail (0m13.101s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test009 Fail (0m13.755s) > jdbcresources02_oracle_thin_jndi JDBCResources02_abstract_Test010 Fail (0m14.125s) > I can provide outputs if you need. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 17 11:45:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Wed, 17 Apr 2019 11:45:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3137) Too much variance it the performance PR checker In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3137: -------------------------------------- Summary: Too much variance it the performance PR checker Key: JBTM-3137 URL: https://issues.jboss.org/browse/JBTM-3137 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The PERF axis of the PR checker job runs some tests to validate that the PR does not introduce any regressions but the axis is not useful since there is too much variance in the runs. For example PR https://github.com/jbosstm/narayana/pull/1437 ran 3 times each producing wildly different results. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 18 04:41:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 18 Apr 2019 04:41:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3137) Too much variance in the performance PR checker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3137: ----------------------------------- Summary: Too much variance in the performance PR checker (was: Too much variance it the performance PR checker) > Too much variance in the performance PR checker > ----------------------------------------------- > > Key: JBTM-3137 > URL: https://issues.jboss.org/browse/JBTM-3137 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The PERF axis of the PR checker job runs some tests to validate that the PR does not introduce any regressions but the axis is not useful since there is too much variance in the runs. For example PR https://github.com/jbosstm/narayana/pull/1437 ran 3 times each producing wildly different results. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 18 16:02:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 18 Apr 2019 16:02:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Michael Musgrove created pull request #1443 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Reopened) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 04:48:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 04:48:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka reopened JBTM-3079: ------------------------------------ Assignee: Ondrej Chaloupka (was: Thomas Jenkinson) > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Ondrej Chaloupka > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 04:48:01 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 04:48:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3079: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1387 > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Ondrej Chaloupka > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 04:49:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 04:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3079: ----------------------------------- Status: Pull Request Sent (was: Reopened) > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Ondrej Chaloupka > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 04:49:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 04:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3079: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Ondrej Chaloupka > Priority: Critical > Fix For: 5.9.2.Final, 5.5.34.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 04:49:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 04:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka closed JBTM-3079. ---------------------------------- > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Ondrej Chaloupka > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:14:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:14:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not work to run commit for crash recovery In-Reply-To: References: Message-ID: Ondrej Chaloupka created JBTM-3138: -------------------------------------- Summary: XTS txbridge does not work to run commit for crash recovery Key: JBTM-3138 URL: https://issues.jboss.org/browse/JBTM-3138 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.9.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. In scenario * WS call to the WFLY server * inbound bridge injects the JTA transactions as subordinate under the WS AT one * prepare is called and the 2PC phase finishes * commit phase starts and JVM crashes * restart of WFLY server * recovery is expected to commit the participants the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:15:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:15:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not work to run commit for crash recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1391 > XTS txbridge does not work to run commit for crash recovery > ----------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:16:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when succesfully prepared on crash recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Summary: XTS txbridge does not run commit when succesfully prepared on crash recovery (was: XTS txbridge does not work to run commit for crash recovery) > XTS txbridge does not run commit when succesfully prepared on crash recovery > ---------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:20:05 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:20:05 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when succesfully prepared on crash recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725579#comment-13725579 ] Ondrej Chaloupka commented on JBTM-3138: ---------------------------------------- It seems the recovery calls {{commit}} but the {{coordinator}} on the {{Prepared}} command is {{null}} (https://github.com/jbosstm/narayana/blob/5.9.5.Final/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CoordinatorProcessorImpl.java#L135). Because of that the rollback is sent (https://github.com/jbosstm/narayana/blob/5.9.5.Final/XTS/WS-T/dev/src/com/arjuna/wst11/messaging/CoordinatorProcessorImpl.java#L150). It sounds that the {{Coordinator}} instance is not activated for the durable participant (e.g. named as {{D0:ffff0a280527:4bf12fc8:5cbf1cd7:1d}}). The reason is under investigation. > XTS txbridge does not run commit when succesfully prepared on crash recovery > ---------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:21:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when succesfully prepared on crash recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Attachment: server.log stacktrace.txt > XTS txbridge does not run commit when succesfully prepared on crash recovery > ---------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 23 11:21:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Tue, 23 Apr 2019 11:21:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when succesfully prepared on crash recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Steps to Reproduce: >From the PR https://github.com/jbosstm/narayana/pull/1391 running the test {code} mvn clean install -Parq -Dtest=InboundCrashRecoveryTests#testCrashCommit {code} > XTS txbridge does not run commit when succesfully prepared on crash recovery > ---------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 24 03:49:02 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 24 Apr 2019 03:49:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Summary: XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later (was: XTS txbridge does not run commit when succesfully prepared on crash recovery) > XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later > ----------------------------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 24 03:51:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 24 Apr 2019 03:51:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3138: ----------------------------------- Workaround Description: Forbid the 1PC to be used. Either in WFLY config {code} {code} or with system property {code} -DCoordinatorEnvironmentBean.commitOnePhase=false {code} Workaround: Workaround Exists > XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later > ----------------------------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Wed Apr 24 05:31:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Wed, 24 Apr 2019 05:31:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725950#comment-13725950 ] Ondrej Chaloupka commented on JBTM-3138: ---------------------------------------- This seems to be caused by 1PC which does not store data to the Narayana object store. If 2PC is used (e.g. forced with parameter {{-DCoordinatorEnvironmentBean.commitOnePhase=false}}) the behaviour is correct and the consistency is not harmed. > XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later > ----------------------------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 25 04:42:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 25 Apr 2019 04:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3087: ----------------------------------- Affects Version/s: 5.9.5.Final (was: 5.9.1.Final) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 25 04:42:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 25 Apr 2019 04:42:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3087: ----------------------------------- Fix Version/s: 5.next (was: 5.9.3.Final) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Thu Apr 25 04:44:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Thu, 25 Apr 2019 04:44:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726471#comment-13726471 ] Michael Musgrove commented on JBTM-3087: ---------------------------------------- Latest PR is https://github.com/jbosstm/narayana/pull/1443 > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 07:49:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 07:49:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: Ondrej Chaloupka created JBTM-3139: -------------------------------------- Summary: XTS localjunit xtstest at XTS/localjunit/xtstest are never run Key: JBTM-3139 URL: https://issues.jboss.org/browse/JBTM-3139 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.9.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. {code} [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- [INFO] No sources to compile [INFO] [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- [INFO] [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar [INFO] [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- [INFO] Tests are skipped. {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 08:28:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 08:28:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3138) XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727043#comment-13727043 ] Ondrej Chaloupka commented on JBTM-3138: ---------------------------------------- possibly connected with issue JBTM-396 > XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later > ----------------------------------------------------------------------------------------------- > > Key: JBTM-3138 > URL: https://issues.jboss.org/browse/JBTM-3138 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Critical > Attachments: server.log, stacktrace.txt > > > As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant. > In scenario > * WS call to the WFLY server > * inbound bridge injects the JTA transactions as subordinate under the WS AT one > * prepare is called and the 2PC phase finishes > * commit phase starts and JVM crashes > * restart of WFLY server > * recovery is expected to commit the participants > the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed. > This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 08:32:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 08:32:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727047#comment-13727047 ] Ondrej Chaloupka commented on JBTM-3139: ---------------------------------------- I found out the {{xtstest}} module contains no tests. It's only a supportive module which is used by other tests. The code of the {{xtstest}} creates only a war archive which is used by {{crashrecovery}} test module. > XTS localjunit xtstest at XTS/localjunit/xtstest are never run > -------------------------------------------------------------- > > Key: JBTM-3139 > URL: https://issues.jboss.org/browse/JBTM-3139 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. > {code} > [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- > [INFO] No sources to compile > [INFO] > [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- > [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar > [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- > [INFO] Tests are skipped. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 08:37:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 08:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3139: ----------------------------------- Priority: Minor (was: Major) > XTS localjunit xtstest at XTS/localjunit/xtstest are never run > -------------------------------------------------------------- > > Key: JBTM-3139 > URL: https://issues.jboss.org/browse/JBTM-3139 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. > {code} > [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- > [INFO] No sources to compile > [INFO] > [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- > [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar > [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- > [INFO] Tests are skipped. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 08:37:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 08:37:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Ondrej Chaloupka created pull request #1444 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > XTS localjunit xtstest at XTS/localjunit/xtstest are never run > -------------------------------------------------------------- > > Key: JBTM-3139 > URL: https://issues.jboss.org/browse/JBTM-3139 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. > {code} > [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- > [INFO] No sources to compile > [INFO] > [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- > [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar > [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- > [INFO] Tests are skipped. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Fri Apr 26 08:38:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Fri, 26 Apr 2019 08:38:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3139: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/1444 > XTS localjunit xtstest at XTS/localjunit/xtstest are never run > -------------------------------------------------------------- > > Key: JBTM-3139 > URL: https://issues.jboss.org/browse/JBTM-3139 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. > {code} > [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- > [INFO] No sources to compile > [INFO] > [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- > [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar > [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- > [INFO] Tests are skipped. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Sat Apr 27 00:26:00 2019 From: issues at jboss.org (Ondrej Chaloupka (Jira)) Date: Sat, 27 Apr 2019 00:26:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3139) XTS localjunit xtstest at XTS/localjunit/xtstest are never run In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ondrej Chaloupka updated JBTM-3139: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Edited README and jenkins ci script. > XTS localjunit xtstest at XTS/localjunit/xtstest are never run > -------------------------------------------------------------- > > Key: JBTM-3139 > URL: https://issues.jboss.org/browse/JBTM-3139 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.9.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > Tests in module {{XTS/localjunit/xtstest}} are never run. Even when used the `-Parq` the tests invocation is skipped. > {code} > [INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ xtstest --- > [INFO] No sources to compile > [INFO] > [INFO] --- byteman-rulecheck-maven-plugin:4.0.4:rulecheck (rulecheck) @ xtstest --- > [INFO] > [INFO] --- maven-dependency-plugin:3.1.1:copy-dependencies (copy-dependencies) @ xtstest --- > [INFO] Copying byteman-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman.jar > [INFO] Copying byteman-submit-4.0.4.jar to /home/jenkins/workspace/btny-pulls-narayana/PROFILE/XTS/jdk/jdk8.latest/label/linux/XTS/localjunit/xtstest/target/lib/byteman-submit.jar > [INFO] > [INFO] --- maven-surefire-plugin:2.20:test (default-test) @ xtstest --- > [INFO] Tests are skipped. > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 29 04:23:00 2019 From: issues at jboss.org (Martin Stefanko (Jira)) Date: Mon, 29 Apr 2019 04:23:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3140) Update LRA to 1.0-20190429.061212-359 In-Reply-To: References: Message-ID: Martin Stefanko created JBTM-3140: ------------------------------------- Summary: Update LRA to 1.0-20190429.061212-359 Key: JBTM-3140 URL: https://issues.jboss.org/browse/JBTM-3140 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: LRA Affects Versions: 5.9.5.Final Reporter: Martin Stefanko Assignee: Martin Stefanko Update LRA to latest specification versions {code:xml} 1.0-20190429.061212-359 1.0-20190429.061213-359 {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 29 04:39:00 2019 From: issues at jboss.org (Anonymous (Jira)) Date: Mon, 29 Apr 2019 04:39:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3140) Update LRA to 1.0-20190429.061212-359 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Issue was automatically transitioned when Martin Stefanko created pull request #1445 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update LRA to 1.0-20190429.061212-359 > ------------------------------------- > > Key: JBTM-3140 > URL: https://issues.jboss.org/browse/JBTM-3140 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update LRA to latest specification versions > {code:xml} > 1.0-20190429.061212-359 > 1.0-20190429.061213-359 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 29 07:16:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 29 Apr 2019 07:16:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3141) Verify that LRA logs a warning when participant status does not match the expected outcome In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-3141: -------------------------------------- Summary: Verify that LRA logs a warning when participant status does not match the expected outcome Key: JBTM-3141 URL: https://issues.jboss.org/browse/JBTM-3141 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next If participants are unable to compensate the implementation should log a warning (and similarly for complete). Check that the implementation does this. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Mon Apr 29 07:18:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Mon, 29 Apr 2019 07:18:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3141) Verify that LRA logs a warning when participant status does not match the expected outcome In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3141: ----------------------------------- Description: If participants are unable to compensate the implementation should log a warning (and similarly for complete). Check that the implementation does this. was:If participants are unable to compensate the implementation should log a warning (and similarly for complete). Check that the implementation does this. > Verify that LRA logs a warning when participant status does not match the expected outcome > ------------------------------------------------------------------------------------------ > > Key: JBTM-3141 > URL: https://issues.jboss.org/browse/JBTM-3141 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > If participants are unable to compensate the implementation should log a warning (and similarly for complete). Check that the implementation does this. -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 30 08:10:00 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 30 Apr 2019 08:10:00 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3140) Update LRA to 1.0-20190429.061212-359 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-3140: ----------------------------------- Status: Open (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/1445 This functionality is included in JBTM-3087 [PR1446|https://github.com/jbosstm/narayana/pull/1445] > Update LRA to 1.0-20190429.061212-359 > ------------------------------------- > > Key: JBTM-3140 > URL: https://issues.jboss.org/browse/JBTM-3140 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update LRA to latest specification versions > {code:xml} > 1.0-20190429.061212-359 > 1.0-20190429.061213-359 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002) From issues at jboss.org Tue Apr 30 08:11:01 2019 From: issues at jboss.org (Michael Musgrove (Jira)) Date: Tue, 30 Apr 2019 08:11:01 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-3140) Update LRA to 1.0-20190429.061212-359 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-3140. ---------------------------------- Resolution: Rejected > Update LRA to 1.0-20190429.061212-359 > ------------------------------------- > > Key: JBTM-3140 > URL: https://issues.jboss.org/browse/JBTM-3140 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update LRA to latest specification versions > {code:xml} > 1.0-20190429.061212-359 > 1.0-20190429.061213-359 > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)