GitHub user zrlw added a comment to the discussion: why the tri protocol could not use the same port number as spring.server.port?
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 # dubbo 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, <img width="1415" height="815" alt="7fc4be2d-8105-4c00-959f-1683dab8e137" src="https://github.com/user-attachments/assets/f1108fe0-87a2-4548-a24c-10f0b5817f81"; /> GitHub link: https://github.com/apache/dubbo/discussions/15706#discussioncomment-14506701 ---- 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]
