RockteMQ-AI commented on issue #10927: URL: https://github.com/apache/rocketmq/issues/10927#issuecomment-5283070715
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** fastjson2 2.0.63 has a JDK 8 cold-start regression where `MethodHandles.Lookup` initialization order causes `LambdaConversionException: Invalid caller` during property accessor creation for remoting serialization classes (e.g., `BatchAck.setTopic`). **Verification:** - Current `pom.xml` on `develop` branch sets `<fastjson2.version>2.0.63</fastjson2.version>` ✓ - Bazel BUILD files reference fastjson2 via `@maven//` — so the Maven version is the single source of truth ✓ - Upstream fix confirmed in fastjson2 2.0.64: [alibaba/fastjson2#7718](https://github.com/alibaba/fastjson2/pull/7718) - Reproduction with `RemotingSerializableCompatTest` on JDK 8 is clear and deterministic ✓ **Impact:** Remoting serialization fails on JDK 8 cold start. Affects all JDK 8 deployments that hit the affected code path before fastjson2 internal caches are warmed. **Severity:** Medium — JDK 8 is a supported runtime; the failure is order-dependent but reproducible in fresh JVMs. **Proposed Fix:** Bump `fastjson2.version` from `2.0.63` → `2.0.64` in `pom.xml`. No code changes needed. An automated fix PR can be generated. Reply `/approve` to proceed, or `/reject` to skip. --- *Automated evaluation by github-manager* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
