why the tri protocol could not use the same port number as spring.server.port?

[pedoc]

Pre-check

• 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:

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

• I agree to follow this project's Code of Conduct

[zrlw]

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

spring:
  application:
    name: dubbo-samples-nativeimage-provider
dubbo:
  application:
    name: ${spring.application.name}
    logger: slf4j
  protocol:
    name: tri
    port: 50052
#    serialization: fastjson2
    triple:
      verbose: true
      servlet:
        enabled: true
      rest:
        case-sensitive-match: false
        json-framework: fastjson2  # this project does not have jackson extension, so i used fastjson2
#  provider:
#    serialization: fastjson2
#  consumer:
#    serialization: fastjson2

logging:
  pattern:
    level: '%5p [${spring.application.name:},%X{traceId:-},%X{spanId:-}]'

server:
  port: 50052

and NativeDemoProviderApplication started successfully,

[zrlw]

Add jackson dependencies to dubbo-samples-native-image-provider,

        <dependency>
          <groupId>com.fasterxml.jackson.core</groupId>
          <artifactId>jackson-core</artifactId>
        </dependency>
        <dependency>
          <groupId>com.fasterxml.jackson.core</groupId>
          <artifactId>jackson-databind</artifactId>
        </dependency>
        <dependency>
          <groupId>com.fasterxml.jackson.datatype</groupId>
          <artifactId>jackson-datatype-jsr310</artifactId>
        </dependency>

then you could take jackson as json-framework,

spring:
  application:
    name: dubbo-samples-nativeimage-provider
dubbo:
  application:
    name: ${spring.application.name}
    logger: slf4j
  protocol:
    name: tri
    port: 50052
#    serialization: fastjson2
    triple:
      verbose: true
      servlet:
        enabled: true
      rest:
        case-sensitive-match: false
        json-framework: jackson
#  provider:
#    serialization: fastjson2
#  consumer:
#    serialization: fastjson2

logging:
  pattern:
    level: '%5p [${spring.application.name:},%X{traceId:-},%X{spanId:-}]'

server:
  port: 50052
  http2:
    enabled: true

[zrlw]

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?

[pedoc]

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.

[zrlw]

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

[finefuture]

Please add dependency and retry.

<dependency>
        <groupId>org.apache.dubbo</groupId>
        <artifactId>dubbo-spring-boot-3-autoconfigure</artifactId>
</dependency>

[pedoc]

thanks @zrlw and @finefuture

It works fine after adding dependency to provider.

[pedoc]

Releted #12495