dgorman jvmConnectors is a core component for native Connectors (vs generic ODBC/JDBC/OLE/etc) so likely a good chance you are using it. I checked with the Support team and they passed this along if you are not using a WAF...If you need additional help with this you can open a ticket here: https://support.sisense.com/kb/en/contact
For Linux version L2021.0 and up
Run commands below and restart build, query and management pods afterward.
curl --request POST -H 'Content-Type: application/json' http://$(kubectl get pods -n sisense -o wide | grep -E configuration-.*`hostname`| awk '{print $6;exit}'):3030/configurations/service/query --data '{"JavaOptions.value":"-Dlog4j2.formatMsgNoLookups=true","JavaOptions.setbyuser":true}'
curl --request POST -H 'Content-Type: application/json' http://$(kubectl get pods -n sisense -o wide | grep -E configuration-.*`hostname`| awk '{print $6;exit}'):3030/configurations/service/build --data '{"JavaOptions.value":"-Dlog4j2.formatMsgNoLookups=true","JavaOptions.setbyuser":true}'
curl --request POST -H 'Content-Type: application/json' http://$(kubectl get pods -n sisense -o wide | grep -E configuration-.*`hostname`| awk '{print $6;exit}'):3030/configurations/service/management --data '{"JavaOptions.value":"-Dlog4j2.formatMsgNoLookups=true","JavaOptions.setbyuser":true}'
curl --request POST -H 'Content-Type: application/json' http://$(kubectl get pods -n sisense -o wide | grep -E configuration-.*`hostname`| awk '{print $6;exit}'):3030/configurations/service/build-connector --data '{"JavaOptions.value":"-XX:+UseParallelGC -Dlog4j2.formatMsgNoLookups=true","JavaOptions.setbyuser":true}'