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

Receiving Stringify Json in DLQ instead of JSON itself #5419

Closed
dkumarkartik opened this issue Aug 1, 2023 · 3 comments
Closed

Receiving Stringify Json in DLQ instead of JSON itself #5419

dkumarkartik opened this issue Aug 1, 2023 · 3 comments
Labels
status/need-feedback Calling participant to provide feedback

Comments

@dkumarkartik
Copy link

Description:
We are using one java application as processor app and when some exception occurs inside application for some record, it sends that record to DLQ which is expected.
But DLQ receives stringfy JSON instead of JSON record.
So can you please do let us know If there is anything we need to specify for getting JSON msg inside DLQ?

Additional context:
If any exception happens in predefined application then it sends record to DLQ as JSON record while for custom application it convert it to stringify JSON.

@github-actions github-actions bot added the status/need-triage Team needs to triage and take a first look label Aug 1, 2023
@EmperorBlack
Copy link

Additional Ifno - if we specify schema registry url for any bean and exception occured in that bean it sends data to DLQ as stringify JSON. if we are not specifying schema-registry config it sends data to DLQ as JSON.

@sobychacko
Copy link
Contributor

@dkumarkartik @EmperorBlack Could you share your config/code here? Also, how can we reproduce it on our end? Which schema registry are you using? Confluent or the one from Spring Cloud Stream?

@ilayaperumalg ilayaperumalg changed the title Reciving Stringify Json in DLQ instead of JSON itself Receiving Stringify Json in DLQ instead of JSON itself Apr 4, 2024
@ilayaperumalg ilayaperumalg added status/need-feedback Calling participant to provide feedback and removed status/need-triage Team needs to triage and take a first look labels Apr 4, 2024
@cppwfs
Copy link
Contributor

cppwfs commented Jul 22, 2024

Closing due to inactivity. If closed in error please let us know.

@cppwfs cppwfs closed this as completed Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/need-feedback Calling participant to provide feedback
Projects
None yet
Development

No branches or pull requests

5 participants