-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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] Using Stream With generic and injvm not work #14546
Comments
org.apache.dubbo.rpc.RpcException: java.lang.IllegalArgumentException: [Serialization Security] Serialized class tech.xixing.dubbo.demo.stream.StreamConsumerDemo$1 has not implement Serializable interface. Current mode is strict check, will disallow to deserialize it by default.
|
System.setProperty("dubbo.application.check-serializable", "false"); must set this properties works well,But using stream mode why I should set this properties |
do you have some idea for your case ? i can implement that @xixingya |
maybe streamObserver can exclude by Serializable check? |
StreamObserver is a special class and should not pass to Serialize checker |
i guess that he wants to use generic invoke, and at the same time use StreamObserver(BI or S),such as following case:
is it ? @xixingya |
yesterday, i try to rebuild GenericFilter and TripleInvoker to support it, but it's costly, need i support it ? @AlbumenJ |
You can try it |
same promblem, looking forword to a solution~~ |
@JunJieLiu51520 I have this requirement, how can it be implemented? |
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
3.2.*
Steps to reproduce this issue
https://github.com/xixingya/dubbo-demo/blob/master/dubbo-demo-spi/src/main/java/tech/xixing/dubbo/demo/stream/StreamProviderDemo.java
please see this code. which is copy from
https://cn.dubbo.apache.org/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/triple/streaming/#%E5%AE%9E%E7%8E%B0%E7%B1%BB
What you expected to happen
the stream mode not working
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: