Issue running multiple workflows in parallel via batch in KNIME 5.5.1 (works fine in 5.4.4)

[arddashti]

Hello,

I’ve recently upgraded from KNIME Analytics Platform 5.4.4 to 5.5.1, and I am experiencing a critical issue when running multiple workflows in parallel via batch execution.

• Environment:

  • Windows Server (running via SQL Server Agent + batch file)

  • KNIME Analytics Platform 5.5.1

  • Previously tested on 5.4.4 (no issues)

• Problem description:

  • When I launch multiple workflows in parallel (each in its own batch call) via SQL Server Agent, all KNIME processes close immediately and none of the workflows execute.

  • However, when running a single workflow (batch execution one by one), everything works fine.

  • This behavior did not occur in version 5.4.4.

• Troubleshooting already attempted:

  • Assigned unique -data (workspace) and -configuration directories for each batch execution.

  • Tried multiple separate KNIME installations (copied installation folders).

  • Still, in version 5.5.1, running workflows in parallel crashes immediately.

• Expected behavior:

  • Multiple workflows should be able to run in parallel, just like in version 5.4.4.

• Question:

  • Is this a known bug/limitation in 5.5.1?

  • Is there any workaround or fix (e.g., in 5.5.2 or later versions)?

Thank you in advance for your support!

[atiorile]

Hi @arddashti,

I made a comment about this issue at 📣 Out now: KNIME Analytics Platform 5.5 - #10 by atiorile

Here is a list of responses that may be useful to you:

Out now: KNIME Analytics Platform 5.5

We do offer scheduled workflow execution on KNIME Community Hub now, perhaps that’s something your employer could look into . The old Batch Execution mode is not being developed any more and may be decommissioned at some point in the future. Interesting! KNIME (and Eclipse) workspaces are not meant to be used from multiple applications simultaneously, and at least the desktop application does check for that and doesn’t allow you to open two instances with the same works…

Out now: KNIME Analytics Platform 5.5

We are experiencing the same problem, we get the below error: A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8653dac8f, pid=5172, tid=13952 JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8) Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64) Problematic frame: C [libcef.dll+0x468ac8f] If …

Out now: KNIME Analytics Platform 5.5

We also have this use case - running Knime workflows using batch executor - and faced the same issue with 5.5 with failures to start one workflow when another is still running. Workflows are scheduled to start at different times but it is not always possible to predict how long processing would take and some of them could overlap. Inability to execute multiple workflows via batch presents significant issue for us, at the moment we had downgraded back to 5.4 but would need to re-evaluate Knime us…

Out now: KNIME Analytics Platform 5.5

Hi @Sarah_rushton, hi @jmartinsonhr23, as @leo_woerteler already remarked, it’s most likely due to the ‘embedded browser’ (CEF). We initialize CEF on start-up which helps to prevent problems when CEF is initialized on demand later and memory is tight. But you can turn that off by setting the system property -Dorg.knime.js.cef.skip_windowless_chromium_initialization=true. Maybe that helps as workaround (provided you don’t use view-image-generation or report-generation - which needs CEF and will …