SilerKing 发表于 2023-6-16 08:29:25

请教一下流程运转过程中后台频繁报错是什么原因

8.0.0版本连接SQLServer数据库,流程运转过程中后台频繁报错,错误代码:


2023-06-16 08:11:07.758 ERROR com.x.base.core.project.scripting.ScriptingFactory - id:4388af44-3888-4fe7-a00b-ed92ad3f87ad, name:com.x.base.core.project.scripting.ScriptingFactory, message:TypeError: Cannot read property "group" from undefined in <eval> at line number 2, exception:javax.script.ScriptException.
javax.script.ScriptException: TypeError: Cannot read property "group" from undefined in <eval> at line number 2
      at jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(NashornScriptEngine.java:477) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:433) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine$3.eval(NashornScriptEngine.java:521) ~
      at com.x.base.core.project.scripting.ScriptingFactory.scriptContextEvalInitialScript(ScriptingFactory.java:148) ~
      at com.x.processplatform.service.processing.processor.AeiObjects.scriptContext(AeiObjects.java:1855) ~
      at com.x.processplatform.service.processing.processor.manual.TranslateTaskIdentityTools.duty(TranslateTaskIdentityTools.java:92) ~
      at com.x.processplatform.service.processing.processor.manual.TranslateTaskIdentityTools.translate(TranslateTaskIdentityTools.java:56) ~
      at com.x.processplatform.service.processing.processor.manual.ManualProcessor.calculateTaskIdentities(ManualProcessor.java:197) ~
      at com.x.processplatform.service.processing.processor.manual.ManualProcessor.executing(ManualProcessor.java:416) ~
      at com.x.processplatform.service.processing.processor.manual.AbstractManualProcessor.executeProcessing(AbstractManualProcessor.java:41) ~
      at com.x.processplatform.service.processing.processor.AbstractProcessor.execute(AbstractProcessor.java:212) ~
      at com.x.processplatform.service.processing.Processing.execute(Processing.java:205) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:78) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:41) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:96) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:41) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$CallableExecute.call(ActionProcessing.java:80) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$CallableExecute.call(ActionProcessing.java:69) ~
      at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
      at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: jdk.nashorn.internal.runtime.ECMAException: TypeError: Cannot read property "group" from undefined
      at jdk.nashorn.internal.runtime.ECMAErrors.error(ECMAErrors.java:57) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:213) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:185) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:172) ~
      at jdk.nashorn.internal.runtime.Undefined.get(Undefined.java:161) ~
      at jdk.nashorn.internal.scripts.Script$Recompilation$245$\^eval\_.:program(<eval>:2) ~[?:?]
      at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:655) ~
      at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:513) ~
      at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:527) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:428) ~
      ... 20 more
2023-06-16 08:11:07.831 ERROR com.x.base.core.project.scripting.JsonScriptingExecutor - id:d39b80d7-40cd-4b97-b545-f46bb83d8e09, name:com.x.base.core.project.scripting.JsonScriptingExecutor, message:TypeError: Cannot read property "getWork" from undefined in <eval> at line number 2, exception:javax.script.ScriptException.
javax.script.ScriptException: TypeError: Cannot read property "getWork" from undefined in <eval> at line number 2
      at jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(NashornScriptEngine.java:477) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:433) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine$3.eval(NashornScriptEngine.java:521) ~
      at com.x.base.core.project.scripting.JsonScriptingExecutor.jsonElement(JsonScriptingExecutor.java:51) ~
      at com.x.base.core.project.scripting.JsonScriptingExecutor.evalDistinguishedNames(JsonScriptingExecutor.java:213) ~
      at com.x.processplatform.service.processing.processor.manual.TranslateTaskIdentityTools.duty(TranslateTaskIdentityTools.java:91) ~
      at com.x.processplatform.service.processing.processor.manual.TranslateTaskIdentityTools.translate(TranslateTaskIdentityTools.java:56) ~
      at com.x.processplatform.service.processing.processor.manual.ManualProcessor.calculateTaskIdentities(ManualProcessor.java:197) ~
      at com.x.processplatform.service.processing.processor.manual.ManualProcessor.executing(ManualProcessor.java:416) ~
      at com.x.processplatform.service.processing.processor.manual.AbstractManualProcessor.executeProcessing(AbstractManualProcessor.java:41) ~
      at com.x.processplatform.service.processing.processor.AbstractProcessor.execute(AbstractProcessor.java:212) ~
      at com.x.processplatform.service.processing.Processing.execute(Processing.java:205) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:78) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:41) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:96) ~
      at com.x.processplatform.service.processing.Processing.processing(Processing.java:41) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$CallableExecute.call(ActionProcessing.java:80) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$CallableExecute.call(ActionProcessing.java:69) ~
      at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
      at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: jdk.nashorn.internal.runtime.ECMAException: TypeError: Cannot read property "getWork" from undefined
      at jdk.nashorn.internal.runtime.ECMAErrors.error(ECMAErrors.java:57) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:213) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:185) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:172) ~
      at jdk.nashorn.internal.runtime.Undefined.get(Undefined.java:161) ~
      at jdk.nashorn.internal.scripts.Script$Recompilation$255$\^eval\_/0x0000000802f9e840.o(<eval>:2) ~[?:?]
      at jdk.nashorn.internal.scripts.Script$Recompilation$254$\^eval\_/0x0000000803004040.:program(<eval>:1) ~[?:?]
      at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunctionData.java:655) ~
      at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.java:513) ~
      at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:527) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:428) ~
      ... 20 more





但神奇的是前端不显示任何报错信息,并且不影响流程运转,只在后台报错。不知道对系统运行有没有什么不良影响。

论坛管理员 发表于 2023-6-16 09:47:10

看起来像是您的自定义脚本里有这个报错,您可以去流程里搜一下设计,搜索group,看看是否有相关的自定义脚本

SilerKing 发表于 2023-6-17 14:03:37

论坛管理员 发表于 2023-6-16 09:47
看起来像是您的自定义脚本里有这个报错,您可以去流程里搜一下设计,搜索group,看看是否有相关的自定义脚 ...

今天流程运转又碰见类似的错误了:
2023-06-17 13:26:44.290 ERROR com.x.base.core.proje
ct.scripting.JsonScriptingExecutor - id:7189194d-2d0f-446c-b01d-0ae63e8423e7, na
me:com.x.base.core.project.scripting.JsonScriptingExecutor, message:TypeError: C
annot read property "dept" from undefined in <eval> at line number 2, exception:
javax.script.ScriptException.
javax.script.ScriptException: TypeError: Cannot read property "dept" from undefi
ned in <eval> at line number 2
      at jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(
NashornScriptEngine.java:477) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptE
ngine.java:433) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine$3.eval(NashornScriptEng
ine.java:521) ~
      at com.x.base.core.project.scripting.JsonScriptingExecutor.jsonElement(J
sonScriptingExecutor.java:51) ~
      at com.x.base.core.project.scripting.JsonScriptingExecutor.evalBoolean(J
sonScriptingExecutor.java:174) ~
      at com.x.processplatform.service.processing.processor.choice.ChoiceProce
ssor.inquiring(ChoiceProcessor.java:63) ~
      at com.x.processplatform.service.processing.processor.choice.AbstractCho
iceProcessor.inquireProcessing(AbstractChoiceProcessor.java:33) ~
      at com.x.processplatform.service.processing.processor.AbstractProcessor.
inquire(AbstractProcessor.java:302) ~
      at com.x.processplatform.service.processing.Processing.inquire(Processin
g.java:252) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:86) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:41) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:96) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:41) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$
CallableExecute.call(ActionProcessing.java:80) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$
CallableExecute.call(ActionProcessing.java:69) ~
      at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1128) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:628) ~[?:?]
      at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: jdk.nashorn.internal.runtime.ECMAException: TypeError: Cannot read pr
operty "dept" from undefined
      at jdk.nashorn.internal.runtime.ECMAErrors.error(ECMAErrors.java:57) ~[j
dk.scripting.nashorn:?]
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:213
) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:185
) ~
      at jdk.nashorn.internal.runtime.ECMAErrors.typeError(ECMAErrors.java:172
) ~
      at jdk.nashorn.internal.runtime.Undefined.get(Undefined.java:161) ~[jdk.
scripting.nashorn:?]
      at jdk.nashorn.internal.scripts.Script$Recompilation$266$\^eval\_/0x0000
00080311fc40.o(<eval>:2) ~[?:?]
      at jdk.nashorn.internal.scripts.Script$Recompilation$265$\^eval\_/0x0000
00080311f840.:program(<eval>:1) ~[?:?]
      at jdk.nashorn.internal.runtime.ScriptFunctionData.invoke(ScriptFunction
Data.java:655) ~
      at jdk.nashorn.internal.runtime.ScriptFunction.invoke(ScriptFunction.jav
a:513) ~
      at jdk.nashorn.internal.runtime.ScriptRuntime.apply(ScriptRuntime.java:5
27) ~
      at jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptE
ngine.java:428) ~
      ... 17 more
2023-06-17 13:26:44.300 ERROR com.x.processplatform
.service.processing.processor.AbstractProcessor - id:1fe02acd-18fe-4987-b9c5-851
27f123650, name:com.x.processplatform.service.processing.processor.AbstractProce
ssor, message:inquire return empty routes, exception:java.lang.IllegalStateExcep
tion.
java.lang.IllegalStateException: inquire return empty routes
      at com.x.processplatform.service.processing.processor.AbstractProcessor.
inquire(AbstractProcessor.java:308) ~
      at com.x.processplatform.service.processing.Processing.inquire(Processin
g.java:252) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:86) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:41) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:96) ~
      at com.x.processplatform.service.processing.Processing.processing(Proces
sing.java:41) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$
CallableExecute.call(ActionProcessing.java:80) ~
      at com.x.processplatform.service.processing.jaxrs.work.ActionProcessing$
CallableExecute.call(ActionProcessing.java:69) ~
      at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
java:1128) ~[?:?]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:628) ~[?:?]
      at java.lang.Thread.run(Thread.java:829) ~[?:?]

这个dept在流程的分支路径上的条件里return (this.data.dept=="XXXXX");报这个错后流程直接卡在分支选择走不下去。
另外这个错误和之前提到的错误都是更新8.0.0后出现的,之前版本是两年前部署的,忘了版本号是多少,从没出现这个问题。而且切回旧版点一下强制流转就能继续流转。中间隔得版本差太多了不确定那一版开始出现这个问题的。

SilerKing 发表于 2023-6-19 10:07:29

本帖最后由 SilerKing 于 2023-6-19 10:09 编辑

原来报错的版本是下载最新版o2oa-master照着教程自行编译打包的,官网下一个现成打包好的8.0.0版本(2023年4月24日21点打包的版本),把新增的页面模块放里,改过的war包替换再部署(只改了x_attendance_assemble_control.war和x_query_assemble_designer.war并且后者改动极小),发现的两个严重错误全解决了。不知哪步错了懒得查了。

xadmin 发表于 2023-6-19 17:44:07

SilerKing 发表于 2023-6-17 14:03
今天流程运转又碰见类似的错误了:
2023-06-17 13:26:44.290ERROR com.x.base.core.proje
ct.scripting ...

dept是人员组织组件吗?如果是的话它是一个对象数组,不是字符串

SilerKing 发表于 2023-6-20 09:38:07

之前从github下载o2oa-master分支代码自行编译的版本有这个报错,直接从官网下载打包好的版本再部署没有这个报错。
另外dept不是人员组织组件,是页面上的一个文本控件。

xadmin 发表于 2023-6-21 10:08:05

SilerKing 发表于 2023-6-20 09:38
之前从github下载o2oa-master分支代码自行编译的版本有这个报错,直接从官网下载打包好的版本再部署没有这 ...

看报错就是执行脚本的时候dept字段类型错误,您dept是文本字段还是文本?如果是文本,那么只是显示用,保存不下来的,用this.data.dept获取就会报错。

SilerKing 发表于 2023-6-21 10:15:44

本帖最后由 SilerKing 于 2023-6-21 10:16 编辑

xadmin 发表于 2023-6-21 10:08
看报错就是执行脚本的时候dept字段类型错误,您dept是文本字段还是文本?如果是文本,那么只是显示用,保 ...
文本字段,不是文本,控件名叫dept。另外绝对不是我设计的问题,用2年前部署的版本和官网下载打包好的8.0.0版本,本帖提到的全部错误全部不存在,流程全能走通,只有之前从github下载o2oa-master分支代码自行编译的版本有这个报错,流程走不下去,应该是6月7日中午下载的。
页: [1]
查看完整版本: 请教一下流程运转过程中后台频繁报错是什么原因