Tagged articles
17 articles
Page 1 of 1
dbaplus Community
dbaplus Community
May 13, 2026 · Backend Development

One‑Click Bug Fixes: AI‑Powered Log Diagnosis Skill with MCP

The article explains how to combine Claude Code's Skill framework with the Model Context Protocol (MCP) to let AI automatically fetch logs, extract key information, cross‑reference code, and pinpoint root‑cause bugs in a single command, illustrated by a hidden SQL bug case and efficiency tips.

AIClaude CodeMCP
0 likes · 14 min read
One‑Click Bug Fixes: AI‑Powered Log Diagnosis Skill with MCP
Wukong Talks Architecture
Wukong Talks Architecture
Sep 4, 2025 · Backend Development

How a ‘Broken Pipe’ Error Revealed Hidden Performance Bottlenecks in Production

An unexpected ‘Broken pipe’ error halted production, prompting a deep dive into logs, trace IDs, and monitoring tools like Kibana and SkyWalking, which uncovered Feign client timeouts, a costly SQL update, and redundant microservice calls, leading to targeted fixes that restored normal device operation.

MicroservicesPerformance OptimizationSQL Tuning
0 likes · 10 min read
How a ‘Broken Pipe’ Error Revealed Hidden Performance Bottlenecks in Production
ITPUB
ITPUB
Nov 1, 2024 · Backend Development

Why Our Nginx Data Gateway OOM’d: Tracing Memory Spikes & Core Dumps

An Nginx‑based data collection gateway began crashing with OOM kills, prompting a detailed investigation that uncovered memory spikes caused by aggressive batch processing, oversized protobuf payloads, and insufficient memory‑pool management, leading to a custom core‑dump solution and several mitigation strategies.

Batch ProcessingOOMProtobuf
0 likes · 16 min read
Why Our Nginx Data Gateway OOM’d: Tracing Memory Spikes & Core Dumps
Huolala Tech
Huolala Tech
Mar 21, 2024 · Backend Development

How a Faulty Lazy-Loading Design Caused Thread‑Pool Exhaustion and How to Fix It

A production incident where a poorly implemented lazy‑loading mechanism for KMSClient caused repeated initialization, blocking threads, exhausting the shared thread pool, and triggering RejectedExecutionException alerts, was investigated step‑by‑step, leading to a concrete code fix, improved monitoring, and better thread‑pool isolation.

JavaKMS clientbackend debugging
0 likes · 16 min read
How a Faulty Lazy-Loading Design Caused Thread‑Pool Exhaustion and How to Fix It
Su San Talks Tech
Su San Talks Tech
Oct 21, 2023 · Backend Development

How to Pinpoint Java Performance Bottlenecks with Arthas

This article walks you through using the open‑source Java diagnostic tool Arthas to locate and analyze performance problems in Java applications, covering basic and advanced tracing, filtering, and flame‑graph visualization without modifying source code.

ArthasJava performanceProfiling
0 likes · 9 min read
How to Pinpoint Java Performance Bottlenecks with Arthas
Liangxu Linux
Liangxu Linux
Apr 25, 2023 · Backend Development

Why Your Service Returns 502 Errors Even When Its Logs Show No Issue

This article explains the meaning of HTTP 502 Bad Gateway errors, how reverse proxies like nginx generate them, common causes such as premature connection termination, server crashes, misconfigured upstreams, and practical steps to diagnose and fix the problem.

502Bad GatewayHTTP status codes
0 likes · 14 min read
Why Your Service Returns 502 Errors Even When Its Logs Show No Issue
Senior Brother's Insights
Senior Brother's Insights
Sep 5, 2022 · Backend Development

How a Hidden Ternary Operator Triggered Massive Data Deletion in a Java Backend

After taking over a system via a server image, the author uncovered malicious modifications that used a ternary expression to force id=1, causing MyBatis to generate a “where 1=1” clause that deleted the entire T_QUART_DATA table, and later discovered cron jobs that removed core jars, illustrating a thorough forensic debugging process.

JavaLinuxMyBatis
0 likes · 7 min read
How a Hidden Ternary Operator Triggered Massive Data Deletion in a Java Backend
360 Quality & Efficiency
360 Quality & Efficiency
Apr 24, 2020 · Backend Development

Root Cause Analysis of Connection Reset by Peer in a Go Backend Service

This article details a production incident where a Go backend service returned "connection reset by peer" due to exhausted process file descriptors caused by a saturated database connection pool, and describes the step‑by‑step troubleshooting, socket internals, and the eventual fix.

Connection ResetDatabase Connection PoolGo
0 likes · 14 min read
Root Cause Analysis of Connection Reset by Peer in a Go Backend Service