Java Ternary Operator NPE, Message Storm, and Network Latency Cases

The article starts with a safety principle analogy and then presents three real‑world backend incidents that illustrate common pitfalls and debugging techniques.

1. Ternary Operator NPE – A Java snippet using the conditional operator expression1 ? expression2 : expression3 caused a NullPointerException because the third operand was a primitive 0L . This forced automatic unboxing of playBoyExtra.getOpenTime() , which could be null . The analysis shows the three steps: fetching the object, unboxing it, and re‑boxing the result, and references JLS 15.25.2. A corrected version replaces the primitive with Long.valueOf(0L) to avoid unboxing.

public class ConditionalOperatorDemo { public static void main(String[] args) { PlayBoyExtra playBoyExtra = new PlayBoyExtra(); Long openTime = null != playBoyExtra ? playBoyExtra.getOpenTime() : 0L; } private static class PlayBoyExtra { private Long openTime; public Long getOpenTime() { return openTime; } public void setOpenTime(Long openTime) { this.openTime = openTime; } } }

2. Message Storm – Wrong Parameter Order – An UPDATE SQL caused a connection‑pool deadlock. The root cause was a bug in a RocketMQ wrapper where the message and tags arguments were swapped. Fixing the parameter order restored normal operation, but the fix unintentionally re‑enabled a message‑driven feedback loop, leading to a “message storm” that repeatedly triggered database updates.

public boolean sendMessage(String topic, String tags, String message) { if (message == null || tags == null) { log.error("[MetaProducerManager] message|tags is null"); return false; } return sendMessage(new Message(topic, tags, message.getBytes())); }

3. Page Lag – Network Path Issue – Users reported intermittent UI lag. Investigation revealed that requests from a specific data center (EA119) were being routed through an extra hop (Zhangbei → South‑Tong server) causing a 10‑fold increase in response time. After adjusting the routing so that affected users connect directly to the South‑Tong entry point, latency returned to normal. The case highlights that performance problems are not always code‑related; network topology can be the hidden factor.

The three cases together illustrate how a developer must consider language semantics, message‑queue contracts, and infrastructure topology when diagnosing production incidents.