I run a workflow in a CRON job. Sometimes I get a warning or an execution failed:
eg WARN KNIME-Worker-10-GET Request 3:824 Node Cannot loop fewer than once
Could there an option in the new UI to look up the node id nr(eg 3:824 with this warning) in a workflow and directly open it?
Hi @Burg,
Thanks for your feature request. I have two related questions: What do you mean with directly open it, the node configuration? If this is a warning, it should be displayed inside the workflow monitor, but I guess this might be not the only warning of this workflow, right?
@schramm When the CRON as automatically run the workflow, I receive an email with all the errors that occurred.
eg part of the email
ERROR KNIME-Worker-3-Excel Reader 3:749 Node Execute failed: Resource deadlock avoided
java.io.IOException: Resource deadlock avoided
at java.base/sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at java.base/sun.nio.ch.FileDispatcherImpl.read(Unknown Source)
at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at java.base/sun.nio.ch.IOUtil.read(Unknown Source)
at java.base/sun.nio.ch.IOUtil.read(Unknown Source)
at java.base/sun.nio.ch.FileChannelImpl.read(Unknown Source)
at java.base/sun.nio.ch.ChannelInputStream.read(Unknown Source)
at java.base/sun.nio.ch.ChannelInputStream.read(Unknown Source)
at java.base/sun.nio.ch.ChannelInputStream.read(Unknown Source)
at org.apache.poi.util.IOUtils.readFully(IOUtils.java:338)
at org.apache.poi.poifs.filesystem.FileMagic.valueOf(FileMagic.java:177)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.read.streamed.AbstractStreamedRead.createParser(AbstractStreamedRead.java:113)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.read.ExcelRead.startParserThread(ExcelRead.java:314)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.read.ExcelRead.(ExcelRead.java:165)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.read.streamed.AbstractStreamedRead.(AbstractStreamedRead.java:100)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.read.streamed.xlsx.XLSXRead.(XLSXRead.java:98)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.ExcelTableReader.createXLSXRead(ExcelTableReader.java:227)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.ExcelTableReader.getExcelRead(ExcelTableReader.java:182)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.ExcelTableReader.checkSpecs(ExcelTableReader.java:146)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.ExcelTableReader.checkSpecs(ExcelTableReader.java:1)
at org.knime.filehandling.core.node.table.reader.DefaultMultiTableReadFactory.validateIndividualSpecs(DefaultMultiTableReadFactory.java:229)
at org.knime.filehandling.core.node.table.reader.DefaultMultiTableReadFactory.createFromConfig(DefaultMultiTableReadFactory.java:214)
at org.knime.filehandling.core.node.table.reader.MultiTableReader.createMultiRead(MultiTableReader.java:128)
at org.knime.filehandling.core.node.table.reader.MultiTableReader.getMultiRead(MultiTableReader.java:209)
at org.knime.filehandling.core.node.table.reader.MultiTableReader.readTable(MultiTableReader.java:167)
at org.knime.filehandling.core.node.table.reader.TableReaderNodeModel.execute(TableReaderNodeModel.java:160)
at org.knime.ext.poi3.node.io.filehandling.excel.reader.ExcelTableReaderNodeModel.execute(ExcelTableReaderNodeModel.java:106)
at org.knime.core.node.NodeModel.executeModel(NodeModel.java:596)
at org.knime.core.node.Node.invokeFullyNodeModelExecute(Node.java:1284)
at org.knime.core.node.Node.execute(Node.java:1049)
at org.knime.core.node.workflow.NativeNodeContainer.performExecuteNode(NativeNodeContainer.java:603)
at org.knime.core.node.exec.LocalNodeExecutionJob.mainExecute(LocalNodeExecutionJob.java:98)
at org.knime.core.node.workflow.NodeExecutionJob.internalRun(NodeExecutionJob.java:198)
at org.knime.core.node.workflow.NodeExecutionJob.run(NodeExecutionJob.java:117)
at org.knime.core.util.ThreadUtils$RunnableWithContextImpl.runWithContext(ThreadUtils.java:369)
at org.knime.core.util.ThreadUtils$RunnableWithContext.run(ThreadUtils.java:223)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at org.knime.core.util.ThreadPool$MyFuture.run(ThreadPool.java:123)
at org.knime.core.util.ThreadPool$Worker.run(ThreadPool.java:246)
In the old UI the number of the node was displayed in the workflow so pinpointing and correction was easier. Now you have to open the node to see the number in the top bar of the pop-up window.
If you have multiple occurrences of the the same node in a workflow this takes quit some time to find the right one.
I don’t understand what you mean with the workflow monitor. I was unable to find it
With the workflow monitor (available since 5.3) I refer to this panel — you see all errors and warnings of the current state of the workflow (If you inspect jobs in the browser on the KNIME Hub, you will see the errors and warnings of opened job) Via the arrow button you can navigate to the node, wether it is in the same level that you are looking at or in a component or metanode. The errors and warnings of the selected nodes are also highlighted inside the workflow monitor via a blue outline.
2 Likes
I’d like to re-iterate the original request for a node ID lookup, and re-introduction of showing node numbers, which were very useful in the old UI.
I have multiple instances of the same component in one workflow. Our of several instances I had two failures (screenshot). And clicking on the → certainly took me to the failure, but I had no idea which component it was out of the several I had so I couldn’t any further troubleshooting. I ended up having to search across my entire workflow manually.
If the node number was listed, and if the search feature existed, then I’d be able to immediately go to it. These are sorely missed features that the old UI has.
Can we do a +1 to getting that re-added to the new UI please?
1 Like