Https 请求僵死导致 @Scheduled 单线程定时任务挂起

已于 2023-08-11 10:32:55 修改
阅读量780 收藏
点赞数
分类专栏： java spring 文章标签： java spring boot
于 2020-09-14 15:34:33 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_38127559/article/details/108575213
版权
spring 同时被 2 个专栏收录
15 篇文章 0 订阅
订阅专栏
java
14 篇文章 0 订阅
订阅专栏

问题描述：

生产环境上的定时任务执行一段时间后，定时任务没有继续执行。

问题排查：

1.通过筛查生产环境上的日志，发现定时任务每次中止执行都是在QjyServiceImpl中的方法执行后。既有错误执行后停止，也有正常执行后停止。
错误中止日志：

2020-08-29 05:40:10.976 ERROR 1 --- [scheduling-1] c.h.e.m.d.zenith.service.QjyServiceImpl  : response is error: 
		org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://***.***.***/deviceStatePageQuery": Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out
			at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:748) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:641) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.execute(QjyServiceImpl.java:332) [attend-backend-1.2-SNAPSHOT.jar!/:1.2-SNAPSHOT]
			at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.deviceStatePageQuery(QjyServiceImpl.java:283) [attend-backend-1.2-SNAPSHOT.jar!/:1.2-SNAPSHOT]
			at com.hbd.edu.monitor.job.FindDeviceStateJob.execute(FindDeviceStateJob.java:43) [attend-backend-1.2-SNAPSHOT.jar!/:1.2-SNAPSHOT]
			at sun.reflect.GeneratedMethodAccessor1070.invoke(Unknown Source) ~[na:na]
			at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_222]
			at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_222]
			at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) [spring-context-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93) [spring-context-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_222]
			at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_222]
			at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_222]
			at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_222]
			at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_222]
			at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_222]
			at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
		Caused by: java.net.SocketTimeoutException: Read timed out
			at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.8.0_222]
			at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[na:1.8.0_222]
			at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[na:1.8.0_222]
			at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[na:1.8.0_222]
			at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[na:1.8.0_222]
			at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[na:1.8.0_222]
			at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) ~[na:1.8.0_222]
			at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:933) ~[na:1.8.0_222]
			at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) ~[na:1.8.0_222]
			at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) ~[na:1.8.0_222]
			at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) ~[na:1.8.0_222]
			at java.io.BufferedInputStream.read(BufferedInputStream.java:345) ~[na:1.8.0_222]
			at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:735) ~[na:1.8.0_222]
			at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:678) ~[na:1.8.0_222]
			at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1593) ~[na:1.8.0_222]
			at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) ~[na:1.8.0_222]
			at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ~[na:1.8.0_222]
			at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352) ~[na:1.8.0_222]
			at org.springframework.http.client.SimpleBufferingClientHttpRequest.executeInternal(SimpleBufferingClientHttpRequest.java:82) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:53) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:739) ~[spring-web-5.2.5.RELEASE.jar!/:5.2.5.RELEASE]
			... 17 common frames omitted

		**正常中止日志：**
		
	2020-09-04 18:35:01.596  INFO 1 --- [scheduling-1] c.h.e.m.d.zenith.service.QjyServiceImpl  : token: QjyResponse(msg=????, code=200, result={"token":"194113Y293b110015321599215701128"})
	2020-09-04 18:35:01.597  INFO 1 --- [scheduling-1] c.h.e.m.d.zenith.service.QjyServiceImpl  : requestUrl: https://***.***.***/deviceStatePageQuery?limit=100&pageNum=1 body: null
	2020-09-04 18:35:05.667  INFO 1 --- [scheduling-1] c.h.e.m.d.zenith.service.QjyServiceImpl  : url--> https://***.***.***/deviceStatePageQuery?limit=100&pageNum=1 QjyResponse -->QjyResponse(msg=????, code=200, result={total=9, pageSize=100, list=[{isOnline=false, did=0106000353}, {isOnline=true, did=0106000316}, {isOnline=true, did=0106000250}, {isOnline=false, did=0106000261}, {isOnline=false, did=0106000279}, {isOnline=false, did=0106000272}, {isOnline=true, did=0106000298}, {isOnline=true, did=0106000238}, {isOnline=true, did=0106000063}], pageNum=1})
		
**2.进入docker输出应用的堆栈信息到文件，找到对应的定时任务执行的线程【scheduling-1】：间隔20分钟，两次输出堆栈信息。**

**第一次定时任务线程状态：**

	"scheduling-1" #48 prio=5 os_prio=0 tid=0x00007ff061a38800 nid=0x39 runnable [0x00007fefc3692000]
	   java.lang.Thread.State: RUNNABLE
		at java.net.SocketInputStream.socketRead0(Native Method)
		at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
		at java.net.SocketInputStream.read(SocketInputStream.java:171)
		at java.net.SocketInputStream.read(SocketInputStream.java:141)
		at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
		at sun.security.ssl.InputRecord.read(InputRecord.java:503)
		at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
		- locked <0x00000000dd210938> (a java.lang.Object)
		at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
		- locked <0x00000000dd210a60> (a java.lang.Object)
		at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
		at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
		at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
		at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
		at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
		- locked <0x00000000dd210ad0> (a sun.net.www.protocol.https.DelegateHttpsURLConnection)
		at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
		- locked <0x00000000dd210ad0> (a sun.net.www.protocol.https.DelegateHttpsURLConnection)
		at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
		at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352)
		at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.lambda$getToken$0(QjyServiceImpl.java:138)
		at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl$$Lambda$1038/1351999069.call(Unknown Source)
		at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:5058)
		at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3708)
		at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2416)
		at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2299)
		- locked <0x00000000dd210c28> (a com.google.common.cache.LocalCache$StrongAccessWriteEntry)
		at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2212)
		at com.google.common.cache.LocalCache.get(LocalCache.java:4147)
		at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:5053)
		at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.getToken(QjyServiceImpl.java:132)
		at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.deviceStatePageQuery(QjyServiceImpl.java:282)
		at com.hbd.edu.monitor.job.FindDeviceStateJob.execute(FindDeviceStateJob.java:43)
		at sun.reflect.GeneratedMethodAccessor950.invoke(Unknown Source)
		at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.lang.reflect.Method.invoke(Method.java:498)
		at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
		at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
		at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93)
		at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
		at java.util.concurrent.FutureTask.run(FutureTask.java:266)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
		at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
		at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
		at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
		at java.lang.Thread.run(Thread.java:748)

	   Locked ownable synchronizers:
		- <0x00000000dc2a5b08> (a java.util.concurrent.ThreadPoolExecutor$Worker)
	
		**第二次定时任务线程状态：**
		
"scheduling-1" #48 prio=5 os_prio=0 tid=0x00007ff061a38800 nid=0x39 runnable [0x00007fefc3692000]
   java.lang.Thread.State: RUNNABLE
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	at java.net.SocketInputStream.read(SocketInputStream.java:171)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
	at sun.security.ssl.InputRecord.read(InputRecord.java:503)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
	- locked <0x00000000dd210938> (a java.lang.Object)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
	- locked <0x00000000dd210a60> (a java.lang.Object)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
	- locked <0x00000000dd210ad0> (a sun.net.www.protocol.https.DelegateHttpsURLConnection)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
	- locked <0x00000000dd210ad0> (a sun.net.www.protocol.https.DelegateHttpsURLConnection)
	at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:352)
	at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.lambda$getToken$0(QjyServiceImpl.java:138)
	at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl$$Lambda$1038/1351999069.call(Unknown Source)
	at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:5058)
	at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3708)
	at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2416)
	at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2299)
	- locked <0x00000000dd210c28> (a com.google.common.cache.LocalCache$StrongAccessWriteEntry)
	at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2212)
	at com.google.common.cache.LocalCache.get(LocalCache.java:4147)
	at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:5053)
	at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.getToken(QjyServiceImpl.java:132)
	at com.hbd.edu.monitor.device.zenith.service.QjyServiceImpl.deviceStatePageQuery(QjyServiceImpl.java:282)
	at com.hbd.edu.monitor.job.FindDeviceStateJob.execute(FindDeviceStateJob.java:43)
	at sun.reflect.GeneratedMethodAccessor950.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
	at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:
	- <0x00000000dc2a5b08> (a java.util.concurrent.ThreadPoolExecutor$Worker)

**3.根据日志和堆栈信息分析，定时任务线程状态正常。**
**4.排查代码QjyServiceImpl，找到getToken方法，检查HttpsUtil.getHttpsURLConnection，发现没有设置connectTimeout、readTimeout。**

public SimpleMessage deviceStatePageQuery(Map<String, Object> filterMap) {
UriComponentsBuilder uriComponentsBuilder = UriComponentsBuilder.fromHttpUrl(url + “/cloud/device/deviceStatePageQuery”);
filterMap.forEach(uriComponentsBuilder::queryParam);
RequestEntity requestEntity = RequestEntity.get(uriComponentsBuilder.build().toUri())
.header(token, getToken()).build();
return execute(requestEntity);
}

	public String getToken() {
		try {
			return CACHE.get(appId, () -> {
				InputStream is = null;
				HttpsURLConnection connection = null;
				try {
					String data = "?appid=" + appId + "&appkey=" + URLEncoder.encode(appKey, "UTF-8");
					connection = HttpsUtil.getHttpsURLConnection(url + "/cloud/getToken" + data, "GET");
					int code = connection.getResponseCode();
					StringBuilder str = new StringBuilder();
					if (code == 200) {//相应成功，获得相应的数据
						is = connection.getInputStream();//得到数据流（输入流）
						str.append(IOUtils.toString(is, StandardCharsets.UTF_8));
					}
					QjyResponse qjyResponse = JSON.parseObject(str.toString(), QjyResponse.class);
					JSONObject jsonObject = (JSONObject) qjyResponse.getResult();
					log.info("token: {}", qjyResponse);
					return jsonObject.getString(token);
				} catch (IOException e) {
					log.error("[getToken] 获取 token 出错了。");
					return null;
				} finally {
					if (is != null) {
						org.apache.tomcat.util.http.fileupload.IOUtils.closeQuietly(is);
					}
					if (connection != null) {
						IOUtils.close(connection);
					}
				}
			});
		} catch (ExecutionException e) {
			return null;
		}
	}

## 问题解决：
设置HttpsUtil的connectTimeout、readTimeout。定时任务中，发起http/https链接后，当链接成功，第三方服务接口持续不返回，会导致当前线程挂起，线程状态正常。类似于http/https链接僵死。
mister-big
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
java 线程僵死_线程的生命周期？什么时候会出现僵死进程？
weixin_31514087的博客
02-25 867
线程的生命周期及五种基本状态关于Java中线程的生命周期，首先看一下下面这张较为经典的图：新建(new Thread)当创建Thread类的一个实例(对象)时，此线程进入新建状态(未被启动)。例如：Thread t1=new Thread();就绪(runnable)调用Thread类的start方法，线程已经被启动，进入就绪状态，正在等待被分配给CPU时间片，也就是说此时线程正在就绪队列中排队...
Java error 62,【java异常】定时任务异常ERROR 20604 --- [ scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler : ...
weixin_42315701的博客
03-13 2276
2019-11-20 13:20:00.006 ERROR 20604 --- [ scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler : Unexpected error occurred in scheduled taskorg.apache.ibatis.binding.BindingException: Invalid bound sta...
线程sleep方法和InterruptedException异常
weixin_67049753的博客
12-01 3578
知道为啥每次调用Thread.sleep(...)方法时,都要求你捕获InterruptedException异常吗?sleep方法和 interrupt方法的关系又是什么呢？
springframework.scheduling.quartz工作调度器使用（三）-自定义多线程池任务
HarryChenj的专栏
04-13 1520
实现场景一：      1）任务在频率H1（30秒）定时执行，频率内任务执行所需时间超过频率时间段（30秒），出现频率内任务未执行完成，被下一次执行的任务中途中断的情况;     2） 第二个30秒时间节点（即下一频率）调度任务时，由于无空闲线程（上一频率任务占用全部线程），出现当前调度任务内的线程大量等待，导致第二个30秒时间节点调度任务执行的工作廷迟。    &lt;即：“springfram...
Linux服务器中线程、CPU、内存、硬盘等资源占用100%时的问题分析及解决措施
最新发布
cainiaoxxl的博客
06-27 1100
但一般情况下MySQL都能成功启动，但Nacos却不会，这是因为为了保证Nacos健康状态，通常会对Nacos设置健康检查，但又由于众多服务同时与Nacos抢资源，导致Nacos无法在健康检查期限内成功启动，Nacos无法启动又导致众多服务无法正常启动，从而不断重启，从而形成了死循环。物理内存 16G 占用，SWAP 额外占用 11G 空间，排查内存系统使用情况，分析各个进程的内存占用情况。在演示环境中，服务运行一段时间后，出现“没有子进程”的错误，ssh也无法登录，服务奔溃，演示环境不可用。
一次线程被挂起问题排查
diyukuanglong的博客
08-15 610
一次线程被挂起问题排查
Spring @Scheduled线程模型探究 - 发现问题
zyc920716的博客
02-22 232
最近工程中发现一个奇怪的问题，简单代码逻辑如下所示： @EnableScheduling @Component public class SimpleImplement { private static final Logger LOG = LoggerFactory.getLogger(SimpleImplement.class); private volatile List&...
@Scheduled定时任务未执行问题排查
weixin_44929059的博客
07-22 2319
@Scheduled(cron = "0 0 7 * * ?") @RequestMapping("/sendToErp") @Async public Result sendToErp() { log.info("xx任务开始"); xxxxxxxxxxxx; log.info("xx任务结束"); return render(); } 日志查询到一个单体定时任务应用,任务很多都没有执行了,查询日志发现任务开始的日志都没有,判断是定时任务没有执行,排查是@Schedul.
linux内核打印"BUG: scheduling while atomic
weixin_30338461的博客
07-21 643
linux内核打印"BUG: scheduling while atomic"和"bad: scheduling from the idle thread"错误的时候， 通常是在中断处理函数中调用了可以休眠的函数，如semaphore,mutex,sleep之类的可休眠的函数， 而linux内核要求在中断处理的时候，不允许系统调度，不允许抢占，要等到中断处理完成才能做其他事情。 因此，要充分...
http请求被挂起 cancled 原因
weixin_30786617的博客
09-07 9773
http请求被挂起了,但是服务器端还是正常处理数据插入/更新只是浏览器端被挂起了没有返回值。 原因 ：1.跨域请求 　　　　2.ajax请求改为同步 　　　　3.修改button type 　　　　4.修改js的响应时间长一点可以支持服务段处理时间过长导致被挂起。 转载于:https://www.cnblogs.com/jerrydailyphp/p/11479997.html...
记录一次rocketmq消费者使用单线程导致线程阻塞，消息大量积压的问题
独乐乐不如众乐乐
07-27 1957
rocketmq消费者使用单线程导致线程阻塞，消息大量积压的问题
java 杀死僵死的线程_神奇的Java僵尸(defunct)进程问题排查过程
weixin_42300721的博客
02-26 658
点击上方"IT牧场"，选择"设为星标"技术干货每日送达！ 原文链接：https://www.jianshu.com/u/21add3dce532现象描述大概1个月多以前 在启动脚本中增加了tail -f用来启动后追踪日志判断是否启动成功后发现无法执行shutdown.sh(卡住 利用curl) 然后无奈使用kill -9但通过ps -el 发现此时进程变为defunct 即僵尸进程当时的解决办法无...
spring 定时任务 崩溃
09-16
根据您提供的引用内容，其中一个可能的原因是由于网络不稳定导致的http请求僵死，最终导致整个线程不再执行。另外，如果您使用的是SpringQuartz定时任务，也有可能由于使用的存储方式不当（例如CN1.RAMJobStore）...
java线程，创建线程，关闭线程，守护线程，线程安全，线程僵死，线程池，同步并发，sleep，wait等
java2014144948的博客
10-19 407
java线程面试题1进程与线程的区别进程和线程的通信方式进程之间通信：线程之间通信：创建线程的方式守护线程线程安全的方式线程的sleep和wait线程池线程的同步和并发线程僵死线程关闭的方式 进程与线程的区别 一、每个进程都有独立的代码和数据空间，进程间的切换会有较大的开销； 二、线程是进程的一部分，可以看做是轻量级进程，属于同一进程的线程可以共享代码和数据空间，每个线程都有独立的运行栈和程序计数...
微服务定时任务 莫名其妙全部死掉的原因 @Scheduled(cron = "0 */1 * * * ?")
weixin_38822255的博客
10-23 2888
springboot 我们一般都用 @Scheduled作为定时任务 @Scheduled默认为单线程模式 ，如果同时有多个定时任务同时运行，是按同步运行的，所以如果有某个定时任务进入死循环或者用时比较长 就会影响其他的定时任务执行 解决： 设置@Scheduled多线程 添加下面类 package com.midea.mcc.task; import org.springframew...
http请求报文挂起案例
weixin_34389926的博客
02-26 1678
2019独角兽企业重金招聘Python工程师标准>>> ...
多线程使用openssl 进行HTTPS链接程序崩溃问题
qq_42330427的博客
04-12 1829
嵌入式程序中多线程调用 HTTPS链接下载文件 导致程序崩溃： 屏蔽SSL Error相关的函数调用之后恢复正常，可能里面有使用到全局变量。 #defineALLOW_SSL_ERROR_PRINTF (0) #if ALLOW_SSL_ERROR_PRINTF SSL_load_error_strings(); #endif #if ALLOW_SSL_ERROR_PRIN...
http和https协议
余韵悠扬
10-07 6356
HTTP是一个属于应用层的面向对象的协议，由于其简捷、快速的方式，适用于分布式超媒体信息系统
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

打赏作者

mister-big

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

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

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

打赏作者

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

抵扣说明：

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

余额充值