<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>分类：JUC - LT技术站</title><link>https://lautung.com/categories/juc</link><atom:link href="https://lautung.com/categories/juc/feed/categories/juc.xml" rel="self" type="application/rss+xml"/><description>纸上得来终觉浅，绝知此事要躬行！</description><generator>Halo v2.27.2</generator><language>zh-cn</language><image><url>https://lautung.com/upload/ChatGPT%20Image%202026%E5%B9%B47%E6%9C%8810%E6%97%A5%2002_45_40(1).webp</url><title>分类：JUC - LT技术站</title><link>https://lautung.com/categories/juc</link></image><lastBuildDate>Sun, 15 Nov 2026 00:18:41 GMT</lastBuildDate><item><title><![CDATA[Java线程池的优雅关停：从shutdown到shutdownNow的究竟]]></title><link>https://lautung.com/archives/lf825xo8</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Java%E7%BA%BF%E7%A8%8B%E6%B1%A0%E7%9A%84%E4%BC%98%E9%9B%85%E5%85%B3%E5%81%9C%EF%BC%9A%E4%BB%8Eshutdown%E5%88%B0shutdownNow%E7%9A%84%E7%A9%B6%E7%AB%9F&amp;url=/archives/lf825xo8" width="1" height="1" alt="" style="opacity:0;">应用重启时，线程池里的任务怎么办？直接“拔电源”，正在执行的任务会丢失，积压的队列也可能被清空。要做到“优雅关停”，就得在停止服务前，给线程池一个体面的收场：尽力完成进行中的任务、合理地放弃等待，并确保资源回收。 本文将讲解线程池关闭的核心机制，并给出标准化的优雅停机范式。 一、线程池的状态：先看懂]]></description><guid isPermaLink="false">/archives/lf825xo8</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019e0c97-57c4-71c8-aa0c-09991c25ad46.jpg&amp;size=m" type="image/jpeg" length="33320"/><category>JUC</category><pubDate>Sat, 9 May 2026 13:04:43 GMT</pubDate></item><item><title><![CDATA[Java线程池如何处理异常？线程池异常处理：避开“吞异常”陷阱]]></title><link>https://lautung.com/archives/5lZPZWGR</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Java%E7%BA%BF%E7%A8%8B%E6%B1%A0%E5%A6%82%E4%BD%95%E5%A4%84%E7%90%86%E5%BC%82%E5%B8%B8%EF%BC%9F%E7%BA%BF%E7%A8%8B%E6%B1%A0%E5%BC%82%E5%B8%B8%E5%A4%84%E7%90%86%EF%BC%9A%E9%81%BF%E5%BC%80%E2%80%9C%E5%90%9E%E5%BC%82%E5%B8%B8%E2%80%9D%E9%99%B7%E9%98%B1&amp;url=/archives/5lZPZWGR" width="1" height="1" alt="" style="opacity:0;">在使用线程池时，你很可能遇到过这种情况：任务明明出错了，日志里却干干净净，就像什么都没发生一样。这其实是因为 线程池默认会“吞掉”某些异常，尤其当你用 submit() 提交 Callable 或 Runnable 时。 本文将彻底梳理线程池异常处理的四种主要方式，并给出最佳实践，帮你告别“异常黑洞]]></description><guid isPermaLink="false">/archives/5lZPZWGR</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019e0cbe-ff1e-733c-a47d-7486e75882c6.jpg&amp;size=m" type="image/jpeg" length="33874"/><category>JUC</category><pubDate>Sat, 9 May 2026 12:58:16 GMT</pubDate></item></channel></rss>