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] Json serialization issue when using Redis as storage. #3523

Closed
2 tasks done
hgaol opened this issue Mar 23, 2023 · 0 comments · Fixed by #3524
Closed
2 tasks done

[Bug] Json serialization issue when using Redis as storage. #3523

hgaol opened this issue Mar 23, 2023 · 0 comments · Fixed by #3524
Labels
bug Something isn't working

Comments

@hgaol
Copy link
Contributor

hgaol commented Mar 23, 2023

Search before asking

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

Environment

Mac

EventMesh version

master

What happened

when I start the TCP demo and set Redis as storage, the runtime throw json parse exception because the body have not been serialized correctly.
image

see data in Redis
image

How to reproduce

  1. set eventMesh.storage.plugin.type=redis in runtime config.
  2. add your redis config in `redis-client.properties.
  3. start runtime via org.apache.eventmesh.starter.StartUp.
  4. start subscribe demo via org.apache.eventmesh.tcp.demo.sub.eventmeshmessage.AsyncSubscribe.
  5. start tcp publish demo via org.apache.eventmesh.tcp.demo.pub.eventmeshmessage.AsyncPublish.
  6. now the error will occur.

Debug logs

Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'testAsyncMessage': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
 at [Source: (byte[])"{"specversion":"1.0","id":"5683320505","source":"/","type":"eventmeshmessage","subject":"TEST-TOPIC-TCP-ASYNC","protocolversion":"1.0","reqeventmesh2mqtimestamp":"1679593289588","propertymessagereplyto":"notnull","reqsendeventmeship":"[fe80:0:0:0:aede:48ff:fe00:1122%en5]","replyto":"localhost@ProducerGroup-producerPool-9-access#V1_4_0#CI","protocoldesc":"tcp","protocoltype":"eventmeshmessage","ttl":"30000","reqc2eventmeshtimestamp":"1679593289587","data":testAsyncMessage}"; line: 1, column: 477]
Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'testAsyncMessage': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')

	at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:2391) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:745) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidToken(UTF8StreamJsonParser.java:3634) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._reportInvalidToken(UTF8StreamJsonParser.java:3607) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._matchToken2(UTF8StreamJsonParser.java:2948) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._matchTrue(UTF8StreamJsonParser.java:2882) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextFieldName(UTF8StreamJsonParser.java:1115) ~[jackson-core-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer._deserializeContainerNoRecursion(JsonNodeDeserializer.java:440) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer$ObjectDeserializer.deserialize(JsonNodeDeserializer.java:122) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer$ObjectDeserializer.deserialize(JsonNodeDeserializer.java:105) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.DeserializationContext.readValue(DeserializationContext.java:966) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.DeserializationContext.readValue(DeserializationContext.java:953) ~[jackson-databind-2.13.0.jar:2.13.0]
	at io.cloudevents.jackson.CloudEventDeserializer.deserialize(CloudEventDeserializer.java:201) ~[cloudevents-json-jackson-2.2.0.jar:?]
	at io.cloudevents.jackson.CloudEventDeserializer.deserialize(CloudEventDeserializer.java:40) ~[cloudevents-json-jackson-2.2.0.jar:?]
	at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:322) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4675) ~[jackson-databind-2.13.0.jar:2.13.0]
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3691) ~[jackson-databind-2.13.0.jar:2.13.0]
	at io.cloudevents.jackson.JsonFormat.deserialize(JsonFormat.java:99) ~[cloudevents-json-jackson-2.2.0.jar:?]
	at org.apache.eventmesh.storage.redis.cloudevent.CloudEventCodec.lambda$static$1(CloudEventCodec.java:48) ~[eventmesh-storage-redis-1.8.0-release.jar:1.8.0-release]
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:383) ~[redisson-3.17.3.jar:3.17.3]
	at org.redisson.client.handler.CommandDecoder.decodeList(CommandDecoder.java:427) ~[redisson-3.17.3.jar:3.17.3]
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:392) ~[redisson-3.17.3.jar:3.17.3]
	at org.redisson.client.handler.CommandPubSubDecoder.decodeCommand(CommandPubSubDecoder.java:86) ~[redisson-3.17.3.jar:3.17.3]
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:137) ~[redisson-3.17.3.jar:3.17.3]
	at org.redisson.client.handler.CommandDecoder.decode(CommandDecoder.java:94) ~[redisson-3.17.3.jar:3.17.3]
	at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510) ~[netty-codec-4.1.79.Final.jar:4.1.79.Final]
	at io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:366) ~[netty-codec-4.1.79.Final.jar:4.1.79.Final]
	... 17 more

Are you willing to submit PR?

  • Yes I am willing to submit a PR!
@hgaol hgaol added the bug Something isn't working label Mar 23, 2023
mytang0 added a commit that referenced this issue Mar 29, 2023
[ISSUE #3523] fix json serialization issue when using redis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant