xxl_job 报错 com.xxl.rpc.util.XxlRpcException: xxl-rpc response status invalid.

流年师兄要努力りゅう 2019-12-17 03:34:08 
15:27:35.001 logback [xxl-job, admin JobScheduleHelper#scheduleThread] INFO  c.x.j.a.c.thread.JobScheduleHelper - >>>>>>>>> init xxl-job admin scheduler success.

15:28:08.386 logback [nioEventLoopGroup-2-1] ERROR c.x.r.r.n.i.n.c.NettyHttpClientHandler - >>>>>>>>>>> xxl-rpc netty_http client caught exception

com.xxl.rpc.util.XxlRpcException: xxl-rpc response status invalid.

	at com.xxl.rpc.remoting.net.impl.netty_http.client.NettyHttpClientHandler.channelRead0(NettyHttpClientHandler.java:40)

	at com.xxl.rpc.remoting.net.impl.netty_http.client.NettyHttpClientHandler.channelRead0(NettyHttpClientHandler.java:22)

	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)

	at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)

	at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)

	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:326)

	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:300)

	at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)

	at io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:287)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)

	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)

	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)

	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:931)

	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)

	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:700)

	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:635)

	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:552)

	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514)

	at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050)

	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:844)

15:28:11.376 logback [xxl-job, admin JobTriggerPoolHelper-fastTriggerPool-1256866690] INFO  c.x.r.r.i.r.XxlRpcReferenceBean - >>>>>>>>>>> xxl-rpc, invoke error, address:192.168.0.153:8080, XxlRpcRequestXxlRpcRequest{requestId='b8dba3b6-6218-4231-a6de-45cb5618b9b5', createMillisTime=1576567685983, accessToken='', className='com.xxl.job.core.biz.ExecutorBiz', methodName='run', parameterTypes=[class com.xxl.job.core.biz.model.TriggerParam], parameters=[TriggerParam{jobId=3, executorHandler='demoJobHandler', executorParams='', executorBlockStrategy='SERIAL_EXECUTION', executorTimeout=0, logId=22, logDateTime=1576567685861, glueType='BEAN', glueSource='', glueUpdatetime=1576567674000, broadcastIndex=0, broadcastTotal=1}], version='null'}

15:28:11.376 logback [xxl-job, admin JobTriggerPoolHelper-fastTriggerPool-1256866690] ERROR c.x.j.a.core.trigger.XxlJobTrigger - >>>>>>>>>>> xxl-job trigger error, please check if the executor[192.168.0.153:8080] is running.

com.xxl.rpc.util.XxlRpcException: xxl-rpc, request timeout at:1576567691376, request:XxlRpcRequest{requestId='b8dba3b6-6218-4231-a6de-45cb5618b9b5', createMillisTime=1576567685983, accessToken='', className='com.xxl.job.core.biz.ExecutorBiz', methodName='run', parameterTypes=[class com.xxl.job.core.biz.model.TriggerParam], parameters=[TriggerParam{jobId=3, executorHandler='demoJobHandler', executorParams='', executorBlockStrategy='SERIAL_EXECUTION', executorTimeout=0, logId=22, logDateTime=1576567685861, glueType='BEAN', glueSource='', glueUpdatetime=1576567674000, broadcastIndex=0, broadcastTotal=1}], version='null'}

	at com.xxl.rpc.remoting.net.params.XxlRpcFutureResponse.get(XxlRpcFutureResponse.java:117)

	at com.xxl.rpc.remoting.invoker.reference.XxlRpcReferenceBean$1.invoke(XxlRpcReferenceBean.java:242)

	at com.sun.proxy.$Proxy102.run(Unknown Source)

	at com.xxl.job.admin.core.trigger.XxlJobTrigger.runExecutor(XxlJobTrigger.java:196)

	at com.xxl.job.admin.core.trigger.XxlJobTrigger.processTrigger(XxlJobTrigger.java:149)

	at com.xxl.job.admin.core.trigger.XxlJobTrigger.trigger(XxlJobTrigger.java:74)

	at com.xxl.job.admin.core.thread.JobTriggerPoolHelper$3.run(JobTriggerPoolHelper.java:90)

	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)

	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)

	at java.base/java.lang.Thread.run(Thread.java:844)


xxl_job 分布式任务报错，求大神解决
...全文
12835 11 打赏 收藏 转发到动态 举报
AI 作业
写回复
用AI写文章
11 条回复
切换为时间正序
请发表友善的回复…
发表回复
流年师兄要努力りゅう 2020-04-23
  • 打赏
  • 举报
 回复
引用 10 楼 BeBiger 的回复：
最后是啥原因呢
执行器没有启动
BeBiger 2020-04-23
  • 打赏
  • 举报
 回复
最后是啥原因呢
流年师兄要努力りゅう 2019-12-18
  • 打赏
  • 举报
 回复
引用 6 楼 Valerie00 的回复:
@Bean(initMethod = "start", destroyMethod = "destroy") public XxlJobSpringExecutor xxlJobExecutor() { XxlJobSpringExecutor xxlJobSpringExecutor = new XxlJobSpringExecutor(); xxlJobSpringExecutor.setAdminAddresses(adminAddresses); xxlJobSpringExecutor.setAppName(appName); xxlJobSpringExecutor.setIp(ip); xxlJobSpringExecutor.setPort(port); xxlJobSpringExecutor.setAccessToken(accessToken); xxlJobSpringExecutor.setLogPath(logPath); xxlJobSpringExecutor.setLogRetentionDays(logRetentionDays); return xxlJobSpringExecutor; } 这个东西配置了没
这个配置了呀！但是日志错误 xxl-rpc响应状态无效。 所以这个我不明白到底是啥东西没有启动呀
Valerie00 2019-12-18
  • 打赏
  • 举报
 回复
@Bean(initMethod = "start", destroyMethod = "destroy")
public XxlJobSpringExecutor xxlJobExecutor() {
XxlJobSpringExecutor xxlJobSpringExecutor = new XxlJobSpringExecutor();
xxlJobSpringExecutor.setAdminAddresses(adminAddresses);
xxlJobSpringExecutor.setAppName(appName);
xxlJobSpringExecutor.setIp(ip);
xxlJobSpringExecutor.setPort(port);
xxlJobSpringExecutor.setAccessToken(accessToken);
xxlJobSpringExecutor.setLogPath(logPath);
xxlJobSpringExecutor.setLogRetentionDays(logRetentionDays);
return xxlJobSpringExecutor;
}

这个东西配置了没
Valerie00 2019-12-18
  • 打赏
  • 举报
 回复
有配置执行器吗
流年师兄要努力りゅう 2019-12-18
  • 打赏
  • 举报
 回复
引用 3 楼 Valerie00 的回复:
把你的调度中心的配置和job端的配置贴出来

### web
server.port=8080
server.context-path=/xxl-job-admin

### actuator
management.context-path=/actuator
management.health.mail.enabled=false

### resources
spring.mvc.servlet.load-on-startup=0
spring.mvc.static-path-pattern=/static/**
spring.resources.static-locations=classpath:/static/

### freemarker
spring.freemarker.templateLoaderPath=classpath:/templates/
spring.freemarker.suffix=.ftl
spring.freemarker.charset=UTF-8
spring.freemarker.request-context-attribute=request
spring.freemarker.settings.number_format=0.##########

### mybatis
mybatis.mapper-locations=classpath:/mybatis-mapper/*Mapper.xml

### xxl-job, datasource
spring.datasource.url=jdbc:mysql://127.0.0.1:3306/xxl_job?Unicode=true&characterEncoding=UTF-8
spring.datasource.username=root
spring.datasource.password=root
spring.datasource.driver-class-name=com.mysql.jdbc.Driver

spring.datasource.type=org.apache.tomcat.jdbc.pool.DataSource
spring.datasource.tomcat.max-wait=10000
spring.datasource.tomcat.max-active=30
spring.datasource.tomcat.test-on-borrow=true
spring.datasource.tomcat.validation-query=SELECT 1
spring.datasource.tomcat.validation-interval=30000

### xxl-job email
spring.mail.host=smtp.qq.com
spring.mail.port=25
spring.mail.username=xxx@qq.com
spring.mail.password=xxx
spring.mail.properties.mail.smtp.auth=true
spring.mail.properties.mail.smtp.starttls.enable=true
spring.mail.properties.mail.smtp.starttls.required=true
spring.mail.properties.mail.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory

### xxl-job, access token
xxl.job.accessToken=

### xxl-job, i18n (default empty as chinese, "en" as english)
xxl.job.i18n=

## xxl-job, triggerpool max size
xxl.job.triggerpool.fast.max=200
xxl.job.triggerpool.slow.max=100

### xxl-job, log retention days
xxl.job.logretentiondays=30

### 登录账号
xxl.job.login.username=admin
xxl.job.login.password=123456




# web port
server.port=8081

# log config
logging.config=classpath:logback.xml


### xxl-job admin address list, such as "http://address" or "http://address01,http://address02"
xxl.job.admin.addresses=http://127.0.0.1:8080/xxl-job-admin

### xxl-job executor address
xxl.job.executor.appname=xxl-job-executor-sample
xxl.job.executor.ip=192.168.0.153
xxl.job.executor.port=9999

### xxl-job, access token
xxl.job.accessToken=

### xxl-job log path
xxl.job.executor.logpath=/data/applogs/xxl-job/jobhandler
### xxl-job log retention days
xxl.job.executor.logretentiondays=30
Valerie00 2019-12-18
  • 打赏
  • 举报
 回复
把你的调度中心的配置和job端的配置贴出来
流年师兄要努力りゅう 2019-12-18
  • 打赏
  • 举报
 回复
引用 1 楼 Valerie00 的回复:
xxl-job trigger error, please check if the executor[192.168.0.153:8080] is running 你这个调度中心启动了吗，看看你job service的xxl job的地址是否配的正确
这个是启动了，就是启动了，调用的时候，才报错了呢！可以私聊解决
流年师兄要努力りゅう 2019-12-18
  • 打赏
  • 举报
 回复
引用 8 楼 Valerie00 的回复:
[quote=引用 7 楼 咸鱼的挣扎 的回复:] [quote=引用 6 楼 Valerie00 的回复:] @Bean(initMethod = "start", destroyMethod = "destroy") public XxlJobSpringExecutor xxlJobExecutor() { XxlJobSpringExecutor xxlJobSpringExecutor = new XxlJobSpringExecutor(); xxlJobSpringExecutor.setAdminAddresses(adminAddresses); xxlJobSpringExecutor.setAppName(appName); xxlJobSpringExecutor.setIp(ip); xxlJobSpringExecutor.setPort(port); xxlJobSpringExecutor.setAccessToken(accessToken); xxlJobSpringExecutor.setLogPath(logPath); xxlJobSpringExecutor.setLogRetentionDays(logRetentionDays); return xxlJobSpringExecutor; } 这个东西配置了没
这个配置了呀！但是日志错误 xxl-rpc响应状态无效。 所以这个我不明白到底是啥东西没有启动呀[/quote] 看下9999端口还在吗，我也不知道什么原因了[/quote] 端口是在的，我在看看其他的原因吧。非常感谢回答
Valerie00 2019-12-18
  • 打赏
  • 举报
 回复
引用 7 楼 咸鱼的挣扎 的回复:
[quote=引用 6 楼 Valerie00 的回复:]
@Bean(initMethod = "start", destroyMethod = "destroy")
public XxlJobSpringExecutor xxlJobExecutor() {
XxlJobSpringExecutor xxlJobSpringExecutor = new XxlJobSpringExecutor();
xxlJobSpringExecutor.setAdminAddresses(adminAddresses);
xxlJobSpringExecutor.setAppName(appName);
xxlJobSpringExecutor.setIp(ip);
xxlJobSpringExecutor.setPort(port);
xxlJobSpringExecutor.setAccessToken(accessToken);
xxlJobSpringExecutor.setLogPath(logPath);
xxlJobSpringExecutor.setLogRetentionDays(logRetentionDays);
return xxlJobSpringExecutor;
}
这个东西配置了没


这个配置了呀！但是日志错误 xxl-rpc响应状态无效。 所以这个我不明白到底是啥东西没有启动呀[/quote]

看下9999端口还在吗，我也不知道什么原因了
Valerie00 2019-12-17
  • 打赏
  • 举报
 回复
xxl-job trigger error, please check if the executor[192.168.0.153:8080] is running

你这个调度中心启动了吗，看看你job service的xxl job的地址是否配的正确
xxl-rpc remoting request fail, http HttpStatus[302] invalid
初次体验 分布式任务调度 xxl-job ，参考网上很多入门教程以及给力的源码 ，相信你也可以快速地在项目里整合起来。 废话不多说，在我启动执行器的项目的时候，竟然启动失败了， 直接po上我遇到的问题： 一开始看着控制台的错误日志，一直以为是http://127.0.0.1:8080/ 解决思路： xxl-job 的开发者不是已经提供了很多sample的嘛。好好看，仔细看看， 咦，samp...
datax-web定时任务报错，调度失败请问下什么原因造成的？是并发数太高了吗？
>>>>>>>>>>触发调度<<<<<<<<<<<调度机器：192.168.1.145。以下是预警邮件很多任务调度失败。任务触发类型：Cron触发。执行器-注册方式：自动注册。阻塞处理策略：单机串行。
xxl-job总结
调度器：负责管理调度信息，按照调度配置发出调度请求，自身不承担业务代码。调度系统与任务解耦，提高了系统可用性和稳定性，同事调度系统性能不再受限于任务模块执行器：负责接收调度请求并执行任务逻辑。任务模块专注于任务的执行等操作。1、依赖maven 2、环境3、下载 https://github.com/xuxueli/xxl-job 源码 4、初始化“调度数据库”“调度数据库初始化SQL脚本” 位置为: 5、解压源码,按照maven格式将源码导入IDE, 使用maven进行编译即可，源码结构如下：
xxl-job 源码解读 （二）
  RemotehttpJobBean 触发任务源码分析 xxl-job 所有的任务触发最终都是通过这个类来执行  , 该类继承关系如下:    RemoteHttpJobBean &gt; QuartzJobBean &gt; Job   当quartz监听到有任务需要触发是，会调用 JobRunShell 的run方法， 在该类的run方法中，会调用当前任务的JOB_CLAS...
Web 开发

81,117

社区成员

341,739

社区内容

发帖
与我相关
我的任务
社区描述
Java Web 开发
社区管理员
  • Web 开发社区
加入社区
  • 近7日
  • 近30日
  • 至今

加载中

查看更多榜单
社区公告
暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章