Spring事务 REQUIRES_NEW、NESTED与NOT_SUPPORTED

最新推荐文章于 2023-03-14 13:44:41 发布
最新推荐文章于 2023-03-14 13:44:41 发布
阅读量8.1k 收藏 2
点赞数 2
分类专栏： Spring事务 文章标签： jta 事务处理
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/chs_jdmdr/article/details/46411879
版权

手动创建一个异常，用来探究Spring事务处理机制。
transactionManager为DataSourceTransactionManager。
本次暂不讨论JTA <tx:jta-transaction-manager/> ，由于公司项目历史原因，不想在项目中使用Jta。

    <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager">
        <property name="dataSource" ref="dataSource"></property>
    </bean>

分别使用Propagation.NESTED与 Propagation.REQUIRES_NEW测试发现，在一系列的操作中，两者的表现形式相同，都是Rollback了所有新增&更新操作。这是什么原因？查看spring doc发现，REQUIRES_NEW与NOT_SUPPORTED都有下面一句话，需要使用JtaTransactionManager。
Note: Actual transaction suspension will not work on out-of-the-box on all transaction managers. This in particular applies to JtaTransactionManager, which requires the javax.transaction.TransactionManager to be made available it to it (which is server-specific in standard J2EE).
但实际情况并非如此，在DataSourceTransactionManager下使用，REQUIRES_NEW没起任何作用，NOT_SUPPORTED则运行良好，正如doc所写：Execute non-transactionally, suspend the current transaction if one exists.
至于NESTED，应该是因为transaction整个都被rollback了，所以也没有commit更新。在日志中会出现如下片段：
DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating nested transaction with name [com….OrderNo]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating in existing transaction
……
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing transaction savepoint

个人觉得在业务不是特别复杂的情况下，使用NOT_SUPPORTED更加简单一些。
在Service其中一个方法中加注解：@Transactional(propagation = Propagation.NOT_SUPPORTED)

logback日志：
10:21:38.107 [http-apr-8080-exec-6] DEBUG com.incito.logistics.common.SpecialCharFilter - process in /web/myorder/agreeRefund
10:21:38.109 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100785} Connection
10:21:38.110 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100785} Preparing Statement:      SELECT * FROM orders WHERE  id =?
10:21:38.110 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
10:21:38.117 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100786} Executing Statement:      SELECT * FROM orders WHERE  id =?
10:21:38.117 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100786} Parameters: [930aebeae7c845c88bb15f985f3cde83]
10:21:38.117 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100786} Types: [java.lang.String]
10:21:38.138 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100787} ResultSet
10:21:38.139 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100787} Header: [id, completetime, generatetime, orderno, status, agentid, carid, goodsid, consigneeid, shipperid, photo, leavelocation, memo, signtime, type, refusal, ordercustom, priseid, weight, volume, goodscustom, refusalreason, refusalmemo, refusaltime, cancelreason, cancelmemo, arrstartcity]
10:21:38.139 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100787} Result: [930aebeae7c845c88bb15f985f3cde83, null, 2015-06-08 10:17:24.0, 04150608000001, 12, 36ff7818c242400db397075c87721db7, fb4db237da604688aeb1f369b5bfd45e, ad532d4b21184280bd0faec9685d1129, null, null, null, 32.08133,112.138352, null, null, 0, null, 0, null, null, null, 0, null, null, null, null, null, 0]
10:21:38.139 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
10:21:38.139 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100788} Connection
10:21:38.139 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100788} Preparing Statement:    SELECT * FROM refundorders WHERE orderid=?
10:21:38.139 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
10:21:38.142 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100789} Executing Statement:    SELECT * FROM refundorders WHERE orderid=?
10:21:38.142 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100789} Parameters: [930aebeae7c845c88bb15f985f3cde83]
10:21:38.143 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100789} Types: [java.lang.String]
10:21:38.147 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100790} ResultSet
10:21:38.148 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100790} Header: [id, orderid, applymoney, applytime, applyreason, applymemo, replytime, replyreason, replymemo, cancelflag, canceltime, reqthirdtime, arbitratetime, arbitrateon, arbitratememo]
10:21:38.148 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100790} Result: [614cee2768e24f7d82a5f90d6f7a58bd, 930aebeae7c845c88bb15f985f3cde83, null, 2015-06-08 10:17:54.0, 3, , null, null, null, null, null, null, null, null, null]
10:21:38.148 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
10:21:38.148 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating new transaction with name [com.incito.logistics.service.OrderService.agreeRefund]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; '',-java.lang.Exception
10:21:38.152 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] for JDBC transaction
10:21:38.155 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] to manual commit
10:21:38.157 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100791} Connection
10:21:38.158 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100791} Preparing Statement:      UPDATE     goods set completedate = null                               where id = ?
10:21:38.158 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100792} Executing Statement:      UPDATE     goods set completedate = null                               where id = ?
10:21:38.158 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100792} Parameters: [ad532d4b21184280bd0faec9685d1129]
10:21:38.158 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100792} Types: [java.lang.String]
10:21:38.162 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100793} Connection
10:21:38.163 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100793} Preparing Statement:      UPDATE     orders     SET        status = ?                                                        , completetime = now()                                                                                                                           WHERE     id = ?
10:21:38.163 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100794} Executing Statement:      UPDATE     orders     SET        status = ?                                                        , completetime = now()                                                                                                                           WHERE     id = ?
10:21:38.163 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100794} Parameters: [16, 930aebeae7c845c88bb15f985f3cde83]
10:21:38.163 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100794} Types: [java.lang.String, java.lang.String]
10:21:38.167 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100795} Connection
10:21:38.168 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100795} Preparing Statement:    UPDATE refundorders   SET     replytime = now()                                               WHERE id = ?
10:21:38.168 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100796} Executing Statement:    UPDATE refundorders   SET     replytime = now()                                               WHERE id = ?
10:21:38.168 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100796} Parameters: [614cee2768e24f7d82a5f90d6f7a58bd]
10:21:38.168 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100796} Types: [java.lang.String]
10:21:38.180 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100797} Connection
10:21:38.180 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100797} Preparing Statement:       SELECT count(1) FROM orders where carid = ? AND status not in (2,7,8,9,10,11,14)
10:21:38.180 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100798} Executing Statement:       SELECT count(1) FROM orders where carid = ? AND status not in (2,7,8,9,10,11,14)
10:21:38.180 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100798} Parameters: [fb4db237da604688aeb1f369b5bfd45e]
10:21:38.180 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100798} Types: [java.lang.String]
10:21:38.185 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100799} ResultSet
10:21:38.185 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100799} Header: [count(1)]
10:21:38.185 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100799} Result: [53]
10:21:38.186 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100800} Connection
10:21:38.186 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100800} Preparing Statement:      update car     SET                                                         carstatus = ?                                                                                                     where id = ?
10:21:38.187 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100801} Executing Statement:      update car     SET                                                         carstatus = ?                                                                                                     where id = ?
10:21:38.187 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100801} Parameters: [1, fb4db237da604688aeb1f369b5bfd45e]
10:21:38.187 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100801} Types: [java.lang.Integer, java.lang.String]
10:21:38.191 [http-apr-8080-exec-6] INFO  com.incito.logistics.service.OrderService - 调用银联接口退款 orderId: 930aebeae7c845c88bb15f985f3cde83
10:21:38.191 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating in existing transaction
10:21:38.192 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100802} Connection
10:21:38.192 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100802} Preparing Statement:      SELECT * FROM ums_paymentorder WHERE BizId=?
10:21:38.192 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100803} Executing Statement:      SELECT * FROM ums_paymentorder WHERE BizId=?
10:21:38.192 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100803} Parameters: [930aebeae7c845c88bb15f985f3cde83]
10:21:38.192 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100803} Types: [java.lang.String]
10:21:38.197 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100804} ResultSet
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100804} Header: [OrderNoMer, SrcReqId, SrcReqDate, TxnType, OrderNo, PyrUserIdMer, PyrUserType, PyeUserIdMer, PyeUserType, PyrUserId, PyeUserId, OrderAmt, OrderStatus, STATUS, StatusDesc, BizId, BizType, BizDesc, PaymentChannel, Priority, HashCode, GenerateTime, UpdateTime, OrgBizId, DrawStatus, DrawTime]
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100804} Result: [DE15060800000000000001, null, 2015-06-08 10:17:48.0, 01, 201506081017323258568, fb4db237da604688aeb1f369b5bfd45e, 02, 36ff7818c242400db397075c87721db7, 01, null, null, 23500, 03, 00, Success!, 930aebeae7c845c88bb15f985f3cde83, 02, 付信息费-矿产, 02, 5, null, 2015-06-08 10:17:28.0, 2015-06-08 10:17:48.0, null, 0, null]
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100805} Connection
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100805} Preparing Statement:      SELECT * FROM ums_paymentorder WHERE BizId=?
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100806} Executing Statement:      SELECT * FROM ums_paymentorder WHERE BizId=?
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100806} Parameters: [DE15060800000000000001]
10:21:38.199 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100806} Types: [java.lang.String]
10:21:38.208 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100807} ResultSet
10:21:38.209 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Suspending current transaction
10:21:38.209 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating new transaction with name [com.incito.logistics.service.SeqService.getNo]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT; ''
10:21:38.214 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] for JDBC transaction
10:21:38.218 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] to manual commit
10:21:38.220 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100808} Connection
10:21:38.220 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100808} Preparing Statement:       SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?),?,0)) AS ordernum;
10:21:38.220 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100809} Executing Statement:       SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?),?,0)) AS ordernum;
10:21:38.220 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100809} Parameters: [CP, %y%m%d, chinapayorder, 14]
10:21:38.221 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100809} Types: [java.lang.String, java.lang.String, java.lang.String, java.lang.Integer]
10:21:38.228 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100810} ResultSet
10:21:38.229 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100810} Header: [ordernum]
10:21:38.229 [http-apr-8080-exec-6] DEBUG java.sql.ResultSet - {rset-100810} Result: [CP15060800000000000003]
10:21:38.229 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction commit
10:21:38.231 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Committing JDBC transaction on Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java]
10:21:38.238 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] after transaction
10:21:38.238 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
10:21:38.238 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction
10:21:38.238 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction
10:21:38.239 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100811} Connection
10:21:38.239 [http-apr-8080-exec-6] DEBUG java.sql.Connection - {conn-100811} Preparing Statement:      insert  into ums_paymentorder (       SrcReqId,       OrderNoMer,       OrderNo,       SrcReqDate,       TxnType,       PyrUserIdMer,       PyeUserIdMer,       PyrUserType,       PyeUserType,       PyrUserId,       PyeUserId,       OrderAmt,       STATUS,       StatusDesc,       BizId,       BizType,       BizDesc,       OrgBizId,       PaymentChannel,       OrderStatus,       Priority,       HashCode,       GenerateTime,       UpdateTime     )     value (       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       now(),now()     )
10:21:38.240 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100812} Executing Statement:      insert  into ums_paymentorder (       SrcReqId,       OrderNoMer,       OrderNo,       SrcReqDate,       TxnType,       PyrUserIdMer,       PyeUserIdMer,       PyrUserType,       PyeUserType,       PyrUserId,       PyeUserId,       OrderAmt,       STATUS,       StatusDesc,       BizId,       BizType,       BizDesc,       OrgBizId,       PaymentChannel,       OrderStatus,       Priority,       HashCode,       GenerateTime,       UpdateTime     )     value (       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       ?,       now(),now()     )
10:21:38.240 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100812} Parameters: [null, CP15060800000000000003, null, 2015-06-08 10:21:38.238, 04, 36ff7818c242400db397075c87721db7, fb4db237da604688aeb1f369b5bfd45e, 01, 02, null, null, 23500, null, 已发送, DE15060800000000000001, 04, 退信息费DE15060800000000000001, 930aebeae7c845c88bb15f985f3cde83, 02, 01, 5, null]
10:21:38.240 [http-apr-8080-exec-6] DEBUG java.sql.PreparedStatement - {pstm-100812} Types: [null, java.lang.String, null, java.sql.Timestamp, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, null, null, java.lang.Long, null, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Integer, null]
10:21:38.245 [http-apr-8080-exec-6] INFO  c.i.logistics.chinapay.ChinaPayOrderService - 创建退货订单 success, refundOrder: PaymentOrder{OrderNoMer='CP15060800000000000003', SrcReqId='null', SrcReqDate=Mon Jun 08 10:21:38 CST 2015, OrderNo='null', TxnType='04', OrderAmt=23500, OrderStatus='01', PyrUserIdMer='36ff7818c242400db397075c87721db7', PyeUserIdMer='fb4db237da604688aeb1f369b5bfd45e', PyrUserType='01', PyeUserType='02', PyrUserId='null', PyeUserId='null', Status='null', StatusDesc='已发送', BizId='DE15060800000000000001', BizType='04', BizDesc='退信息费DE15060800000000000001', Priority=5, HashCode='null', GenerateTime=null, UpdateTime=null, PaymentChannel='02'}
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - txnType-->04
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - frontUrl-->http://192.168.81.24:8080/web/chinapay/callback
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - channelType-->08
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - currencyCode-->156
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - merId-->777290058111285
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - txnSubType-->00
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - txnAmt-->23500
10:21:38.245 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - version-->5.0.0
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - signMethod-->01
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - backUrl-->http://58.51.36.100:60001/chinapay/callback
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - origQryId-->201506081017323258568
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - encoding-->UTF-8
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - bizType-->000201
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - orderId-->CP15060800000000000003
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - txnTime-->20150608102138
10:21:38.246 [http-apr-8080-exec-6] DEBUG c.i.logistics.chinapay.utils.ChinaPayUtil - accessType-->0
......
    at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:1852) [tomcat-coyote.jar:7.0.42]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_40]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_40]
    at java.lang.Thread.run(Thread.java:724) [na:1.7.0_40]
10:21:38.502 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating transaction failed - marking existing transaction as rollback-only
10:21:38.504 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Setting JDBC transaction [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] rollback-only
10:21:38.505 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction rollback
10:21:38.510 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Rolling back JDBC transaction on Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java]
10:21:38.523 [http-apr-8080-exec-6] DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoReconnect=true&useUnicode=true&characterEncoding=utf8, UserName=root@172.16.0.3, MySQL Connector Java] after transaction
10:21:38.523 [http-apr-8080-exec-6] DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
Caused by: java.lang.RuntimeException: test db exception ...
    at com.incito.logistics.service.ChinaPayOrderService.refund(ChinaPayOrderService.java:700) ~[logistic-server-0.0.1-SNAPSHOT.jar:na]
    ... 69 common frames omitted
10:21:38.530 [http-apr-8080-exec-6] DEBUG com.incito.logistics.common.SpecialCharFilter - process out /web/myorder/agreeRefund

可以看到，不管方法的注解是什么，select语句并不会打开事务。只有insert\update出现时，才Creating new transaction。之后调用其它service方法时都是参与到当前的事务中Participating in existing transaction。最后commit或rollback。
（NOT_SUPPORTED与REQUIRES_NEW的日志被提取了出去，后面会看到，而他们之外的事务处理流程都一样）
DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating new transaction with name
DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://。。。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://。。。]to manual commit
。。。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating in existing transaction
。。。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating transaction failed - marking existing transaction as rollback-only
DEBUG o.s.j.datasource.DataSourceTransactionManager - Setting JDBC transaction [jdbc:mysql://192.168。。。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction rollback
DEBUG o.s.j.datasource.DataSourceTransactionManager - Rolling back JDBC transaction on Connection [jdbc:mysql://19。。。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.1。。。
DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource

如果其中的一个方法中使用了PROPAGATION_NOT_SUPPORTED，那么上面的流程中会出现下面日志，进入方法前先挂起当前事务且创建新事务，在NOT_SUPPORTED方法范围内，每执行一次就要commit一次，退出方法时提交新事务且恢复被挂起的事务。从日志中可看出NOT_SUPPORTED的行为。如下：执行了两次查询SELECT orderno，每次执行完后都commit了。
DEBUG o.s.j.datasource.DataSourceTransactionManager - Suspending current transaction
DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating new transaction with name [com.incito.logistics.service.SeqSer
DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoRe
DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?
DEBUG java.sql.Connection - {conn-100158} Connection
DEBUG java.sql.Connection - {conn-100158} Preparing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?),
DEBUG java.sql.PreparedStatement - {pstm-100159} Executing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextva
DEBUG java.sql.PreparedStatement - {pstm-100159} Parameters: [CP, %y%m%d, chinapayorder, 14]
DEBUG java.sql.PreparedStatement - {pstm-100159} Types: [java.lang.String, java.lang.String, java.lang.String, java.lang.Inte
DEBUG java.sql.ResultSet - {rset-100160} ResultSet
DEBUG java.sql.ResultSet - {rset-100160} Header: [ordernum]
DEBUG java.sql.ResultSet - {rset-100160} Result: [CP15060800000000000006]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction commit
DEBUG o.s.j.datasource.DataSourceTransactionManager - Committing JDBC transaction on Connection [jdbc:mysql://192.168.11.140:
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?
DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction
DEBUG o.s.j.datasource.DataSourceTransactionManager - Creating new transaction with name [com.incito.logistics.service.SeqSer
DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoRe
DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?
DEBUG java.sql.Connection - {conn-100161} Connection
DEBUG java.sql.Connection - {conn-100161} Preparing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?),
DEBUG java.sql.PreparedStatement - {pstm-100162} Executing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextva
DEBUG java.sql.PreparedStatement - {pstm-100162} Parameters: [CP, %y%m%d, chinapayorder, 14]
DEBUG java.sql.PreparedStatement - {pstm-100162} Types: [java.lang.String, java.lang.String, java.lang.String, java.lang.Inte
DEBUG java.sql.ResultSet - {rset-100163} ResultSet
DEBUG java.sql.ResultSet - {rset-100163} Header: [ordernum]
DEBUG java.sql.ResultSet - {rset-100163} Result: [CP15060800000000000007]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction commit
DEBUG o.s.j.datasource.DataSourceTransactionManager - Committing JDBC transaction on Connection [jdbc:mysql://192.168.11.140:
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?
DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction
DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction

如果其中的一个方法中使用了PROPAGATION_REQUIRES_NEW，与NOT_SUPPORTED相比只有一点区别，就是REQUIRES_NEW只commit了一次。之后处理步骤就相同了Resuming suspended transaction。。。

DEBUG o.s.j.datasource.DataSourceTransactionManager - Suspending current transaction, creating new transaction with name [co
DEBUG o.s.j.datasource.DataSourceTransactionManager - Acquired Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev?autoR
DEBUG o.s.j.datasource.DataSourceTransactionManager - Switching JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev
DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating in existing transaction
DEBUG java.sql.Connection - {conn-100195} Connection
DEBUG java.sql.Connection - {conn-100195} Preparing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?)
DEBUG java.sql.PreparedStatement - {pstm-100196} Executing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextv
DEBUG java.sql.PreparedStatement - {pstm-100196} Parameters: [CP, %y%m%d, chinapayorder, 14]
DEBUG java.sql.PreparedStatement - {pstm-100196} Types: [java.lang.String, java.lang.String, java.lang.String, java.lang.Int
DEBUG java.sql.ResultSet - {rset-100197} ResultSet
DEBUG java.sql.ResultSet - {rset-100197} Header: [ordernum]
DEBUG java.sql.ResultSet - {rset-100197} Result: [CP15060800000000000010]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Participating in existing transaction
DEBUG java.sql.Connection - {conn-100198} Connection
DEBUG java.sql.Connection - {conn-100198} Preparing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextvalue(?)
DEBUG java.sql.PreparedStatement - {pstm-100199} Executing Statement: SELECT CONCAT(?,DATE_FORMAT(NOW(), ?),LPAD(nextv
DEBUG java.sql.PreparedStatement - {pstm-100199} Parameters: [CP, %y%m%d, chinapayorder, 14]
DEBUG java.sql.PreparedStatement - {pstm-100199} Types: [java.lang.String, java.lang.String, java.lang.String, java.lang.Int
DEBUG java.sql.ResultSet - {rset-100200} ResultSet
DEBUG java.sql.ResultSet - {rset-100200} Header: [ordernum]
DEBUG java.sql.ResultSet - {rset-100200} Result: [CP15060800000000000011]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction commit
DEBUG o.s.j.datasource.DataSourceTransactionManager - Committing JDBC transaction on Connection [jdbc:mysql://192.168.11.140
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://192.168.11.140:3306/smartdbdev
DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
DEBUG o.s.j.datasource.DataSourceTransactionManager - Resuming suspended transaction after completion of inner transaction

==============================================================================================
测试时，遇到了另外一种现象：
假设在同一个XXXService中，有下面两个方法：
@Transactional
method_One(){…method_Two()…}

@Transactional(propagation = Propagation.REQUIRES_NEW)
method_Two(){…}

问method_Two()会不会创建一个新事务？
答：不会创建。仔细查看了日志，没有找到类似creating new transaction的输出，应该是因为在同一个Service类中，spring并不重新创建新事务，如果是两不同的Service，就会创建新事务了。
那么为什么spring只对跨Service的方法才生效？
Debug代码发现跨Service调用方法时，都会经过org.springframework.aop.framework.CglibAopProxy.DynamicAdvisedInterceptor.intercept()方法，只有经过此处，才能对事务进行控制。
如果你要问此方法又是如何控制事务的？下次有机会再研究。。。嘿嘿

==============================================================================================

DEBUG o.s.j.datasource.DataSourceTransactionManager - Global transaction is marked as rollback-only but transactional code requested commit
DEBUG o.s.j.datasource.DataSourceTransactionManager - Initiating transaction rollback
DEBUG o.s.j.datasource.DataSourceTransactionManager - Rolling back JDBC transaction on Connection [jdbc:mysql://。。。, MySQL Connector Java]
DEBUG o.s.j.datasource.DataSourceTransactionManager - Releasing JDBC Connection [jdbc:mysql://。。。,  ] after transaction
DEBUG o.s.jdbc.datasource.DataSourceUtils - Returning JDBC Connection to DataSource
org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only

Propagation.REQUIRES_NEW 与 Propagation.REQUIRED 比较
method_XX(){
      //创建退货订单
      try {
        refundOrder.setOrderNoMer(seqService.nextOrderNo());//跨Service调用方法时
      } catch (Exception e) {//catch后不抛出
        refundOrder.setOrderNoMer("11111111111111112");//商户端订单号
        logger.info("catch后不抛出", e);
      }
}

跨Service调用方法时：
**如果被调用方法是Propagation.REQUIRES_NEW，被catch后不抛出，事务可以正常提交；
如果被调用方法是Propagation.REQUIRED，被catch后不抛出，后面的代码虽然可以执行下去，但最终还是会分出rollback-only异常：**Global transaction is marked as rollback-only but transactional code requested commit
如果是在同一个Service中调用方法时：
不论注解是REQUIRES_NEW还是REQUIRED，其结果都是一样的，就是都被忽略掉了，等于没写。当其抛出异常时，只需catch住不抛出，事务就可以正常提交。

==============================================================================================

chs_jdmdr
关注
  • 2
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
java 事物 notsupport_Spring事务传播属性介绍(二).mandatory、not_supported、never、supports...
weixin_33268205的博客
02-26 760
Required、Required_New传播属性分析传送门:https://www.cnblogs.com/lvbinbin2yujie/p/10259897.htmlNested传播属性分析传送门:https://www.cnblogs.com/lvbinbin2yujie/p/10260066.html我的Spring事务传播属性介绍比较传送门:https://files.cnblogs.c...
Spring事务处理
wy827349995的博客
03-07 222
@Transactional 上一章节我们提到了Spring的AOP，其中所举的例子就是数据库事务处理。原本的数据库事务操作是繁杂而充斥冗余的，但Spring为我们引入了“切面”的思想，从而分离了变与不变的部分。 当然，像上一节那样自己定义一个MyAspect仍然显得不够简洁，为此，Spring提供了一个注解@Transactional。你只需要在service类的业务方法上增加该注解，Sprin...
Spring框架+Spring中的事务
03-22
什么是Spring事务传播机制 Spring事务传播机制是指在多个事务操作发生时，如何管理这些操作之间的事务关系。Spring事务传播机制可以通过Propagation枚举类中的不同值来指定，共包括七种不同的传播行为。具体来说，Spring事务传播机制包括以下七种： REQUIRED：如果当前没有事务，则创建一个新的事务；如果当前已经存在事务，则加入该事务。这是默认的传播行为。 SUPPORTS：如果当前存在事务，则加入该事务；如果当前没有事务，则以非事务的方式执行。 MANDATORY：必须在一个已存在的事务中执行，否则就抛出TransactionRequiredException异常。 REQUIRES_NEW：创建一个新的事务，并在该事务中执行；如果当前存在事务，则将当前事务挂起。 NOT_SUPPORTED：以非事务方式执行操作，如果当前存在事务，则将当前事务挂起。 NEVER：以非事务方式执行操作，如果当前存在事务，则抛出IllegalTransactionStateException异常。NESTED：如果当前存在事务，则在嵌套事务中执行；如果当前没有事务，则创建一个新事务
New-Microsoft-Office-Word-Document.zip_The Word
07-15
its lms1 algorithm.very useful to calculate end points in the leaning curves and also requires less no.of iterations.
Spring异常捕获且回滚事务解决方案
08-19
主要介绍了Spring异常捕获且回滚事务解决方案,文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值,需要的朋友可以参考下
Spring 事务
weixin_43612949的博客
04-14 668
1.数据库是否为InnoDB引擎，具体原因请查看 Mysql引擎类型刨析 2.配置文件中是否开启 transaction: rollback-on-commit-failure: true 3.是否在启动类中加入注解（此项可忽略，spring boot 默认开启了事务） @EnableTransactionManagement 4.@Transactional注解位置： @Transactiona...
Spring Transactional事务不生效的场景
叶子的博客
11-22 1461
1、未启用事务功能 2、事务传播类型为 NOT_SUPPORTED 3、在非事务方法中调用事务方法 4、进行了 try catch 异常捕获，并未抛出异常 5、调用类方法（static 修饰的方法）
spring事务传播行为中的REQUIRED_NEW
m0_70794624的博客
03-14 1362
运行到methodA()这行的时候会挂起当前事务，然后重新创建一个事务，在methodA()中没有发生异常的情况下，运行完methodA方法直接提交methodA的事务；后续再执行dosomgthingAfter。通常我们只会用到@Transactional默认是REQUIRED在特殊需求的时候需要在一个方法内部提前提交一部分事务或者是让内部的一段代码处于单独的一个事务管理的时候需要用到REQUIRES_NEW。
我总结的几种@Transactional失效原因
热门推荐
滕青山博客
05-18 11万+
非public方法： spring事务是通过动态代理的方法来实现的，有两种实现动态代理的方式，jdk动态代理方式是将目标对象放入代理对象内部，通过代理对象来访问目标对象；cglib字节码生成是通过生成目标对象的子类，通过重写的方式来完成对父类的增强。 但是它俩实际上可以为非public方法生成代理对象，只不过spring在调用动态代理之前，会过滤掉非public方法。如果修改spring的源码就可以为非public方法生成代理对象了。 自调用问题： 若同一类中的没有@Transactional注解的方法内部
spring 事务传播REQUIRED 与 NESTED的区别
FREEDOM
05-12 4418
NESTED 似乎与REQUIRED 是一样的，但是他们是不同的。 若 关于spring事务传播机制的解释 播行为 意义 PROPAGATION_REQUIRES 表示当前方法必须在一个事务中运行。如果一个现有事务正在进行中，该方法将在那个事务中运行，否则就要开始一个新事务。 PROPAGATION_SUPPORTS 表示当前方法不需要事务性上下文，但是如果有一个事务已经在运行的话，它也可以在这个事务里运行。 PROPAGATION_MANDATORY ...
Pytorch训练过程中改变模型参数 requires_grad 属性
01-20
如果模型只在一块GPU上跑，该过程非常简单，只需要训练中途迭代model的 parameters，然后改变各个param的requires_grad 属性即可： for name, param in model.named_parameters(): logger.info('parameter of %s'...
Spring 事务配置的五种方式.docx
06-19
PROPAGATION_REQUIRES_NEW--新建事务，如果当前存在事务，把当前事务挂起。 PROPAGATION_NOT_SUPPORTED--以非事务方式执行操作，如果当前存在事务，就把当前事务挂起。 PROPAGATION_NEVER--以非事务方式执行，如果...
@Transactional事务注解
m0_58680865的博客
04-26 4490
一、事务注解使用的位置 1、用于类的上方 表示这个类中的所有方法都进行事务处理 当类中的某个方法不需要事务处理时，可以在这个方法上添加： @Transactional(propagation =Propagation.NOT_SUPPORTED) 例如： @Transactional public class AServiceImplements AService { public void m1() { } @Transactional(pr
Spring @Transactional （一）
iteye_9815的博客
11-26 625
Spring事务的传播行为 在service类前加上@Transactional，声明这个service所有方法需要事务管理。每一个业务方法开始时都会打开一个事务。 Spring默认情况下会对运行期例外(RunTimeException)进行事务回滚。这个例外是unchecked 如果遇到checked意外就不回滚。 如何改变默认规则： 1 让checked例...
【Spring】@Transactional常用参数使用示例、以及常见的一些坑
superKusch的博客
08-03 2488
当spring隔离级别和数据库隔离级别不一样时，spring的优先。
Spring事务@Transactional(rollbackFor = Exception.class) 不生效
riemann_的博客
01-07 1万+
一、发现问题 项目中写了一个关务事务的方法，然后发现不生效。然后我做了下面的一个测试看看到底哪里出了问题！ 这是我的简化后的测试代码，上面有个insert操作数据库的插入方法，下面我就直接抛个异常，省得写测试操作数据库不成功的另一个方法。我们都知道事务是作为一个整体来执行，包含在其中的对数据库的操作要么全部执行，要么都不执行。所以我下面来演示一个成功插入，另一个报错的情况。这种情况加了事务只要有一...
spring的propogation(传播机制)
ForestCat的专栏
08-24 1242
pring的propagation，表示打算对这些方法怎么使用事务，是用还是不用. propagation有七种配置.  REQUIRED：支持当前事务，如果当前没有事务，就新建一个事务。这是最常见的选择。  SUPPORTS：支持当前事务，如果当前没有事务，就以非事务方式执行。  MANDATORY：支持当前事务，如果当前没有事务，就抛出异常。  REQUIRES_NEW：新建事务，如果
jdbc管理事务
weixin_45701447的博客
09-16 279
JDBC控制事务 事务: 一个包含多个步骤的业务操作。如果这个业务操作被事务管理，那么这些操作要么同时成功要么同时失败 操作 1。开启事务 2.提交事务 3.回滚事务 使用Connection 对象来管理事务 开启事务 : setAutCommit(boolean autoCommit):调用该方法 设置参数为false ，即开启事务 在操作之前开启事务 例:conn.setAutCommit(boolean autoCommit) 提交事务: commit() conn.commit() 回滚事务： ro
0017音乐播放器(1)AdobeXD源码下载设计素材UI设计.xd
最新发布
04-23
0017音乐播放器(1)AdobeXD源码下载设计素材UI设计
Spring事务与事务传播机制
09-13
Spring事务是Spring框架提供的一种用于管理数据库事务的机制。它可以确保在一组数据库操作中，要么全部成功提交，要么全部失败回滚。 事务传播机制是指在一个方法调用另一个方法时，如何处理事务的传播行为。Spring框架提供了多种事务传播行为选项，包括： 1. REQUIRED：如果当前存在事务，则加入到当前事务中；如果当前没有事务，则创建一个新的事务。 2. SUPPORTS：如果当前存在事务，则加入到当前事务中；如果当前没有事务，则以非事务方式执行。 3. MANDATORY：如果当前存在事务，则加入到当前事务中；如果当前没有事务，则抛出异常。 4. REQUIRES_NEW：创建一个新的事务，并挂起当前事务（如果存在）。 5. NOT_SUPPORTED：以非事务方式执行操作，如果当前存在事务，则挂起该事务。 6. NEVER：以非事务方式执行操作，如果当前存在事务，则抛出异常。 7. NESTED：如果当前存在事务，则在嵌套事务内执行；如果当前没有事务，则创建一个新的事务。 通过使用适当的事务传播机制，可以灵活地控制方法调用之间的事务行为，以满足应用程序的需求。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值