5.0.1 / Renders workflows unusable

[robert_m_muench]

When changing nodes, like selecting a different file to read from or pressing the node reset (whatever this does), KNIME becomes unresponsive and later can’t load the workflow any longer.

Is this a known problem or behavior? Is there a workaround to avoid this? I’m now doing manual backups after every couple of changes.

[AlexanderFillbrunn]

Hi,
This should not happen and I think it also does not happen for everyone, as I have worked with 5.0.1 just yesterday and did not encounter such problems. There are ways to debug this, if you are willing to, but you’d need to install a Java JDK from adoptium.net and then run the jstack command via command line while KNIME is frozen. This takes a snapshot of everything that is going on inside the program at the moment. If you could do that and share the result with us, it would help tremendously. Let me know if you need help with that.

As for the node reset: A node has 3 main states: unconfigured, configured, and executed. What each means:

• Unconfigured: The node is missing inputs to perform its task. That can be a missing connection or a missing configuration, such as an Excel Reader where no file path has been configured yet.
• Configured: The node has everything it needs to be executed, but it has not been executed yet.
• Executed: The node has been executed and data is available for subsequent nodes.

You get from one state to the other like so:

• Unconfigured → Configured by configuring the node and connecting all non-optional input ports
• Configured → Unconfigured by removing a non-optional input connection
• Configured → Executed by executing the node itself or any downstream node
• Executed → Configured by resetting the node or by changing the node configuration

The last state change is what the node reset does. It resets the node back to configured state so it can be executed again, potentially processing new data.
I hope this helps!
Kind regards,
Alexander