Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] level too large 2048 problem during serialization data by fastjson2 #14202

Open
3 of 4 tasks
asmpg opened this issue May 16, 2024 · 1 comment
Open
3 of 4 tasks
Labels
component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage

Comments

@asmpg
Copy link

asmpg commented May 16, 2024

Pre-check

  • I am sure that all the content I provide is in English.

Search before asking

  • I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

  • Dubbo 3.2.12,
  • spring cloud 2023.0.1,
  • spring boot 3.2.4,
  • spring-cloud-alibaba 2022.0.0.0,
  • JDK Azul zulu 17.0.4,
  • Windows 11

Steps to reproduce this issue

  1. create instance like this SomeObject so = new SomeObject{{ setV1("some value"); }}
  2. set so as parameter to dubbo service like ds.insert(so); ( i use @DubboReference to inject ds )
  3. get error info like below
    errimg

What you expected to happen

I need the method could run without error .

Anything else

Considering the complexity of Dubbo's workflow, I'm not sure if Dubbo's preprocessing might affect the data output to Fastjson2. Therefore, I'm submitting this issue to Dubbo first. If it's confirmed that Dubbo is not the problem, please provide me with relevant information so I can raise the question with the Fastjson2 team.

Are you willing to submit a pull request to fix on your own?

  • Yes I am willing to submit a pull request on my own!

Code of Conduct

@asmpg asmpg added component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage labels May 16, 2024
@chickenlj
Copy link
Contributor

This is the default limitation of fastjson2, you can consult Fastjson community how to avoid this issue. And we would appreciate it if you could put the link or solution back here once it's solved, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage
Projects
Status: Todo
Development

No branches or pull requests

2 participants