quartz.net运行报unable to bind scheduler to remoting

博客内容涉及遇到程序运行时端口被占用的问题,通过检查任务管理器并关闭使用端口654的进程,或者修改配置文件将端口改为655来避免报错。此解决方案适用于遇到类似端口冲突的开发者。

报错如下图:

解决:

 在任务管理器的进程中应该已经有一个端口为654的程序正在运行了,所以找到端口号为654已经运行的程序将其关闭,或者将这里的port=654改为port=655则不会报错了。

: Tomcat started on port 40000 (http) with context path '/' 2025-09-16T11:27:13.523+08:00 ERROR 34440 --- [jnpf-boot] [ Thread-13] com.xxl.job.core.server.EmbedServer : >>>>>>>>>>> xxl-job remoting server error. java.net.BindException: Address already in use: bind at java.base/sun.nio.ch.Net.bind0(Native Method) at java.base/sun.nio.ch.Net.bind(Net.java:565) at java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:344) at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:301) at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:141) at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:561) at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1281) at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600) at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579) at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:922) at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:259) at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:380) at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:173) at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:166) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:1583) 2025-09-16T11:27:13.551+08:00 INFO 34440 --- [jnpf-boot] [ main] o.s.s.quartz.SchedulerFactoryBean : Starting Quartz Scheduler now 2025-09-16T11:27:13.551+08:00 INFO 34440 --- [jnpf-boot] [ main] org.quartz.core.QuartzScheduler : Scheduler quartzScheduler_$_NON_CLUSTERED started. 2025-09-16T11:27:13.584+08:00 INFO 34440 --- [jnpf-boot] [ main] jnpf.JnpfAdminApplication : Started JnpfAdminApplication in 37.067 seconds (process running for 38.286) 2025-09-16T11:27:13.612+08:00 WARN 34440 --- [jnpf-boot] [ main] o.s.b.c.p.m.PropertiesMigrationListener : The use of configuration keys that have been renamed was found in the environment: Property source 'Config resource 'class path resource [application-dev.yml]' via location 'optional:classpath:/'': Key: spring.redis.database Line: 108 Replacement: spring.data.redis.database Key: spring.redis.host Line: 110 Replacement: spring.data.redis.host Key: spring.redis.port Line: 111 Replacement: spring.data.redis.port Key: spring.redis.timeout Line: 113 Replacement: spring.data.redis.timeout Each configuration key has been temporarily mapped to its replacement for your convenience. To silence this warning, please update your configuration to use the new keys. 2025-09-16T11:27:13.613+08:00 ERROR 34440 --- [jnpf-boot] [ main] o.s.b.c.p.m.PropertiesMigrationListener : The use of configuration keys that are no longer supported was found in the environment: Property source 'Config resource 'class path resource [application-dev.yml]' via location 'optional:classpath:/'': Key: spring.redis.lettuce.pool.max-active Line: 116 Reason: none Key: spring.redis.lettuce.pool.max-idle Line: 119 Reason: none Key: spring.redis.lettuce.pool.max-wait Line: 117 Reason: none Key: spring.redis.lettuce.pool.min-idle Line: 118 Reason: none Please refer to the release notes or reference guide for potential alternatives.
最新发布
09-17
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值