Niels Oertel

Probably related to this commit: neo4j/docker-neo4j@17c0acc598fab6765a5366164b056524eeaf8647 I will also raise a bug in the neo4j-docker repository.

Confirmed. Issue can be closed.

Actually the `controlTask` build in `AbstractParallelEoSStreamProcessor#controlTask` adds `myId` to the `MDC` before starting to run the `controlLoop`. However `processWorkCompleteMailBox` which is called from within every run of the `controlLoop` clears...

I also raised issue neo4j/neo4j#12914 but realized that the problem is more likely to be in the entrypoint script.

FYI: I have related ticket #20000 open with enterprise customer support.

Just an idea - not sure about side effects, though: ```bash #!/bin/bash function params_test() { echo "----------------------------------" for param in "$@"; do echo " '$param'" done echo "----------------------------------" } COMMAND='params_test...

Having given this some more thoughts, I think that #349 is conceptually wrong. Running this command: ```bash docker run --env=NEO4J_ACCEPT_LICENSE_AGREEMENT=yes --env=NEO4J_dbms_jvm_additional="'"'-Dhello=world$x'"' -Dfoo=bar" neo4j:4.4.9-enterprise ``` Leads to this entry in neo4j.conf...

I'm not sure what happened yesterday but today I can't reproduce the second issue - `ExecuteQueriesDelegate#mayBeReadWrite` correctly identifies the write operation and clears the session caches. The first issue however...

Exactly, `@DateLong` works with `Instant`, too - only in SDN 6 this support has been removed (although documentation still says it's supported). My issue however is not that I need...

Will test that. Just to be sure - you're talking about `ACCESS_MODE_DATA=r`, correct?