关于分布式调度中心部署登录成功后控制台显示的异常(争盼回复)

来源：5-6 XXL-JOB-ADMIN搭建

网络时空

2021-01-29

师兄，晚上好！

根据视频中的教程，我用docker方式已经部署好了xxl-job的调度中心，用默认的用户名和密码 admin 123456 也可以正常登录，登录后也能在管理界面中看到相关内容。

图片描述
但是控制台下用
docker logs --tail 10000 容器id 看时，却发现报如下错务

图片描述

官方的sql语句中对于t_job_info表中及提供的sql语句中的确是没有定义job_cron这个字段的，但是登录时相关的业务逻辑查询语句中却是有这个字段job_cron的查询的，所以一直报这个错，但是xxl-job-admin 管理后台却是可以登录的。

难道这是官方的一个bug ? 请师兄帮忙答疑确认下！

如下是xxl-job 官方的sql语句中的部分内容

CREATE TABLE xxl_job_info (
id int(11) NOT NULL AUTO_INCREMENT,
job_group int(11) NOT NULL COMMENT ‘执行器主键ID’,
job_desc varchar(255) NOT NULL,
add_time datetime DEFAULT NULL,
update_time datetime DEFAULT NULL,
author varchar(64) DEFAULT NULL COMMENT ‘作者’,
alarm_email varchar(255) DEFAULT NULL COMMENT ‘报警邮件’,
schedule_type varchar(50) NOT NULL DEFAULT ‘NONE’ COMMENT ‘调度类型’,
schedule_conf varchar(128) DEFAULT NULL COMMENT ‘调度配置，值含义取决于调度类型’,
misfire_strategy varchar(50) NOT NULL DEFAULT ‘DO_NOTHING’ COMMENT ‘调度过期策略’,
executor_route_strategy varchar(50) DEFAULT NULL COMMENT ‘执行器路由策略’,
executor_handler varchar(255) DEFAULT NULL COMMENT ‘执行器任务handler’,
executor_param varchar(512) DEFAULT NULL COMMENT ‘执行器任务参数’,
executor_block_strategy varchar(50) DEFAULT NULL COMMENT ‘阻塞处理策略’,
executor_timeout int(11) NOT NULL DEFAULT ‘0’ COMMENT ‘任务执行超时时间，单位秒’,
executor_fail_retry_count int(11) NOT NULL DEFAULT ‘0’ COMMENT ‘失败重试次数’,
glue_type varchar(50) NOT NULL COMMENT ‘GLUE类型’,
glue_source mediumtext COMMENT ‘GLUE源代码’,
glue_remark varchar(128) DEFAULT NULL COMMENT ‘GLUE备注’,
glue_updatetime datetime DEFAULT NULL COMMENT ‘GLUE更新时间’,
child_jobid varchar(255) DEFAULT NULL COMMENT ‘子任务ID，多个逗号分隔’,
trigger_status tinyint(4) NOT NULL DEFAULT ‘0’ COMMENT ‘调度状态：0-停止，1-运行’,
trigger_last_time bigint(13) NOT NULL DEFAULT ‘0’ COMMENT ‘上次调度时间’,
trigger_next_time bigint(13) NOT NULL DEFAULT ‘0’ COMMENT ‘下次调度时间’,
PRIMARY KEY (id)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

写回答

1回答

网络时空

提问者

2021-01-29

数据表中的sql语句中压根就没有t_job字段的定义，但是xxl-job调试中心的系统却有查询语句查询这个字段

-------------------------------------------------------------------------------

21:29:47.012 logback [xxl-job, admin JobScheduleHelper#scheduleThread] ERROR c.x.j.a.c.thread.JobScheduleHelper - >>>>>>>>>>> xxl-job, JobScheduleHelper#scheduleThread error:{}
org.springframework.jdbc.BadSqlGrammarException:
### Error querying database. Cause: java.sql.SQLSyntaxErrorException: Unknown column 't.job_cron' in 'field list'
### The error may exist in class path resource [mybatis-mapper/XxlJobInfoMapper.xml]
### The error may involve com.xxl.job.admin.dao.XxlJobInfoDao.scheduleJobQuery-Inline
### The error occurred while setting parameters
### SQL: SELECT     t.id,   t.job_group,   t.job_cron,   t.job_desc,   t.add_time,   t.update_time,   t.author,   t.alarm_email,   t.executor_route_strategy,   t.executor_handler,   t.executo
r_param,   t.executor_block_strategy,   t.executor_timeout,   t.executor_fail_retry_count,   t.glue_type,   t.glue_source,   t.glue_remark,   t.glue_updatetime,   t.child_jobid,   t.trigger_status,   t.trigger_last_time,   t.trigger_next_time      FROM xxl_job_info AS t   WHERE t.trigger_status = 1    and t.trigger_next_time   <=   ?   ORDER BY id ASC   LIMIT ?### Cause: java.sql.SQLSyntaxErrorException: Unknown column 't.job_cron' in 'field list'
; bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: Unknown column 't.job_cron' in 'field list'
   at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:235)
   at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:72)
   at org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:88)
   at org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:440)
   at com.sun.proxy.$Proxy80.selectList(Unknown Source)
   at org.mybatis.spring.SqlSessionTemplate.selectList(SqlSessionTemplate.java:223)
   at org.apache.ibatis.binding.MapperMethod.executeForMany(MapperMethod.java:147)
   at org.apache.ibatis.binding.MapperMethod.execute(MapperMethod.java:80)
   at org.apache.ibatis.binding.MapperProxy$PlainMethodInvoker.invoke(MapperProxy.java:144)
   at org.apache.ibatis.binding.MapperProxy.invoke(MapperProxy.java:85)
   at com.sun.proxy.$Proxy82.scheduleJobQuery(Unknown Source)
   at com.xxl.job.admin.core.thread.JobScheduleHelper$1.run(JobScheduleHelper.java:79)
   at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLSyntaxErrorException: Unknown column 't.job_cron' in 'field list'
   at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
   at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
   at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
   at com.mysql.cj.jdbc.ClientPreparedStatement.executeInternal(ClientPreparedStatement.java:953)
   at com.mysql.cj.jdbc.ClientPreparedStatement.execute(ClientPreparedStatement.java:370)
   at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44)
   at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java)
   at org.apache.ibatis.executor.statement.PreparedStatementHandler.query(PreparedStatementHandler.java:64)