-
Notifications
You must be signed in to change notification settings - Fork 223
Closed
Description
Expected Behavior
When starting with grpc, the program should start normally without any alarm log information
Actual Behavior
When using grpc, the following warn logs appear.
2025-03-29T09:49:14.430+08:00 WARN 4660 --- [dapr-demo] [ main] io.dapr.config.Property : Invalid override value in property: dapr.grpc.port
2025-03-29T09:49:15.080+08:00 WARN 4660 --- [dapr-demo] [ main] io.dapr.config.Property : Invalid override value in property: dapr.grpc.port
2025-03-29T09:49:15.594+08:00 WARN 4660 --- [dapr-demo] [ main] io.dapr.config.Property : Invalid override value in property: dapr.grpc.port
2025-03-29T09:49:16.474+08:00 WARN 4660 --- [dapr-demo] [ main] io.dapr.config.Property : Invalid override value in property: dapr.grpc.port
Steps to Reproduce the Problem
Use the following version and start directly without any properties or YAML configuration.
<!--
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.4.4</version>
<relativePath/>
</parent>
-->
<dependency>
<groupId>io.grpc</groupId>
<artifactId>grpc-services</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.grpc</groupId>
<artifactId>spring-grpc-spring-boot-starter</artifactId>
</dependency>
<dependency>
<groupId>io.dapr.spring</groupId>
<artifactId>dapr-spring-boot-starter</artifactId>
<version>0.14.0</version>
</dependency>
Release Note
RELEASE NOTE: Fix the warn log issue caused by not setting the dapr.client.grpcPort variable
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't workingSomething isn't working