GitHub user pedoc edited a discussion: why the tri protocol could not use the
same port number as spring.server.port?
### Pre-check
- [X] I am sure that all the content I provide is in English.
### Apache Dubbo Component
Java SDK (apache/dubbo)
### Details
Spring boot 3.5.5
dubbo-spring-boot-starter 3.3.5
provider config:
```yml
spring:
application:
name: dubbo-spring-provider
server:
port: 50052
http2:
enabled: true
dubbo:
application:
name: ${spring.application.name}
qos-enable: false
protocol:
name: tri
port: 50052
triple:
verbose: true
servlet:
enabled: true
rest:
case-sensitive-match: false
json-framework: jackson
logging:
level:
"org.apache.dubbo.rpc.protocol.tri": debug
"org.apache.dubbo.remoting": debug
```
When the tri protocol uses the same port number as spring.server.port, the
consumer call will fail.error:
```
2025-09-24T19:41:50.862+08:00 ERROR 25776 --- [dubbo-spring-consumer]
[io-60052-exec-2] o.a.c.c.C.[.[.[/].[dispatcherServlet] : Servlet.service()
for servlet [dispatcherServlet] in context with path [] threw exception
[Request processing failed: org.apache.dubbo.rpc.RpcException:
java.util.concurrent.ExecutionException:
org.apache.dubbo.rpc.StatusRpcException: UNIMPLEMENTED : invalid content-type:
application/json] with root cause
```
Is this by design?
I'd like to reduce the number of ports, and it would be great if Dubbo service
calls could reuse Spring ports.
I've searched extensively but haven't found any similar information. Currently,
do Spring and Dubbo support this level of seamless integration? Or do I need to
separate the port numbers?
Thanks
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://www.apache.org/foundation/policies/conduct)
GitHub link: https://github.com/apache/dubbo/discussions/15706
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
