Java死锁情况下打印日志,是先打印了死锁的警告然后输出Neo4j的日志，能否帮忙分析一下是什么原因导致的？...

最新推荐文章于 2022-03-09 17:42:06 发布
最新推荐文章于 2022-03-09 17:42:06 发布
阅读量351 收藏 1
点赞数
文章标签： Java死锁情况下打印日志

分布式程序更新图，客户端使用CYPHER更新图，使用了Neo4j驱动，用C3p0做了连接池，当我启动一个Server和多个Client更新图的时候爆java.nio.channels.ClosedChannelException

备注：启动了一个server，五个client，测试时四个client挂掉了爆的错一样，只有一个client是看起来正常的

爆出这个错误，是先打印了死锁的警告然后输出Neo4j的日志，能否帮忙分析一下是什么原因导致的？

2018-08-18 10:39:59[com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector.run(ThreadPoolAsynchronousRunner.java:807)] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@23468307 -- APPARENT DEADLOCK!!! Complete Status:

Managed Threads: 3

Active Threads: 3

Active Tasks:

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@245dbd09

on thread: C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#2

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@5655278d

on thread: C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#1

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@7bf16972

on thread: C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#0

Pending Tasks:

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@820b78a

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@75312c94

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@1dbf727a

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@2dd4a7a9

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@75566f4

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@3777fc44

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@23909b3

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@628aea61

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@6dd1f239

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@47400608

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@5857d723

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@109188b4

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@2cfd9b0a

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@752180c4

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@24ac87a

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@215404a1

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@6265a548

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@489b7559

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@39a09c0

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@34f32575

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@3ace65df

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@2c7aba7c

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@1185b0b7

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@404566e7

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@b0c4905

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@4a9f0360

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@240f712e

Pool thread stack traces:

Thread[C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#2,5,main]

sun.misc.Unsafe.park(Native Method)

java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)

java.util.concurrent.FutureTask.get(FutureTask.java:191)

org.neo4j.jdbc.utils.TimeLimitedCodeBlock.runWithTimeout(TimeLimitedCodeBlock.java:48)

org.neo4j.jdbc.bolt.impl.BoltNeo4jConnectionImpl.isValid(BoltNeo4jConnectionImpl.java:250)

sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:483)

org.neo4j.jdbc.utils.Neo4jInvocationHandler.invoke(Neo4jInvocationHandler.java:54)

com.sun.proxy.$Proxy3.isValid(Unknown Source)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)

com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)

com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckin(C3P0PooledConnectionPool.java:404)

com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckin(BasicResourcePool.java:1760)

com.mchange.v2.resourcepool.BasicResourcePool.access$200(BasicResourcePool.java:44)

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask.run(BasicResourcePool.java:1378)

com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

Thread[C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#0,5,main]

sun.misc.Unsafe.park(Native Method)

java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)

java.util.concurrent.FutureTask.get(FutureTask.java:191)

org.neo4j.jdbc.utils.TimeLimitedCodeBlock.runWithTimeout(TimeLimitedCodeBlock.java:48)

org.neo4j.jdbc.bolt.impl.BoltNeo4jConnectionImpl.isValid(BoltNeo4jConnectionImpl.java:250)

sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:483)

org.neo4j.jdbc.utils.Neo4jInvocationHandler.invoke(Neo4jInvocationHandler.java:54)

com.sun.proxy.$Proxy3.isValid(Unknown Source)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)

com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)

com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckin(C3P0PooledConnectionPool.java:404)

com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckin(BasicResourcePool.java:1760)

com.mchange.v2.resourcepool.BasicResourcePool.access$200(BasicResourcePool.java:44)

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask.run(BasicResourcePool.java:1378)

com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

Thread[C3P0PooledConnectionPoolManager[identityToken->2rvzm09xks5pppxp14t3|79698539]-HelperThread-#1,5,main]

sun.misc.Unsafe.park(Native Method)

java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)

java.util.concurrent.FutureTask.get(FutureTask.java:191)

org.neo4j.jdbc.utils.TimeLimitedCodeBlock.runWithTimeout(TimeLimitedCodeBlock.java:48)

org.neo4j.jdbc.bolt.impl.BoltNeo4jConnectionImpl.isValid(BoltNeo4jConnectionImpl.java:250)

sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

java.lang.reflect.Method.invoke(Method.java:483)

org.neo4j.jdbc.utils.Neo4jInvocationHandler.invoke(Neo4jInvocationHandler.java:54)

com.sun.proxy.$Proxy3.isValid(Unknown Source)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)

com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)

com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)

com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.finerLoggingTestPooledConnection(C3P0PooledConnectionPool.java:452)

com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckin(C3P0PooledConnectionPool.java:404)

com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckin(BasicResourcePool.java:1760)

com.mchange.v2.resourcepool.BasicResourcePool.access$200(BasicResourcePool.java:44)

com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask.run(BasicResourcePool.java:1378)

com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

2018-08-18 10:40:59[com.mchange.v2.async.ThreadPoolAsynchronousRunner.processReplacedThreads(ThreadPoolAsynchronousRunner.java:555)] Task com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@245dbd09 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().

2018-08-18 10:40:59[com.mchange.v2.async.ThreadPoolAsynchronousRunner.processReplacedThreads(ThreadPoolAsynchronousRunner.java:555)] Task com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@7bf16972 (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().

2018-08-18 10:40:59[com.mchange.v2.async.ThreadPoolAsynchronousRunner.processReplacedThreads(ThreadPoolAsynchronousRunner.java:555)] Task com.mchange.v2.resourcepool.BasicResourcePool$1RefurbishCheckinResourceTask@5655278d (in deadlocked PoolThread) failed to complete in maximum time 60000ms. Trying interrupt().

八月 18, 2018 10:40:59 上午 org.neo4j.driver.internal.logging.JULogger error

严重: [727298531] TLS socket could not be closed cleanly

java.nio.channels.ClosedChannelException

at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:269)

at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:460)

at org.neo4j.driver.internal.security.TLSSocketChannel.channelWrite(TLSSocketChannel.java:193)

at org.neo4j.driver.internal.security.TLSSocketChannel.close(TLSSocketChannel.java:481)

at org.neo4j.driver.internal.net.SocketClient.stop(SocketClient.java:212)

at org.neo4j.driver.internal.net.SocketConnection.close(SocketConnection.java:265)

at org.neo4j.driver.internal.net.ConcurrencyGuardingConnection.close(ConcurrencyGuardingConnection.java:178)

at org.neo4j.driver.internal.net.pooling.PooledSocketConnection.dispose(PooledSocketConnection.java:251)

at org.neo4j.driver.internal.net.pooling.BlockingPooledConnectionQueue.disposeSafely(BlockingPooledConnectionQueue.java:167)

at org.neo4j.driver.internal.net.pooling.BlockingPooledConnectionQueue.disposeBroken(BlockingPooledConnectionQueue.java:120)

at org.neo4j.driver.internal.net.pooling.PooledConnectionReleaseConsumer.accept(PooledConnectionReleaseConsumer.java:50)

at org.neo4j.driver.internal.net.pooling.PooledConnectionReleaseConsumer.accept(PooledConnectionReleaseConsumer.java:29)

at org.neo4j.driver.internal.net.pooling.PooledSocketConnection.close(PooledSocketConnection.java:200)

at org.neo4j.driver.internal.NetworkSession.closeCurrentConnection(NetworkSession.java:375)

at org.neo4j.driver.internal.NetworkSession.syncAndCloseCurrentConnection(NetworkSession.java:349)

at org.neo4j.driver.internal.NetworkSession.close(NetworkSession.java:169)

at org.neo4j.jdbc.bolt.impl.BoltNeo4jConnectionImpl.close(BoltNeo4jConnectionImpl.java:214)

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:483)

at org.neo4j.jdbc.utils.Neo4jInvocationHandler.invoke(Neo4jInvocationHandler.java:54)

at com.sun.proxy.$Proxy3.close(Unknown Source)

at com.mchange.v2.c3p0.impl.NewPooledConnection.close(NewPooledConnection.java:642)

at com.mchange.v2.c3p0.impl.NewPooledConnection.closeMaybeCheckedOut(NewPooledConnection.java:255)

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.destroyResource(C3P0PooledConnectionPool.java:622)

at com.mchange.v2.resourcepool.BasicResourcePool$1DestroyResourceTask.run(BasicResourcePool.java:1076)

at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:696)

f36d49dcdd5c03bd8acea06479703f9e.png

是小谷吗
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Java死锁情况下打印日志_数据库死锁和慢日志问题导致服务不可用的排查过程...
weixin_35997054的博客
03-01 516
数据库执行更新失败，查看日志首先是根据报的Exception进行排查：org.hibernate.exception.LockAcquisitionException: could not execute statement很明显，是数据库死锁，导致不能执行我的更新sql。思路一：查找并杀死死锁的进程查看进程show OPEN TABLES where In_use > 0;SHOW PRO...
(实战篇)Java服务线上死锁日志怎么看?
丶Joy丶的博客
11-13 757
前言 别嫌弃日志篇幅长哈, 只要是想让看到的同学可以完整的感受到死锁的排查过程. 一、死锁栈日志信息 Found one Java-level deadlock: ============================= "pool-1-thread-5": waiting to lock monitor 0x00007efa20010788 (object 0x00000005f78000...
记录一次真实的Java服务死锁问题
weixin_39919140的博客
03-09 496
项目启动死锁问题的排查和解决
Java死锁情况下打印日志_通过JVM日志分析排查Java线程死锁
weixin_35992471的博客
03-01 736
通过JVM日志分析排查Java线程死锁两种办法：使用jstack 命令和jconsole工具1. jstack(1) 首先通过 jps 命令查看需要查看运行的Java进程列表，得到想查看的进程的id。(2)执行: jstack -l ：得到一些log，可以看到获取，释放，等待锁等log情况2. 使用jconsole: 命令行直接jconsole打开jconsole，这是个可视化的工具，可以查看：概...
java死锁打印进程信息分析
神奇的木木的博客
11-24 347
public class DeadLockTest { private static Object A = new Object(), B = new Object(); public static void main(String[] args) { new Thread(() -> { System.out.println("线程1开始执行..."); synchronized (A)
Neo4j_v1.2用户手册
03-09
- **死锁**：分析了死锁发生的原因及其解决方案。 - **删除语义**：说明了 Neo4j 中删除节点或关系的具体行为。 ##### 4. Neo4j Server - **安装**：指导用户如何安装并配置 Neo4j Server。 - **配置**：提供了 ...
数据库实战大全，你想要的都能找到全套源码提供
05-22
数据库是信息技术领域中不可或缺的一部分，它负责存储、管理和检索数据，是支撑各类应用程序运行的基础。在本套资源“数据库实战大全”中，你将获得一套完整的源码，这对于学习、研究或开发数据库相关项目非常有帮助...
database-journal：数据库：概念，命令，代码，面试问题等等。
02-05
Elasticsearch是一种实时的分布式搜索和分析引擎，常用于日志分析和全文检索。 Kafka是一个高吞吐量的消息中间件，适合构建实时数据管道和流处理应用。MongoDB是面向文档的NoSQL数据库，支持JSON格式的数据存储，...
并发控制：数据库的守护神
最新发布
07-17
在这种情况下，多个用户可能尝试同时修改相同的数据，如果没有适当的控制机制，会导致数据不一致甚至损坏。因此，**并发控制**成为了数据库设计和实现的关键因素之一。 #### 并发控制简介 并发控制是一种机制，它...
数据库原理课件
01-08
并发控制处理多个用户同时访问数据库时可能出现的问题，如死锁和数据不一致。 7. 数据库备份与恢复： 学习如何备份数据库以防止数据丢失，并理解不同的恢复策略，如简单恢复、完全恢复和大容量日志记录恢复。 8. ...
发生死锁的线程dump日志
fangleijiang的专栏
01-03 1403
2018-01-03 19:38:30 Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode): "RMI TCP Connection(2)-10.100.227.115" daemon prio=6 tid=0x000000000d4e6000 nid=0x29c0 runnable [0x
死锁与挂起程序jstack打印日志
m0_47360218的博客
04-16 495
死锁程序1 package com.demo; public class DeadLock implements Runnable{ private static final Object o1= new Object(); private static final String o2 = new String("ss"); private int flag = 0; public DeadLock setFlag(int flag) { thi
java ibatis 锁表,记一次死锁问题
weixin_29809497的博客
03-13 362
背景：前系统跑定时任务，由于是循环插入、查询、修改同时存在，其中一个log表中数据存在500多万，做了修改操作，但是并没有做索引，通过执行计划查看为全表操作。从而造成死锁。日志: (Deadlock found when trying to get lock; try restarting transaction)2020-10-14 16:05:26 [ myScheduler-5:65588...
neo4j启动时，日志报错：Address xx.xx.xx.xxx:7687 is already in use, cannot bind to it.
benpaodexiaowoniu的博客
09-12 2769
总结：neo4j.conf中bolt监听地址由阿里云服务器的“公网ip”改为“内网ip”或0.0.0.0 背景：接阿里对阿里云服务器进行升级的通知，对阿里云服务器进行迁移。在重启neo4j时，无论是使用默认7687端口，还是随意改一个提前验证绝对不曾使用的端口，均报错如下： 问题有两个： 无论什么端口，均报被占用。 日志显示的时间既不是系统时间，也不是硬件时间 首先针对“时间”问题，做如...
java日志丢失故障处理导致的死锁问题
u013995172的专栏
03-02 1617
从报表A中发现数据丢失，然后找到程序运行的日志，发现日志只有一小部分，平常12G，今天只有243M 但是报表B中发现程序运行完毕。因此可以推断程序在运行，但是日志丢失了。   根据proc文件系统来找相关的信息 发现几个log文件 打开文件发现确实是今天丢失的文件，Tail –f一下文件发现，有一个线程一直在等待 说明文件中的线程发生了死
synchronized实现死锁，并使用jstack查看日志分析死锁产生原因
qq_37977055的博客
10-14 311
死锁产生的条件 简单来说，A线程持有m对象锁，想要获得n对象锁，B线程持有n对象锁，想要获得m对象锁。（因为n对象锁已经被B线程持有了，所以A线程获取不到，程序执行不下去，自己的m对象锁也无法释放，同理m对象锁也是如此） synchronized 实现个死锁 public class MyLock2 { public static void main(String[] args) { //自己随便创建个对象..... Person p1 = new Person();
什么是死锁？产生死锁的原因和必要条件是什么？如何预防死锁？
03-31
死锁是指两个或多个进程（线程）在执行过程中，因争夺资源而造成的一种互相等待的现象，导致进程（线程）无法继续执行。 产生死锁的原因和必要条件： 1. 互斥：资源不能被同时访问，只能被一个进程使用。 2. 占有和...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值