[jira] [Updated] (NIFI-7544) ReplaceText processor seems not thread-safe?
[ https://issues.apache.org/jira/browse/NIFI-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milco Numan updated NIFI-7544: -- Attachment: ReplaceText-Configuration.png > ReplaceText processor seems not thread-safe? > > > Key: NIFI-7544 > URL: https://issues.apache.org/jira/browse/NIFI-7544 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.11.4 > Environment: Red Hat Enterprise Linux 7.8 > openjdk version "11.0.7" 2020-04-14 LTS > OpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing) >Reporter: Milco Numan >Priority: Major > Attachments: ReplaceText-Configuration.png, apache-nifi.txt > > > We have a flow where there are separate flow files containing a single > string. We use the ReplaceText processor to prepend this string by a > parameter name (for use in an actual URI, as query parameter) and postfix the > string by an ampersand: > When using this processor with number of concurrrent tasks > 1 (4 in our > case), we have seen it happening that content of file-A is inserted as the > result of file-B, it seems as if the process is not thread safe where the > actual search value is captured. > We can see from the logfile (created by inserting LogAttribute processors > logging uuid and the actual content after all steps in the process) that the > input of one file is overwritten with the search/replace pattern of another > file (just before it), see uploaded log file > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7544) ReplaceText processor seems not thread-safe?
[ https://issues.apache.org/jira/browse/NIFI-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milco Numan updated NIFI-7544: -- Attachment: apache-nifi.txt > ReplaceText processor seems not thread-safe? > > > Key: NIFI-7544 > URL: https://issues.apache.org/jira/browse/NIFI-7544 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.11.4 > Environment: Red Hat Enterprise Linux 7.8 > openjdk version "11.0.7" 2020-04-14 LTS > OpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing) >Reporter: Milco Numan >Priority: Major > Attachments: apache-nifi.txt > > > We have a flow where there are separate flow files containing a single > string. We use the ReplaceText processor to prepend this string by a > parameter name (for use in an actual URI, as query parameter) and postfix the > string by an ampersand: > When using this processor with number of concurrrent tasks > 1 (4 in our > case), we have seen it happening that content of file-A is inserted as the > result of file-B, it seems as if the process is not thread safe where the > actual search value is captured. > We can see from the logfile (created by inserting LogAttribute processors > logging uuid and the actual content after all steps in the process) that the > input of one file is overwritten with the search/replace pattern of another > file (just before it), see uploaded log file > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7544) ReplaceText processor seems not thread-safe?
Milco Numan created NIFI-7544: - Summary: ReplaceText processor seems not thread-safe? Key: NIFI-7544 URL: https://issues.apache.org/jira/browse/NIFI-7544 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.11.4 Environment: Red Hat Enterprise Linux 7.8 openjdk version "11.0.7" 2020-04-14 LTS OpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing) Reporter: Milco Numan We have a flow where there are separate flow files containing a single string. We use the ReplaceText processor to prepend this string by a parameter name (for use in an actual URI, as query parameter) and postfix the string by an ampersand: When using this processor with number of concurrrent tasks > 1 (4 in our case), we have seen it happening that content of file-A is inserted as the result of file-B, it seems as if the process is not thread safe where the actual search value is captured. We can see from the logfile (created by inserting LogAttribute processors logging uuid and the actual content after all steps in the process) that the input of one file is overwritten with the search/replace pattern of another file (just before it), see uploaded log file -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7391) Suppress illegal access warnings in nifi-bootstrap.log
Milco Numan created NIFI-7391: - Summary: Suppress illegal access warnings in nifi-bootstrap.log Key: NIFI-7391 URL: https://issues.apache.org/jira/browse/NIFI-7391 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.11.4 Environment: RHEL 7.7 openjdk version "11.0.6" 2020-01-14 LTS OpenJDK Runtime Environment 18.9 (build 11.0.6+10-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.6+10-LTS, mixed mode, sharing) Nifi 1.11.4 Reporter: Milco Numan When starting NiFi, we're running into WARNINGs/ERRORs due to illegal accesses of certain classes. It's not only the JAXB classes (these can be suppressed), but if we supress these using '-Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true', we'll get the next one First message: _2020-04-23 16:51:34,267 INFO [main] org.apache.nifi.bootstrap.Command Command: /usr/lib/jvm/java-11-openjdk-11.0.6.10-1.el7_7.x86_64/bin/java -classpath /var/opt/nifi_current/conf:/var/opt/nifi_current/lib/javax.servlet-api-3.1.0.jar:/var/opt/nifi_current/lib/jetty-schemas-3.1.jar:/var/opt/nifi_current/lib/logback-classic-1.2.3.jar:/var/opt/nifi_current/lib/logback-core-1.2.3.jar:/var/opt/nifi_current/lib/jcl-over-slf4j-1.7.30.jar:/var/opt/nifi_current/lib/jul-to-slf4j-1.7.30.jar:/var/opt/nifi_current/lib/log4j-over-slf4j-1.7.30.jar:/var/opt/nifi_current/lib/slf4j-api-1.7.30.jar:/var/opt/nifi_current/lib/nifi-api-1.11.4.jar:/var/opt/nifi_current/lib/nifi-framework-api-1.11.4.jar:/var/opt/nifi_current/lib/nifi-runtime-1.11.4.jar:/var/opt/nifi_current/lib/nifi-nar-utils-1.11.4.jar:/var/opt/nifi_current/lib/nifi-properties-1.11.4.jar:/var/opt/nifi_current/lib/java11/jaxb-api-2.3.0.jar:/var/opt/nifi_current/lib/java11/jaxb-impl-2.3.0.jar:/var/opt/nifi_current/lib/java11/jaxb-core-2.3.0.jar:/var/opt/nifi_current/lib/java11/javax.annotation-api-1.3.2.jar:/var/opt/nifi_current/lib/java11/javax.activation-api-1.2.0.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx8g -Xms8g -Dzookeeper.admin.enableServer=false -Djavax.security.auth.useSubjectCredsOnly=true -Djava.security.egd=file:/dev/urandom -Djava.security.krb5.conf=./conf/krb5.conf -Djava.security.auth.login.config=./conf/jaas.conf -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Dorg.xerial.snappy.tempdir=/var/opt/nifi_tmp -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -XX:+UseG1GC -Dnifi.properties.file.path=/var/opt/nifi_current/conf/nifi.properties -Dnifi.bootstrap.listen.port=17260 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=/var/opt/nifi_log org.apache.nifi.NiFi_ _2020-04-23 16:51:34,286 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 31822_ _2020-04-23 16:51:34,852 INFO [NiFi Bootstrap Command Listener] org.apache.nifi.bootstrap.RunNiFi Apache NiFi now running and listening for Bootstrap requests on port 34968_ _2020-04-23 16:51:42,618 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: An illegal reflective access operation has occurred_ _2020-04-23 16:51:42,619 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (file:/var/opt/nifi-1.11.4/lib/java11/jaxb-impl-2.3.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)_ _2020-04-23 16:51:42,619 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector_ _2020-04-23 16:51:42,619 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations_ _2020-04-23 16:51:42,619 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: All illegal access operations will be denied in a future release_ Second message: _2020-04-23 16:24:13,962 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: An illegal reflective access operation has occurred_ _2020-04-23 16:24:13,962 ERROR [NiFi logging handler] org.apache.nifi.StdErr WARNING: Illegal reflective access by org.xerial.snappy.SnappyLoader (file:/var/opt/nifi_current/work/nar/extensions/nifi-hive-nar-1.11.4.nar-unpacked/NAR-INF/bundled-dependencies/snappy-java-1.0.5.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)_ -- This message was sent by Atlassian Jira (v8.3.4#803005)
