记Java代码的一次线程之旅

最新推荐文章于 2024-07-27 03:59:32 发布
最新推荐文章于 2024-07-27 03:59:32 发布
阅读量1.5k 收藏
点赞数
分类专栏： # Java
喜欢文章？请私信联系作者。
本文链接：https://blog.csdn.net/liu16659/article/details/82356444
版权

记Java代码的一次线程之旅

0.前言

我很纳闷儿，为啥我没有开启多线程，但是程序却最后跑出了多线程，正在我十分不解时，我观察intellij的标准输出察觉出有些规律可循。日志如下：

1.日志
22:36:07.012 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:07.012 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:12.013 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:12.013 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
···
22:36:17.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:17.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:17.315 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:17.315 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:22.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:22.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:22.316 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:22.316 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
···
22:36:27.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:27.014 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:27.317 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:27.317 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:27.517 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:27.517 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:32.015 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:32.015 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:32.317 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:32.317 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:32.517 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:32.517 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
···
22:36:47.016 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:47.016 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:47.319 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:47.319 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:47.519 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:47.519 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:47.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:47.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:47.908 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:47.908 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:52.017 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:52.017 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:52.319 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:52.319 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:52.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:52.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:52.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:52.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:52.909 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:52.909 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
···
22:36:57.018 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:57.018 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:57.320 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:57.320 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:57.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:57.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:57.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:57.716 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:57.910 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:57.910 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:36:58.088 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:36:58.088 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:02.018 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:02.018 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:02.320 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:02.320 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:02.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:02.520 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:02.717 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:02.717 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:02.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:02.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:03.089 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:03.089 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
····
22:37:07.019 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:07.019 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:07.019 [Thread-0] DEBUG o.a.h.i.c.DefaultManagedHttpClientConnection - http-outgoing-0: Close connection
22:37:07.321 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:07.321 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:07.521 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:07.521 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:07.718 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:07.718 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:07.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:07.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:08.090 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:08.090 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:08.269 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:08.269 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:12.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:12.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:12.321 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:12.321 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:12.321 [Thread-1] DEBUG o.a.h.i.c.DefaultManagedHttpClientConnection - http-outgoing-1: Close connection
22:37:12.521 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:12.521 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:12.718 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:12.718 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:12.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:12.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:13.090 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:13.090 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:13.269 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:13.269 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
···
22:37:17.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:17.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:17.322 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:17.322 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:17.522 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:17.522 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:17.719 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:17.719 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:17.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:17.911 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:18.091 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:18.091 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:18.270 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:18.270 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:18.463 [Thread-7] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:18.463 [Thread-7] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:22.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:22.020 [Thread-0] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:22.323 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:22.323 [Thread-1] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:22.522 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:22.522 [Thread-2] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:22.719 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:22.719 [Thread-3] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:22.912 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:22.912 [Thread-4] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:23.092 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:23.092 [Thread-5] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:23.270 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:23.270 [Thread-6] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
22:37:23.463 [Thread-7] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing expired connections
22:37:23.463 [Thread-7] DEBUG o.a.h.i.c.PoolingHttpClientConnectionManager - Closing connections idle longer than 60 SECONDS
2.思考

仔细发现，可以看到这个线程数按照1的数目递增，那么这个现象能够说明的原因就是：并不是因为设置了某个固定的线程数，而是因为某种特殊的原因导致多个线程在运行了。
接着，我就查看我的源代码，怀疑问题可能出现在while(true)循环中，其中代码如下：

public static void main(String[] args) {
        while(true){
            //testPutData();
            String charset = "utf-8";
            CsdnHtml csdnHtml = new CsdnHtml();
            String[]  result;
            result = csdnHtml.getSpecificInfo(
                    "myCsdn",
                    "https://blog.csdn.net/liu16659",
                    "grade-box clearfix",
                    charset);            
            putCsdnData(result);
            try {
                Thread.sleep(10000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
        }
    }

出现多线程的原因就是在这个while循环里。while循环中调用了putCsdnData(result)这个方法，查看这个方法

public static void putCsdnData(String [] data) {
        OpentsdbClient client = new OpentsdbClient("http://192.168.211.4:4399");
        long accessNumber = Long.parseLong(data[1]);
        Date date = new Date();
        SimpleDateFormat sdf = new SimpleDateFormat("yyyyMMdd  HH:mm");
        try {
            Map tagMap = new HashMap();
            tagMap.put("accessNumber", "cs");
            client.putData(
                    "csdn",
                    DateTimeUtil.parse(sdf.format(date).toString(), "yyyyMMdd HH:mm"),
                    accessNumber,
                    tagMap);
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

就会发现问题所在，因为每次调用一个putCsdnData()方法时，都会new一个OpentsdbClient的实例，这样每个实例都会使用一个线程【底层代码的实现】，最后慢慢累积成多个线程。
接着是，将代码修改成如下样子：

static OpentsdbClient client = new OpentsdbClient("http://192.168.211.4:4399");//使用static修饰
public static void putCsdnData(String [] data) {
        long accessNumber = Long.parseLong(data[1]);
        Date date = new Date();
        SimpleDateFormat sdf = new SimpleDateFormat("yyyyMMdd  HH:mm");
        try {
            Map tagMap = new HashMap();
            tagMap.put("accessNumber", "cs");
            client.putData(
                    "csdn",
                    DateTimeUtil.parse(sdf.format(date).toString(), "yyyyMMdd HH:mm"),
                    accessNumber,
                    tagMap);
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

最后，再次执行，即成了单线程，标准输出如下：

说文科技
关注
专栏目录
HttpClien高并发请求连接池 - PoolingHttpClientConnectionManager（*）
weixin_42408447的博客
10-29 4369
连接池技术作为创建和管理连接的缓冲池技术，目前已广泛用于诸如数据库连接等长连接的维护和管理中，能够有效减少系统的响应时间，节省服务器资源开销。其优势主要有两个：其一是减少创建连接的资源开销，其二是资源的访问控制。连接池管理的对象是长连接，对于HTTP连接是否适用，我们需要首先回顾一下长连接和短连接。 所谓长连接是指客户端与服务器端一旦建立连接以后，可以进行多次数据传输而不需重新建立连接，而短连接则每次数据传输都需要客户端和服务器端建立一次连接。长连接的优势在于省去了每次数据传输连接建立的时间开销，能够大幅度
java打印线程堆栈_Java问题定位之Java线程堆栈分析
weixin_33016287的博客
02-13 1475
采用Java开发的大型应用系统越来越大，越来越复杂，很多系统集成在一起，整个系统看起来像个黑盒子。系统运行遭遇问题(系统停止响应，运行越来越慢，或者性能低下，甚至系统宕掉)，如何速度命中问题的根本原因是我们接下来讲的目的。本系列文章将Java问题定位的方法体系化，提供一种以黑盒子方式进行问题定位的思路：如何使用线程堆栈进行性能瓶颈分析？如何分析内存泄漏？如何分析系统挂死？目录总述如何输出线程堆栈？...
apache httpclient连接池PoolingHttpClientConnectionManager
mazhongjia的博客
08-11 9913
一、首先,明确以下内容: 1.http连接池不是万能的,过多的长连接会占用服务器资源,导致其他服务受阻 2.http连接池只适用于请求是经常访问同一主机(或同一个接口)的情况下 3.并发数不高的情况下资源利用率低下 那么,当你的业务符合上面3点,那么你可以考虑使用http连接池来提高服务器性能 使用http连接池的优点: 1.复用http连接,省去了tcp的3次握手和4次挥手的时间,极大降低请求响应的时间 2.自动管理tcp连接,不用人为地释放/创建连接 使用http连接池的大致流程 : 1.创
PoolingHttpClientConnectionManager实现http连接池
毅香雪海的博客
01-08 1万+
PoolingHttpClientConnectionManager是通过租用连接和收回链接的方式来实现的。解决了http请求的多线程问题。 <dependency> <groupId>org.apache.httpcomponents</groupId> <artifactId>httpclient</artifactId> </dependency> 实现 首先需要初始化连接池。设定链接数量等，定义清理连.
记录一次OSSClient使用不当导致的OOM排查过程
最新发布
weixin_41891956的博客
07-27 66
前言最近线上有个比较边缘的项目出现OOM了，还好这个项目只是做一些离线的任务处理，出现OOM对线上业务没有什么影响，这里记录一下排查的过程Dump日志查看项目配置的主要JVM参数设置如下：登录后复制 -Xmx5120m -XX:+PreserveFramePointer -XX:+PrintGCDetails -XX:+...
聊聊jest的IdleConnectionReaper
weixin_34403693的博客
04-22 264
序 本文主要研究一下jest的IdleConnectionReaper IdleConnectionReaper jest-common-6.3.1-sources.jar!/io/searchbox/client/config/idle/IdleConnectionReaper.java public class IdleConnectionReaper extends AbstractSche...
连接池剖析及连接泄漏定位思路
shuxiaohua的博客
01-12 1427
背景 最近连续解决两起连接泄漏的问题，期间阅读了大量开源源码，发现开源软件中设计的连接池，用的也都是一些常规手段，本文为大家揭开这层神秘的面纱。 概述 大多数应用中应该都是用的TCP协议，TCP连接在建立阶段会经过3次握手，销毁阶段会经过4次握手。标准网络是分7层的，每一层都有各自的协议头，应用层拿到的有效数据，在整个报文中占比没这么大。TCP握手阶段的报文，对应用层来讲都是额外的负担。所以很多客户端都会设计连接池，来复用已建立的连接。减少创建连接带来的消耗。 连接池本身不复杂，如果不想做的通用，少量的代码
java毕设之旅游网站设计
03-22
【标题】"java毕设之旅游网站设计"涵盖了多个IT领域的关键知识点，主要涉及Java编程语言、前端开发、后端架构、数据库管理和毕业设计实践。这个项目是一个完整的餐饮旅游类网站，适合用作大学生的毕业设计或课程设计...
java 线程 异常中断_java多线程并发之旅-19-InterruptedException 中断异常处理及中断机制...
weixin_36132766的博客
02-16 1588
引言如果对 Java 中断没有一个全面的了解，可能会误以为被中断的线程将立马退出运行，但事实并非如此。中断机制是如何工作的？捕获或检测到中断后，是抛出 InterruptedException 还是重设中断状态以及在方法中吞掉中断状态会有什么后果？Thread.stop 与中断相比又有哪些异同？什么情况下需要使用中断？线程池中的异常如何处理？中断处理的最佳实践？线程中断基础知识1、interrup...
学习Java基础知识 记录笔记练习代码 Java学习资料
06-25
Java是世界上最流行的编程语言之一，尤其在企业级应用开发领域占据主导地位。这份"学习Java基础知识"的资源包，显然是一份专为初学者准备的Java学习材料，旨在帮助你从零开始掌握...祝你在Java学习之旅上取得丰硕成果！
java代码-第一个java
07-15
在IT行业中，Java是一种广泛应用的面向对象的编程语言，由...总之，“第一个Java”标志着编程之旅的开始，通过编写和运行简单的程序，初学者能够逐步掌握Java编程的基础，并为进一步探索这个强大的编程语言打开大门。
POST String文件流的几种方式
04-03 1593
13:31:08.016 [main] DEBUG o.a.h.c.protocol.RequestAddCookies - CookieSpec selected: best-match 13:31:08.027 [main] DEBUG o.a.h.c.protocol.RequestAuthCache - Auth cache not set in the context 13:31:08...
分享一次解决线上java应用导致JVM内存溢出（OOM）的问题
要啥自行车
03-15 5253
某个线上的应用运行几天后，总是出现卡死甚至出现OOM的情况。 注：文中图片可能与描述不符，仅作为演示！ 通过Linux的top命令查看cpu占比 首先通过top命令查看，发现某个java程序占用了较高内存： JDK的jps命令确定是哪个java程序 然后通过jps -l 与上面的PID列（2848）比较，确定是 picasso-java-v1.jar 这个java程序占用c...
PoolingHttpClientConnectionManager原理剖析
u014133299的博客
06-13 2万+
PoolingHttpClientConnectionManager原理剖析 继承体系 连接是如何租用和释放的？ 获取连接,回收连接触发时机 PoolingHttpClientConnectionManager原理剖析 继承体系 public class HttpClientUtil{ //全局参数 private PoolingHttpClientCo...
HttpClien高并发请求连接池 - PoolingHttpClientConnectionManager
热门推荐
soman的博客
03-15 3万+
        连接池技术作为创建和管理连接的缓冲池技术，目前已广泛用于诸如数据库连接等长连接的维护和管理中，能够有效减少系统的响应时间，节省服务器资源开销。其优势主要有两个：其一是减少创建连接的资源开销，其二是资源的访问控制。连接池管理的对象是长连接，对于HTTP连接是否适用，我们需要首先回顾一下长连接和短连接。       所谓长连接是指客户端与服务器端一旦建立连接以后，可以进行多次数据传输而...
SpringBoot 启动慢(坑)
chengjiaoti5842的博客
05-10 1399
今天生产环境出现一个诡异的现象，授权服务奇慢无比，其他接口确都正常，此现象只出现在生产环境，而我们开发，测试，预发，环境基本一致；，然后就开始了漫无边际的日志海洋里寻找原因， 017-05-10 14:00:57.951 DEBUG 20674 --- [ionManagerTimer]...
**com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findGoodsById in the service
HiFighting的博客
01-06 2907
遇到一个方法测试了好多次都报*com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method findGoodsById in the service com.qingcheng.service.goods.SpuService. Tried 3 times 这个错。也百度了很多，很多人都说是序列化或者IP的问题，但是实体类都实现了...
Tomcat内存溢出的三种情况及解决办法分析
上善若水，浮生如茶
09-08 864
Tomcat内存溢出的原因 在生产环境中tomcat内存设置不好很容易出现内存溢出。造成内存原因是不一样的，当然处理方式也不一样。 这里根据平时遇到的情况和相关资料进行一个总结。常见的一般会有下面三种情况： 1.OutOfMemoryError： Java heap space 2.OutOfMemoryError： PermGen space...
Java2实战：学习之旅与代码解析
实验提供了模板代码Hello.java，包含了主函数`main()`以及一个额外的类A，类A有一个方法`fA()`用于输出另一段文字。 实验2是一个简单的JavaApplet程序，通常涉及Web环境下的交互式小程序。虽然Java Applet在现代Web...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

打赏作者

说文科技

看书人不妨赏个酒钱？

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

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

打赏作者

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

抵扣说明：

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

余额充值