April 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3128) Rollback in QA JDBCResources01 Test003 is not performed on Oracle DB

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3128?page=com.atlassian.jira.plugin.... ] 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@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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3132) Common parent maven module for Narayana quickstarts

by Ondrej Chaloupka (Jira)

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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.... ] 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException

by Laird Nelson (Jira)

[ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.... ] 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/54b60a4db37ca859b9742d5f6f25cc82...). > 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException

by Laird Nelson (Jira)

[ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.... ] 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/54b60a4db37ca859b9742d5f6f25cc82...). > 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean's create() method can fail with NoInitialContextException

by Laird Nelson (Jira)

[ https://issues.jboss.org/browse/JBTM-3131?page=com.atlassian.jira.plugin.... ] 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/54b60a4db37ca859b9742d5f6f25cc82...). 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/54b60a4db37ca859b9742d5f6f25cc82...). 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/54b60a4db37ca859b9742d5f6f25cc82...). > 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3131) JNDIBean does not explicitly catch NoInitialContextException

by Laird Nelson (Jira)

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/54b60a4db37ca859b9742d5f6f25cc82...). 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/JBTM-3130?page=com.atlassian.jira.plugin.... ] 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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3130) QA tests do not work with recent Oracle and MySQL drivers

by Ivan Straka (Jira)

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)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3129) codeCoverage profile fails with JDK 11

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3129?page=com.atlassian.jira.plugin.... ] 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.<clinit>(AbstractJavadocMojo.java:188) > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2019