Component not finishing due to Table View Node

Feedback & Ideas
1

Hi,

I regenerated the latest reports for a client and found that, after several minutes, a component did not want to finish processing. Here is t he log:

2024-12-31 12:37:06,028 : ERROR : KNIME-Worker-283-Component Output 3:1471:0:1452:0:1383:0:2 :  : ReportPortObject : Component Output : 3:1471:0:1452:0:1383:0:2 : 
java.lang.InterruptedException
	at java.base/java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.base/java.util.concurrent.CompletableFuture.get(Unknown Source)
	at org.knime.js.cef.headless.CEFHeadlessUtil.generateContent(CEFHeadlessUtil.java:218)
	at org.knime.js.cef.headless.CEFHeadlessUtil.generateReport(CEFHeadlessUtil.java:136)
	at org.knime.reporting2.porttype.ReportPortObject.fromExecutedComponent(ReportPortObject.java:133)
	at org.knime.reporting2.ReportServiceImpl.createOutput(ReportServiceImpl.java:69)
	at org.knime.core.node.port.report.ReportUtil.lambda$0(ReportUtil.java:94)
	at java.base/java.util.Optional.map(Unknown Source)
	at org.knime.core.node.port.report.ReportUtil.computeReportObject(ReportUtil.java:94)
	at org.knime.core.node.workflow.virtual.subnode.VirtualSubNodeOutputNodeModel.execute(VirtualSubNodeOutputNodeModel.java:178)
	at org.knime.core.node.NodeModel.executeModel(NodeModel.java:596)
	at org.knime.core.node.ExtendedScopeNodeModel.executeModel(ExtendedScopeNodeModel.java:86)
	at org.knime.core.node.workflow.virtual.subnode.VirtualSubNodeOutputNodeModel.executeModel(VirtualSubNodeOutputNodeModel.java:162)
	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)
2024-12-31 12:37:06,028 : WARN  : KNIME-Worker-283-Component Output 3:1471:0:1452:0:1383:0:2 :  : Node : Component Output : 3:1471:0:1452:0:1383:0:2 : Execution canceled

image
image1361×1214 68.1 KB

Here the thread dump:

241231 Knime 5-4 Table View prevents component ouput from finishing threaddump-1735656074043.tdump.txt (65.0 KB)

I recon that I brought the issue of not finishing components which contain interactive views up once (quite some time ago) but could not find the topic.

PS: Executing just the component output after aborting the execution, worked without throwing any error. Worth to note that my outer loop looks like so, generating one large YoY Interactive View:

image
image1251×404 19.6 KB

Best
Mike

2

Hey @mwiegand,

Sorry for the late response. Indeed the table view can cause problems when you render large amounts of rows as it would run into the default timeout set for the reporting. We increased this default quiet a bit with a recent version. (Currently don’t remember which version and the exact amount)
There is a vm parameter that you can set to increase that timeout org.knime.reporting2.report_generation_timeout_seconds=x

Greetings,
Daniel

3 Likes
3

No probs @DanielBog and thanks for still picking this up. I will rerun the workflow in question tomorrow and see if the issue still persists.

If a timeout is hit, would it be possible to make that obvious in the console? It would give Knimers the opportunity to search for a solution like your suggestion as this doesn’t seem to be a bug per se.

Cheers
Mike

1 Like