apache / apache/dubbo

Dubbo 3.0.5 Provider 接收参数为 Null

Open
#9,611 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
41.6k
Forks
26.4k
Avg merge
15h 13m
Merged PRs (30d)
4

Description

- [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.

## Ask your question here
hello:
I defined the service API interface with IDL, but the parameter received by the Provider is null;

## Service config
spring.profiles.active=local
server.port = 8081
spring.application.name=xxxxxxx
recommend.service.version=1.0.0
management.endpoint.health.show-details=always
management.server.ssl.enabled=false

## dubbo config
dubbo.scan.base-packages=com.mx.yoho.coordination
dubbo.protocol.name=dubbo
dubbo.protocol.port=8082
dubbo.registry.address=zookeeper://127.0.0.1:2181
dubbo.registry.file=${user.home}/dubbo-cache/${spring.application.name}/dubbo.cache

do i need add the config "dubbo.protocol.serialization=protobuf" in the properties file ? i have try to add it, will meet more serialization issue.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the IDL-defined service with Dubbo 3.0.5 and the service configuration shown, focusing on the Provider's null parameter. Compare the default Dubbo serialization with the attempted protobuf setting and record the resulting serialization errors. Done means the Provider receives the expected non-null parameter without introducing serialization failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
backend-api-design, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.