springboot问题之 The Tomcat connector configured to listen on port 33333 failed to start. The port may

最新推荐文章于 2023-07-18 17:07:50 发布
最新推荐文章于 2023-07-18 17:07:50 发布
阅读量525 收藏
点赞数
分类专栏： spring-boot spring-cloud
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u014636209/article/details/116206926
版权

1.问题描述

[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.463 ERROR 22440 [main] org.apache.catalina.util.LifecycleBase Failed to start component [Connector[HTTP/1.1-33333]]


org.apache.catalina.LifecycleException: Protocol handler start failed
at org.apache.catalina.connector.Connector.startInternal(Connector.java:1008)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.core.StandardService.addConnector(StandardService.java:226)
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.addPreviouslyRemovedConnectors(TomcatWebServer.java:259)
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.start(TomcatWebServer.java:197)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.startWebServer(ServletWebServerApplicationContext.java:311)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:164)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
at org.springframework.boot.actuate.autoconfigure.web.server.ManagementContextAutoConfiguration$DifferentManagementContextConfiguration.onApplicationEvent(ManagementContextAutoConfiguration.java:143)
at org.springframework.boot.actuate.autoconfigure.web.server.ManagementContextAutoConfiguration$DifferentManagementContextConfiguration.onApplicationEvent(ManagementContextAutoConfiguration.java:116)
at org.springframework.boot.actuate.autoconfigure.web.server.ManagementContextAutoConfiguration$DifferentManagementContextConfiguration$$EnhancerBySpringCGLIB$$81bf3d37.onApplicationEvent(<generated>)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:402)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:359)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:166)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248)
at com.haiercash.marketcontrol.core.CoreApplication.main(CoreApplication.java:21)
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:497)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:437)
at sun.nio.ch.Net.bind(Net.java:429)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:239)
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:213)
at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1116)
at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:1202)
at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:568)
at org.apache.catalina.connector.Connector.startInternal(Connector.java:1005)
... 33 common frames omitted


[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.470 INFO 22440 [main] org.apache.catalina.core.StandardService Stopping service [Tomcat]
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.485 INFO 22440 [main] org.apache.catalina.core.StandardService Stopping service [Tomcat]
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.490 WARN 22440 [main] org.apache.catalina.loader.WebappClassLoaderBase The web application [ROOT] appears to have started a thread named [lettuce-eventExecutorLoop-1-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
 java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467)
 io.netty.util.concurrent.SingleThreadEventExecutor.takeTask(SingleThreadEventExecutor.java:252)
 io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:64)
 io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:906)
 io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
 io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
 java.lang.Thread.run(Thread.java:745)
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.491 WARN 22440 [main] org.apache.catalina.loader.WebappClassLoaderBase The web application [ROOT] appears to have started a thread named [Druid-ConnectionPool-Create-975521494] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 com.alibaba.druid.pool.DruidDataSource$CreateConnectionThread.run(DruidDataSource.java:2443)
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.492 WARN 22440 [main] org.apache.catalina.loader.WebappClassLoaderBase The web application [ROOT] appears to have started a thread named [Druid-ConnectionPool-Destroy-975521494] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Thread.sleep(Native Method)
 com.alibaba.druid.pool.DruidDataSource$DestroyConnectionThread.run(DruidDataSource.java:2540)
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.494 WARN 22440 [main] org.apache.catalina.loader.WebappClassLoaderBase The web application [ROOT] appears to have started a thread named [spring.cloud.inetutils] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
 java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1067)
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 java.lang.Thread.run(Thread.java:745)
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.513 INFO 22440 [main] org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener 


Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.514 INFO 22440 [main] org.springframework.cloud.netflix.eureka.serviceregistry.EurekaServiceRegistry Unregistering application MAKETCONTROL-CORE with eureka with status DOWN
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.515 WARN 22440 [main] com.netflix.discovery.DiscoveryClient Saw local status change event StatusChangeEvent [timestamp=1619517220515, current=DOWN, previous=UP]
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.515 INFO 22440 [DiscoveryClient-InstanceInfoReplicator-0] com.netflix.discovery.DiscoveryClient DiscoveryClient_MAKETCONTROL-CORE/maketcontrol-core@10.164.194.116:9001(qd02.haiercash): registering service...
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.520 INFO 22440 [DiscoveryClient-InstanceInfoReplicator-0] com.netflix.discovery.DiscoveryClient DiscoveryClient_MAKETCONTROL-CORE/maketcontrol-core@10.164.194.116:9001(qd02.haiercash) - registration status: 204
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.532 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Waiting for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.890 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Successfully waited for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:40.892 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Waiting for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.891 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Successfully waited for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.894 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Waiting for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.896 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Successfully waited for workers to finish.
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.907 INFO 22440 [main] org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor Shutting down ExecutorService 'applicationTaskExecutor'
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.918 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Shutdown ignored - container is not active already
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.918 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Shutdown ignored - container is not active already
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.918 INFO 22440 [main] org.springframework.amqp.rabbit.listener.SimpleMessageListenerContainer Shutdown ignored - container is not active already
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.929 INFO 22440 [main] com.alibaba.druid.pool.DruidDataSource {dataSource-1} closed
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:41.987 INFO 22440 [main] com.netflix.discovery.DiscoveryClient Shutting down DiscoveryClient ...
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:44.989 INFO 22440 [main] com.netflix.discovery.DiscoveryClient Unregistering ...
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:44.989 WARN 22440 [DiscoveryClient-0] com.netflix.discovery.TimedSupervisorTask task supervisor shutting down, can't accept the task
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:44.998 INFO 22440 [main] com.netflix.discovery.DiscoveryClient DiscoveryClient_MAKETCONTROL-CORE/maketcontrol-core@10.164.194.116:9001(qd02.haiercash) - deregister  status: 200
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:45.004 INFO 22440 [main] com.netflix.discovery.DiscoveryClient Completed shut down of DiscoveryClient
[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:45.011 ERROR 22440 [main] org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter 


***************************
APPLICATION FAILED TO START
***************************


Description:


The Tomcat connector configured to listen on port 33333 failed to start. The port may already be in use or the connector may be misconfigured.


Action:


Verify the connector's configuration, identify and stop any process that's listening on port 33333, or configure this application to listen on another port.


[APP_IS_UNDEFINED:10.164.194.116:0000] [,,,] 2021-04-27 17:53:45.015 INFO 22440 [Thread-9] com.netflix.niws.loadbalancer.EurekaNotificationServerListUpdater Shutting down the Executor for EurekaNotificationServerListUpdater

在这里插入图片描述

在这里插入图片描述

2.解决方案

1.端口被其他的应用使用了 重新定义即可

在这里插入图片描述

东山富哥
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
Redis ‘MISCONF Redis is configured to save RDB snapshots, but is currently not able to …’持久化问题
01-09
Redis遇到了报错：MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for ...
AT91SAM7A3-EK.rar_AT91SAM7A3_ATMEL flash_On The Run_ice FLASH_sa
09-21
SAM7A3 RAM - ULINK: configured to run from on-chip RAM, using ULINK (may be used for target debugging) SAM7A3 Flash - SAMICE: configured for on-chip Flash ROM, using SAM-ICE (used for production ...
端口号被占用：The Tomcat connector configured to listen on port “端口号“ failed to start.
weixin_43785732的博客
11-17 5423
打开cmd命令窗口 输入如下指令查看所有端口和PID netstat -ano 找到对应的端口对应的PID ，杀掉该进程 再次启动就OK taskkill /F /pid PID
springcloud eureka启动报错
chenzhouwa4173的博客
06-27 250
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to process import candidates for configuration class [com.itumch.cloud.Eurek...
报错：The Tomcat connector configured to listen on port xxxx failed to start. The port may already be
weixin_47010136的博客
07-18 5286
原因： 当遇到 The port may already be in use or the connector my be misconfigured.这个错误时，居多是因为上一次项目正在启动时，由于其他非正常原因导致服务宕机等现象。当出现"成功"字样时，代表杀死进程成功！或者：win+r 输入cmd，快捷启动。2.杀死"xxxx"端口号的进程。
SpringBoot导出war包在tomcat下启动报错
Stormer的博客
06-08 2122
我照着Spring官网的教程把我的项目导出成war包，放到tomcat下部署，启动的时候报错java.lang.ClassNotFoundException: org.springframework.boot.web.embedded.tomcat.TomcatEmbeddedWebappClassLoader at java.net.URLClassLoader.findClass(URLCla...
【tomcat 端口占用启动失败】The Tomcat connector configured to listen on port xx failed to start
qq_28331393的博客
09-30 1998
【tomcat 启动报错】The Tomcat connector configured to listen on port 80failed to start问题解决 1.打开cmd 在CMD中输入命令：netstat -ano（注：以管理员的身份打开cmd） 2.在cmd中找到你启动的端口号，并记住端口号后面的PID 3.照样以管理员身份打开cmd,CMD中输入命令：taskkill /f /t /im 【PID】 ...
TIM_EncoderMode.rar_On The Edge
09-24
This example shows how to configure the TIM peripheral to interface with a encoder sensor. The TIM3 is configured in encoder mode1: Counter counts up/down on TI2 rising edge depending on TI1 level
jakarta-tomcat-catalina.rar_The Bat
09-23
This temp directory is used by the JVM for temporary file storage. The JVM is configured to use this as its java.io.tmpdir in the catalina.sh and catalina.bat scripts.
DMA.rar_The Show_dma_dma flash ram_pending_ram dma
09-23
The dedicated DMA channel is configured to transfer once a time a 32 word data buffer stored as constant in the Flash memory to another buffer in the RAM memory. The received data are stored in the ...
Spring Boot启动报错: The Tomcat connector configured to listen on port xxx failed to start 解决办法
story7的随记
07-03 714
我的端口配置在了8099 因此 控制台输入: netstat -ano |findstr 8099 找到占用8099端口的所有进程。因此 控制台输入: taskkill -PID 4560 -F 杀死端口4560的进程 -F是为了强制关闭。发现4560端口的程序正在占用我的8099端口。报错信息提示端口连接不上, 应该是被占用了。
SpringBoot运行报错“The Tomcat connector configured to listen on port 80 failed to start.“
二木成林
06-13 1万+
异常 运行启动SpringBoot项目报错： Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled. 2021-06-13 22:47:32.704 ERROR 79648 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *****
The Tomcat connector configured to listen on port 10000 failed to start. The port may already be in
weixin_42188778的博客
08-13 2312
今天周末在家，启动自己写的一个电商项目，发现一个端口被占用了，记录下来 The Tomcat connector configured to listen on port 10000 failed to start. The port may already be in
The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in
weixin_40964170的博客
07-22 2021
报错如下，可知端口被占用 二、解决方法 1、查询被占用端口号对应的tcp号 正在占用的端口号：netstat -ano|findstr 30000，此时会显示端口8081对应的tcp号 2、杀死进程 输入命令 taskkill /f /t /im 5680，终止了8081端口的运行进程 ...
解决问题 The Tomcat connector configured to listen on port 8080 failed to start.
热门推荐
有天你会让我妒忌的.
06-26 21万+
在学习SpringBoot过程中, 遇到了各种问题..错误过程:org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-8080]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:16...
The Tomcat connector configured to listen on port 8081 failed to start. The port may already be in u
weixin_43313277的博客
05-19 2028
idea运行时遇到问题： 字面意思，Tomcat在8081端口启动失败，8081这个端口已经被其他进程使用了，或者遇到了其他连接的问题。 方法一 重启电脑。关机后进程会被杀掉，再启动idea就不会出现被占用的情况。 方法二 命令行杀掉进程。这种方式在自己不能确定是什么进程在运行时，不建议使用。 使用管理员的身份打开命令行 使用命令查询端口号。这里可以看到，对应的值为14484 netstat -aon|findstr "8081" 杀掉进程 taskkill /T /F /PID "14484"
The Tomcat connector configured to listen on port 8082 failed to start.启动web项目报错
weixin_45150516的博客
03-06 1287
8082端口被占用 用IDEA连tomcat做web，特意换了8082接口，之前都好好的，这次突然打不开了。显示The Tomcat connector configured to listen on port 8082 failed to start. 解决方案 1.用管理员身份打开cmd，输入netstat -ano 2.找到本地地址最后显示的端口8082对应的PID 再输入 taskkill /f /t /im 【PID值】 java.exe 敲个回车 对应的端口就被解放了√ ...
Springboot集成RabbitMQ（二）
zsx18273117003的博客
08-27 1569
背景：基于Springboot集成RabbitMQ（一）进行 一、Direct exchange（默认） 每个新建队列（queue）都会自动绑定到默认交换机上，绑定的路由键（routingKey）名称与队列名称相同，工作方式类似于单播 1. 交换机和队列配置 package com.zsx.config; import org.springframework.amqp.core.Bin...
Error starting ApplicationContext. To display the conditions report re-run your application with debug enabled.
最新发布
08-13
引用、和是关于报错信息的内容。报错信息"Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled."表示在启动应用程序上下文时出现了错误，并建议重新运行应用程序，并启用调试模式以显示条件报告。这个错误一般出现在使用Spring框架的应用程序中，当应用程序启动时，它会尝试加载应用程序的上下文，但由于某种原因导致了错误。要解决这个问题，可以按照建议重新运行应用程序，并启用调试模式。这将显示条件报告，帮助你找到问题所在。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* [Error starting ApplicationContext. To display the conditions report re-run your application with](https://blog.csdn.net/blbyu/article/details/126468130)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT0_1"}}] [.reference_item style="max-width: 50%"] - *2* *3* [Error starting ApplicationContext... To display the conditions report re-run your application with ‘de](https://blog.csdn.net/s17856147699/article/details/125962137)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT0_1"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

东山富哥

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值