[ISSUE #10927] Upgrade fastjson2 to 2.0.64 for JDK 8 compatibility - #10928
Open
RongtongJin wants to merge 1 commit into
Open
[ISSUE #10927] Upgrade fastjson2 to 2.0.64 for JDK 8 compatibility#10928RongtongJin wants to merge 1 commit into
RongtongJin wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #10928 +/- ##
=============================================
- Coverage 48.45% 48.32% -0.14%
+ Complexity 13588 13546 -42
=============================================
Files 1380 1380
Lines 101196 101196
Branches 13130 13130
=============================================
- Hits 49038 48902 -136
- Misses 46190 46297 +107
- Partials 5968 5997 +29 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
RongtongJin
marked this pull request as ready for review
August 13, 2026 17:42
RockteMQ-AI
approved these changes
Aug 13, 2026
RockteMQ-AI
left a comment
Contributor
There was a problem hiding this comment.
Summary
Upgrades fastjson2 from 2.0.63 → 2.0.64 (Maven) and aligns the Bazel pin from 2.0.59 → 2.0.64. This fixes a known JDK 8 cold-start regression (LambdaConversionException: Invalid caller) documented in fastjson2#7691.
Changes reviewed:
pom.xml:fastjson2.version2.0.63 → 2.0.64 ✓WORKSPACE: Bazel fastjson2 pin 2.0.59 → 2.0.64 ✓
Assessment:
- Both build systems (Maven + Bazel) are now aligned at 2.0.64
- All 10 CI checks pass (CodeQL, Bazel compile, Maven compile on JDK-8 × 3 platforms, coverage, license, misspell)
- PR description includes reproduction evidence and upstream fix references
- No API changes, no behavioral changes beyond the bugfix
LGTM — clean, minimal dependency upgrade with clear justification.
Automated review by RockteMQ-AI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which Issue(s) This PR Fixes
Brief Description
RocketMQ upgraded the Maven fastjson2 dependency to 2.0.63 in #10715. That version contains a JDK 8 cold-start regression which may throw:
The regression is fixed upstream in fastjson2 2.0.64:
This change:
How Did You Test This Change?
Using Amazon Corretto
1.8.0_502-b07in a fresh JVM, I ran:mvn -B -ntp -nsu -pl remoting -am \ -Djacoco.skip=true \ -Dtest=RemotingSerializableCompatTest \ -Dsurefire.failIfNoSpecifiedTests=false \ clean testResults under the same environment and test command:
LambdaConversionExceptionAdditional verification:
mvn -pl remoting -am -DskipTests package: passed;commonandremoting: resolves fastjson2 2.0.64 only;git diff --check: passed.