March 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when dshaver1 created pull request #1294 in GitHub --------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Support for Oracle Wallet JDBC connections > ------------------------------------------ > > Key: JBTM-3000 > URL: https://issues.jboss.org/browse/JBTM-3000 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Daniel Shaver > Priority: Optional > > In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. > This means that Narayana does not support Oracle Wallet JDBC connections. > This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. > {code:java} > user = info.getProperty(TransactionalDriver.userName, ""); > passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > and in com.arjuna.ats.internal.jdbc.ConnectionManager > {code:java} > String user = info.getProperty(TransactionalDriver.userName, ""); > String passwd = info.getProperty(TransactionalDriver.password, ""); > {code} > I believe it should be okay to just remove default value so that the client's input is always taken as-is. > I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections

by Daniel Shaver (JIRA)

Daniel Shaver created JBTM-3000: ----------------------------------- Summary: Support for Oracle Wallet JDBC connections Key: JBTM-3000 URL: https://issues.jboss.org/browse/JBTM-3000 Project: JBoss Transaction Manager Issue Type: Feature Request Reporter: Daniel Shaver Priority: Optional In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet. This means that Narayana does not support Oracle Wallet JDBC connections. This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. {code:java} user = info.getProperty(TransactionalDriver.userName, ""); passwd = info.getProperty(TransactionalDriver.password, ""); {code} and in com.arjuna.ats.internal.jdbc.ConnectionManager {code:java} String user = info.getProperty(TransactionalDriver.userName, ""); String passwd = info.getProperty(TransactionalDriver.password, ""); {code} I believe it should be okay to just remove default value so that the client's input is always taken as-is. I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Ondra Chaloupka > Fix For: 5.next > > Attachments: surefire.jstack.23019.txt, wfly.jstack.txt > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.<init>(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.<init>(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.<init>(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2999?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2999: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update git url for the jboss-as part of the build > ------------------------------------------------- > > Key: JBTM-2999 > URL: https://issues.jboss.org/browse/JBTM-2999 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.8.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The AS part of the narayana build on mac-os fails with: > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs > fatal: HTTP request failed > {quote} > using the git url does work though: > git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2999?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1291 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update git url for the jboss-as part of the build > ------------------------------------------------- > > Key: JBTM-2999 > URL: https://issues.jboss.org/browse/JBTM-2999 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.8.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The AS part of the narayana build on mac-os fails with: > {quote} > Building AS > First time checkout of AS7 > Cloning into jboss-as... > error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs > fatal: HTTP request failed > {quote} > using the git url does work though: > git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2999) Update git url for the jboss-as part of the build

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2999: -------------------------------------- Summary: Update git url for the jboss-as part of the build Key: JBTM-2999 URL: https://issues.jboss.org/browse/JBTM-2999 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.8.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The AS part of the narayana build on mac-os fails with: {quote} Building AS First time checkout of AS7 Cloning into jboss-as... error: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version while accessing https://github.com/jbosstm/jboss-as.git/info/refs fatal: HTTP request failed {quote} using the git url does work though: git://github.com/jbosstm/jboss-as.git -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2998) Blacktie TestTPGetRply failed with unknown session

by Amos Feng (JIRA)

Amos Feng created JBTM-2998: ------------------------------- Summary: Blacktie TestTPGetRply failed with unknown session Key: JBTM-2998 URL: https://issues.jboss.org/browse/JBTM-2998 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Priority: Minor Fix For: 5.later {noformat} 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :200 ) - get session: 3 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :209 ) - did not get session: 3 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :924 ) - tpgetrply return: -1 tperrno: 2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerLogc :72 ) - CHKCOND ASSERT FAILED C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx:272 {noformat} It looks like that the sessionIds have the prev id in the other tests which has not been removed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2018