2.5将server.port改为8091报错port already used

[AllKai]

Check Ahead

• I have searched the issues of this repository and believe that this is not a duplicate.

• I am willing to try to fix this bug myself.

Ⅰ. Issue Description

No response

Ⅱ. Describe what happened

No response

Ⅲ. Describe what you expected to happen

No response

Ⅳ. How to reproduce it (as minimally and precisely as possible)

No response

Ⅴ. Anything else we need to know?

No response

Ⅵ. Environment

No response

[AllKai]

[funky-eyes]

Please provide your configuration files and the exception stack trace

[AllKai]

Please provide your configuration files and the exception stack trace

我直接改的application.yml，目前用的2.3版本，然后2.5按要求把server.port改成8091启动失败端口被占用，然后现在还是7091就没问题

`server:
port: 8091

spring:
application:
name: seata-server

logging:
config: classpath:logback-spring.xml
file:
path: ${log.home:${user.home}/logs/seata}
extend:
logstash-appender:
destination: 127.0.0.1:4560
kafka-appender:
bootstrap-servers: 127.0.0.1:9092
topic: logback_to_logstash

console:
user:
username: seata
password: seata
seata:
config:
# support: nacos, consul, apollo, zk, etcd3
type: nacos
nacos:
server-addr: xxxxx:8848
namespace: xxxxxx-c0bd-49b8-82de-1d76cd05976c
group: SEATA_GROUP
#username: nacos
#password: nacos
data-id: seataServer.properties
registry:
# support: nacos, eureka, redis, zk, consul, etcd3, sofa
type: nacos
nacos:
application: seata-server
server-addr: 172.27.195.56:8848
group: SEATA_GROUP
namespace: 585c2008-c0bd-49b8-82de-1d76cd05976c
cluster: default
#username: nacos
#password: nacos
store:
# support: file 、 db 、 redis
mode: db
session:
mode: db
lock:
mode: db
db:
datasource: druid
db-type: mysql
driver-class-name: com.mysql.cj.jdbc.Driver
url: jdbc:mysql://xxxxx:3306/seata?useUnicode=true&characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true&useSSL=false
user: xxxxx
password: xxxxx
min-conn: 10
max-conn: 100
global-table: global_table
branch-table: branch_table
lock-table: lock_table
distributed-lock-table: distributed_lock
query-limit: 1000
max-wait: 5000

`

[funky-eyes]

So when you changed the port, were you using version 2.5 or 2.3? Or is there another process on the same machine that has already bound to port 8091?