When the tri protocol uses the same port number as spring.server.port, the consumer call will fail.error:
\n2025-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\nIs this by design?
\nI'd like to reduce the number of ports, and it would be great if Dubbo service calls could reuse Spring ports.
\nI'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
\nCode of Conduct
\n- \n
- I agree to follow this project's Code of Conduct \n
Please add dependency and retry.
\n<dependency>\n <groupId>org.apache.dubbo</groupId>\n <artifactId>dubbo-spring-boot-3-autoconfigure</artifactId>\n</dependency>\nwhy the tri protocol could not use the same port number as spring.server.port? #15706
-
Pre-check
Apache Dubbo ComponentJava SDK (apache/dubbo) DetailsSpring boot 3.5.5 provider config: 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: 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. Thanks Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
|
I tested dubbo-samples-native-image-provider at dubbo-samples, i changed https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-native-image/dubbo-samples-native-image-provider/src/main/resources/application.yml to and NativeDemoProviderApplication started successfully, |
Beta Was this translation helpful? Give feedback.
-
|
Add jackson dependencies to dubbo-samples-native-image-provider, then you could take |
Beta Was this translation helpful? Give feedback.
-
|
you could do anything of http protocols through tripe since triple support all http protocols, why you need to use the same port as spring's server.port? |
Beta Was this translation helpful? Give feedback.
-
|
Dubbo automatically registers with Nacos, simplifying infrastructure if they share the same port. The front-end gateway also adds some dedicated headers, and the Spring pipeline also has custom logic, allowing Dubbo and Spring to share the same business logic. |
Beta Was this translation helpful? Give feedback.
-
|
you could filter the http request to triple by servlet filter, refer to dubbo-samples-triple-servlet: https://github.com/apache/dubbo-samples/tree/master/2-advanced/dubbo-samples-triple-servlet |
Beta Was this translation helpful? Give feedback.
-
|
Please add dependency and retry. |
Beta Was this translation helpful? Give feedback.
-
|
thanks @zrlw and @finefuture It works fine after adding dependency to provider. |
Beta Was this translation helpful? Give feedback.
-
|
Releted #12495 |
Beta Was this translation helpful? Give feedback.
Please add dependency and retry.