[jira] Updated: (DAYTRADER-66) Non-transactional datasource deployment descriptor use transactional definition in db2 and oracle deployment plan
[ https://issues.apache.org/jira/browse/DAYTRADER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated DAYTRADER-66: -- Fix Version/s: 2.2 2.1.3 Assignee: Donald Woods (was: Forrest Xia) Non-transactional datasource deployment descriptor use transactional definition in db2 and oracle deployment plan - Key: DAYTRADER-66 URL: https://issues.apache.org/jira/browse/DAYTRADER-66 Project: DayTrader Issue Type: Bug Components: buildsystem Affects Versions: 2.0 Environment: daytrader trunk Reporter: Forrest Xia Assignee: Donald Woods Priority: Minor Fix For: 2.1.3, 2.2 Attachments: daytrader-66.patch In DB2 and Oracle deployment plan, there are deployment descriptor like this: DB2: connectiondefinition-instance namejdbc/NoTxTradeDataSource/name config-property-setting name=UserNametrade/config-property-setting config-property-setting name=Passwordtrade/config-property-setting config-property-setting name=PortNumber50001/config-property-setting config-property-setting name=ServerNamelocalhost/config-property-setting config-property-setting name=DatabaseNametradedb/config-property-setting config-property-setting name=DriverType4/config-property-setting connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size10/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes30/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance Oracle: connectiondefinition-instance namejdbc/NoTxTradeDataSource/name config-property-setting name=UserNametrade/config-property-setting config-property-setting name=Passwordtrade/config-property-setting config-property-setting name=DatabaseNametradedb/config-property-setting config-property-setting name=DataSourceNameTradeDataSource/config-property-setting config-property-setting name=ServerNamelocalhost/config-property-setting config-property-setting name=PortNumber1160/config-property-setting config-property-setting name=DriverTypethin/config-property-setting connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size10/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes30/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance Obviously, the snippet xa-transactiontransaction-caching//xa-transaction is not correct for a non-transactional datasource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAYTRADER-66) Non-transactional datasource deployment descriptor use transactional definition in db2 and oracle deployment plan
[ https://issues.apache.org/jira/browse/DAYTRADER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated DAYTRADER-66: - Attachment: daytrader-66.patch patch for daytrader trunk Non-transactional datasource deployment descriptor use transactional definition in db2 and oracle deployment plan - Key: DAYTRADER-66 URL: https://issues.apache.org/jira/browse/DAYTRADER-66 Project: DayTrader Issue Type: Bug Components: buildsystem Affects Versions: 2.0 Environment: daytrader trunk Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Attachments: daytrader-66.patch In DB2 and Oracle deployment plan, there are deployment descriptor like this: DB2: connectiondefinition-instance namejdbc/NoTxTradeDataSource/name config-property-setting name=UserNametrade/config-property-setting config-property-setting name=Passwordtrade/config-property-setting config-property-setting name=PortNumber50001/config-property-setting config-property-setting name=ServerNamelocalhost/config-property-setting config-property-setting name=DatabaseNametradedb/config-property-setting config-property-setting name=DriverType4/config-property-setting connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size10/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes30/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance Oracle: connectiondefinition-instance namejdbc/NoTxTradeDataSource/name config-property-setting name=UserNametrade/config-property-setting config-property-setting name=Passwordtrade/config-property-setting config-property-setting name=DatabaseNametradedb/config-property-setting config-property-setting name=DataSourceNameTradeDataSource/config-property-setting config-property-setting name=ServerNamelocalhost/config-property-setting config-property-setting name=PortNumber1160/config-property-setting config-property-setting name=DriverTypethin/config-property-setting connectionmanager xa-transaction transaction-caching/ /xa-transaction single-pool max-size10/max-size min-size0/min-size blocking-timeout-milliseconds5000/blocking-timeout-milliseconds idle-timeout-minutes30/idle-timeout-minutes match-one/ /single-pool /connectionmanager /connectiondefinition-instance Obviously, the snippet xa-transactiontransaction-caching//xa-transaction is not correct for a non-transactional datasource. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
