from:"Byunghwa Yun \(JIRA\)"

[jira] [Commented] (NIFI-3425) Cache prepared statements in PutCassandraQL

2017-02-15 Thread Byunghwa Yun (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867650#comment-15867650
 ] 

Byunghwa Yun commented on NIFI-3425:


[~mattyb149]
Could you apply this patch to the main branch?
Thank you.

> Cache prepared statements in PutCassandraQL
> ---
>
> Key: NIFI-3425
> URL: https://issues.apache.org/jira/browse/NIFI-3425
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Matt Burgess
>Priority: Minor
> Attachments: NIFI-3425.patch
>
>
> Currently PutCassandraQL supports prepared statements (using ? parameters 
> much like JDBC SQL statements) via flow file attributes specifying the type 
> and value of the parameters.
> However, the prepared statement is created (and thus possibly re-created) for 
> each flow file, which neuters its effectiveness over literal CQL statements. 
> The driver warns of this:
> 2017-01-31 14:30:54,287 WARN [cluster1-worker-1] 
> com.datastax.driver.core.Cluster Re-preparing already prepared query insert 
> into test_table (id, timestamp, id1, timestamp1, id
> 2, timestamp2, id3, timestamp3, id4, timestamp4, id5, timestamp5, id6, 
> timestamp6) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);. Please note 
> that preparing the same query
>  more than once is generally an anti-pattern and will likely affect 
> performance. Consider preparing the statement only once.
> Prepared statements should be cached and reused where possible.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

2016-10-04 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2867:
--

 Summary: The ColumnSize of datetime type is 19 length in MySQL 
JDBC.
 Key: NIFI-2867
 URL: https://issues.apache.org/jira/browse/NIFI-2867
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.1.0
Reporter: Byunghwa Yun
Priority: Minor


When I use the ConvertJSONToSQL, it changes the field value for data capacity 
of source datastore.

/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
 430
if (colSize != null && fieldValue.length() > colSize) {
fieldValue = fieldValue.substring(0, colSize);
}

But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
size. So above code truncate field value to 2016-10-05 12:00:00 from 2016-10-05 
12:00:00.0.
PuSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
SimpleDateFormat. So it throws below exception.

2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
o.apache.nifi.processors.standard.PutSQL
org.apache.nifi.processor.exception.ProcessException: The value of the 
sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
timestamp
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_51]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
Caused by: java.text.ParseException: Unparseable date: "2016-10-05 13:05:43"
at java.text.DateFormat.parse(DateFormat.java:366) ~[na:1.8.0_51]
at 
org.apache.nifi.processors.standard.PutSQL.setParameter(PutSQL.java:798) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:626) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
... 13 common frames omitted

Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2867:
---
Description: 
When I use the ConvertJSONToSQL, it changes the field value for data capacity 
of source datastore.

/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
 430
if (colSize != null && fieldValue.length() > colSize) {
fieldValue = fieldValue.substring(0, colSize);
}

But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
size. So above code truncate field value to 2016-10-05 12:00:00 from 2016-10-05 
12:00:00.0.
PutSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
SimpleDateFormat. So it throws below exception.

2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
o.apache.nifi.processors.standard.PutSQL
org.apache.nifi.processor.exception.ProcessException: The value of the 
sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
timestamp
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_51]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
Caused by: java.text.ParseException: Unparseable date: "2016-10-05 13:05:43"
at java.text.DateFormat.parse(DateFormat.java:366) ~[na:1.8.0_51]
at 
org.apache.nifi.processors.standard.PutSQL.setParameter(PutSQL.java:798) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:626) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
... 13 common frames omitted

Thank you.

  was:
When I use the ConvertJSONToSQL, it changes the field value for data capacity 
of source datastore.

/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
 430
if (colSize != null && fieldValue.length() > colSize) {
fieldValue = fieldValue.substring(0, colSize);
}

But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
size. So above code truncate field value to 2016-10-05 12:00:00 from 2016-10-05 
12:00:00.0.
PuSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
SimpleDateFormat. So it throws below exception.

2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
o.apache.nifi.processors.standard.PutSQL
org.apache.nifi.processor.exception.ProcessException: The value of the 
sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
timestamp
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)

[jira] [Updated] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2867:
---
Description: 
When I use the ConvertJSONToSQL, it changes the field value for data capacity 
of source datastore.

/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
 430 line
if (colSize != null && fieldValue.length() > colSize) {
fieldValue = fieldValue.substring(0, colSize);
}

But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
size. So above code truncate field value to 2016-10-05 12:00:00 from 2016-10-05 
12:00:00.0.
PutSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
SimpleDateFormat. So it throws below exception.

2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
o.apache.nifi.processors.standard.PutSQL
org.apache.nifi.processor.exception.ProcessException: The value of the 
sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
timestamp
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_51]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
Caused by: java.text.ParseException: Unparseable date: "2016-10-05 13:05:43"
at java.text.DateFormat.parse(DateFormat.java:366) ~[na:1.8.0_51]
at 
org.apache.nifi.processors.standard.PutSQL.setParameter(PutSQL.java:798) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:626) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
... 13 common frames omitted

Thank you.

  was:
When I use the ConvertJSONToSQL, it changes the field value for data capacity 
of source datastore.

/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
 430
if (colSize != null && fieldValue.length() > colSize) {
fieldValue = fieldValue.substring(0, colSize);
}

But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
size. So above code truncate field value to 2016-10-05 12:00:00 from 2016-10-05 
12:00:00.0.
PutSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
SimpleDateFormat. So it throws below exception.

2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
o.apache.nifi.processors.standard.PutSQL
org.apache.nifi.processor.exception.ProcessException: The value of the 
sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
timestamp
at 
org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns zero or a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Description: 
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns zero or a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is zero or a negative value, it 
skips setting setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think when getSystemLoadAverage returns a negative value, systemLoad sets 
-1.0 and returns zero, systemLoad sets zero.

Thank you.

  was:
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns zero or a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Summary: getSystemLoadAverage of OperatingSystemMXBean sometimes returns 
zero or a negative value.  (was: getSystemLoadAverage of OperatingSystemMXBean 
sometimes returns a negative value.)

> getSystemLoadAverage of OperatingSystemMXBean sometimes returns zero or a 
> negative value.
> -
>
> Key: NIFI-2858
> URL: https://issues.apache.org/jira/browse/NIFI-2858
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>
> When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
> exception.
> So, I was tracking that exception to find a problem that getSystemLoadAverage 
> of OperatingSystemMXBean sometimes returns a negative value.
> 2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
> java.lang.NullPointerException. Returning Internal Server Error response.
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
> ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
> ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
>  ~[classes/:na]
> at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
> ~[na:na]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_51]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>  [jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>  [jersey-server-1.19.jar:1.19]
> at 
>

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2866:
---
Description: 
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

When I set the property that is initial.maxvalue.UPDATE_TIME, 
QueryDatabaseTable doesn't have WHERE cause with UPDATE_TIME.
Thanks.

  was:
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

When I set the property that is initial.maxvalue.UPDATE_TIME, 
QueryDatabaseTable doesn't have where cause with UPDATE_TIME.
Thanks.


> The Initial Max Value of QueryDatabaseTable won't be case sensitive.
> 
>
> Key: NIFI-2866
> URL: https://issues.apache.org/jira/browse/NIFI-2866
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>Priority: Minor
>
> Now, the Initial Max Value of QueryDatabaseTable is allowed the only 
> lowercase so I think to change the below code, it added .toLowerCase() method.
> for(final Map.Entry maxProp : 
> maxValueProperties.entrySet()){
> if 
> (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
> statePropertyMap.put(maxProp.getKey().toLowerCase(), 
> maxProp.getValue());
> }
> }
> When I set the property that is initial.maxvalue.UPDATE_TIME, 
> QueryDatabaseTable doesn't have WHERE cause with UPDATE_TIME.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2866:
---
Description: 
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

When I set the property that is initial.maxvalue.UPDATE_TIME, 
QueryDatabaseTable doesn't have where cause with UPDATE_TIME.
Thanks.

  was:
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

Thanks.


> The Initial Max Value of QueryDatabaseTable won't be case sensitive.
> 
>
> Key: NIFI-2866
> URL: https://issues.apache.org/jira/browse/NIFI-2866
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>Priority: Minor
>
> Now, the Initial Max Value of QueryDatabaseTable is allowed the only 
> lowercase so I think to change the below code, it added .toLowerCase() method.
> for(final Map.Entry maxProp : 
> maxValueProperties.entrySet()){
> if 
> (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
> statePropertyMap.put(maxProp.getKey().toLowerCase(), 
> maxProp.getValue());
> }
> }
> When I set the property that is initial.maxvalue.UPDATE_TIME, 
> QueryDatabaseTable doesn't have where cause with UPDATE_TIME.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

2016-10-04 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2866:
--

 Summary: The Initial Max Value of QueryDatabaseTable won't be case 
sensitive.
 Key: NIFI-2866
 URL: https://issues.apache.org/jira/browse/NIFI-2866
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.1.0
Reporter: Byunghwa Yun
Priority: Minor


Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2866:
---
Description: 
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

When I set the property that is initial.maxvalue.UPDATE_TIME, 
QueryDatabaseTable doesn't have WHERE clause with UPDATE_TIME.
Thanks.

  was:
Now, the Initial Max Value of QueryDatabaseTable is allowed the only lowercase 
so I think to change the below code, it added .toLowerCase() method.

for(final Map.Entry maxProp : 
maxValueProperties.entrySet()){
if (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
statePropertyMap.put(maxProp.getKey().toLowerCase(), 
maxProp.getValue());
}
}

When I set the property that is initial.maxvalue.UPDATE_TIME, 
QueryDatabaseTable doesn't have WHERE cause with UPDATE_TIME.
Thanks.


> The Initial Max Value of QueryDatabaseTable won't be case sensitive.
> 
>
> Key: NIFI-2866
> URL: https://issues.apache.org/jira/browse/NIFI-2866
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>Priority: Minor
>
> Now, the Initial Max Value of QueryDatabaseTable is allowed the only 
> lowercase so I think to change the below code, it added .toLowerCase() method.
> for(final Map.Entry maxProp : 
> maxValueProperties.entrySet()){
> if 
> (!statePropertyMap.containsKey(maxProp.getKey().toLowerCase())) {
> statePropertyMap.put(maxProp.getKey().toLowerCase(), 
> maxProp.getValue());
> }
> }
> When I set the property that is initial.maxvalue.UPDATE_TIME, 
> QueryDatabaseTable doesn't have WHERE clause with UPDATE_TIME.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2811) JdbcCommon doesn't convert bigint(20) column.

2016-09-23 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2811:
--

 Summary: JdbcCommon doesn't convert bigint(20) column.
 Key: NIFI-2811
 URL: https://issues.apache.org/jira/browse/NIFI-2811
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Byunghwa Yun


JdbcCommon doesn't convert SQL-to-Avro that has bigint(20) column with the 
small value.
Even column type is BIGINT(20), MySQL JDBC driver can return number type value 
when the return value is small.

Related Exception: 
2016-09-23 10:50:22,191 ERROR [Timer-Driven Process Thread-8] 
o.a.n.p.standard.QueryDatabaseTable
org.apache.nifi.processor.exception.ProcessException: Error during database 
query or conversion of records to Avro.
at 
org.apache.nifi.processors.standard.QueryDatabaseTable.lambda$onTrigger$0(QueryDatabaseTable.java:255)
 ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.QueryDatabaseTable$$Lambda$132/464322944.process(Unknown
 Source) ~[na:na]
at 
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:2123)
 ~[nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.QueryDatabaseTable.onTrigger(QueryDatabaseTable.java:249)
 ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_51]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_51]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_51]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_51]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
Caused by: org.apache.avro.file.DataFileWriter$AppendWriteException: 
org.apache.avro.UnresolvedUnionException: Not in union ["null","string"]: 936398
at org.apache.avro.file.DataFileWriter.append(DataFileWriter.java:296) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.nifi.processors.standard.util.JdbcCommon.convertToAvroStream(JdbcCommon.java:207)
 ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.processors.standard.QueryDatabaseTable.lambda$onTrigger$0(QueryDatabaseTable.java:253)
 ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
... 14 common frames omitted
Caused by: org.apache.avro.UnresolvedUnionException: Not in union 
["null","string"]: 936398
at 
org.apache.avro.generic.GenericData.resolveUnion(GenericData.java:604) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.resolveUnion(GenericDatumWriter.java:151)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:71) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.writeField(GenericDatumWriter.java:114)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.writeRecord(GenericDatumWriter.java:104)
 ~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:66) 
~[avro-1.7.7.jar:1.7.7]
at 
org.apache.avro.generic.GenericDatumWriter.write(GenericDatumWriter.java:58) 
~[avro-1.7.7.jar:1.7.7]
at org.apache.avro.file.DataFileWriter.append(DataFileWriter.java:290) 
~[avro-1.7.7.jar:1.7.7]
... 16 common frames omitted




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

2016-09-22 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2803:
--

 Summary: The pagination of GenerateTableFetch has a sort bug.
 Key: NIFI-2803
 URL: https://issues.apache.org/jira/browse/NIFI-2803
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Byunghwa Yun


When data is coming to the ingested table, the pagination SQL needs the ORDER 
BY statement with maxValueClauses.
If maxValueClauses are not the primary keys, incoming data usually inserts  
using primary keys. So when ExecuteSQL executes, some data may be lost.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-2802) The implementation classes don't support orderByClause.

2016-09-22 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2802:
--

 Summary: The implementation classes don't support orderByClause.
 Key: NIFI-2802
 URL: https://issues.apache.org/jira/browse/NIFI-2802
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 1.0.0
Reporter: Byunghwa Yun
Priority: Minor


The implementation classes don't support orderByClause.
The below code is the part of GenericDatabaseAdapter class(even 
OracleDatabaseAdapter and DerbyDatabaseAdapter).

if (!StringUtils.isEmpty(orderByClause)) {
query.append(" ORDER BY ");
query.append(whereClause);
}

Expected:
if (!StringUtils.isEmpty(orderByClause)) {
query.append(" ORDER BY ");
query.append(orderByClause);
}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Description: 
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is negative, it skips setting 
setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think when 
to set systemLoad even a negative value.

Thank you.

  was:
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred:

[jira] [Created] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-2858:
--

 Summary: getSystemLoadAverage of OperatingSystemMXBean sometimes 
returns a negative value.
 Key: NIFI-2858
 URL: https://issues.apache.org/jira/browse/NIFI-2858
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.0.0
Reporter: Byunghwa Yun


When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is negative, it skips setting 
setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think to set systemLoad even a negative value.

Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Description: 
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is negative, it skips setting 
setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think when getSystemLoadAverage returns a nagative value, it sets 1.

Thank you.

  was:
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Description: 
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is negative, it skips setting 
setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think when getSystemLoadAverage returns a negative value, systemLoad sets 1.

Thank you.

  was:
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Description: 
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
 ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
at 
org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
 ~[classes/:na]
at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
~[na:na]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_51]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
 ~[jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
 [jersey-server-1.19.jar:1.19]
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
 [jersey-server-1.19.jar:1.19]


When systemLoad of SystemDiagnosticsFactory is negative, it skips setting 
setProcessorLoadAverage of SystemDiagnostics.

if (systemLoad > 0) {
systemDiagnostics.setProcessorLoadAverage(systemLoad);
}

I think when getSystemLoadAverage returns a negative value, systemLoad sets 
-1.0.

Thank you.

  was:
When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
exception.
So, I was tracking that exception to find a problem that getSystemLoadAverage 
of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

2016-10-04 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-2858:
---
Affects Version/s: (was: 1.0.0)
   1.1.0

> getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative 
> value.
> -
>
> Key: NIFI-2858
> URL: https://issues.apache.org/jira/browse/NIFI-2858
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>
> When NiFi cluster is busy, Sometimes Cluster of Global Menu throws below an 
> exception.
> So, I was tracking that exception to find a problem that getSystemLoadAverage 
> of OperatingSystemMXBean sometimes returns a negative value.
> 2016-10-04 14:53:20,488 ERROR [NiFi Web Server-40942] 
> o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
> java.lang.NullPointerException. Returning Internal Server Error response.
> java.lang.NullPointerException: null
> at 
> org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:576) 
> ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.manager.StatusMerger.merge(StatusMerger.java:548) 
> ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:69)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.SystemDiagnosticsEndpointMerger.mergeResponses(SystemDiagnosticsEndpointMerger.java:31)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.StandardHttpResponseMerger.mergeResponses(StandardHttpResponseMerger.java:179)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.getMergedResponse(StandardAsyncClusterResponse.java:145)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.cluster.coordination.http.replication.StandardAsyncClusterResponse.awaitMergedResponse(StandardAsyncClusterResponse.java:160)
>  ~[nifi-framework-cluster-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.web.api.SystemDiagnosticsResource.getSystemDiagnostics(SystemDiagnosticsResource.java:141)
>  ~[classes/:na]
> at sun.reflect.GeneratedMethodAccessor988.invoke(Unknown Source) 
> ~[na:na]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_51]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_51]
> at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>  ~[jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>  [jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>  [jersey-server-1.19.jar:1.19]
> at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>  [jersey-server-1.19.jar:1.19]
> When systemLoad of

[jira] [Created] (NIFI-3027) ExecuteProcess supports the expression language

2016-11-11 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-3027:
--

 Summary: ExecuteProcess supports the expression language
 Key: NIFI-3027
 URL: https://issues.apache.org/jira/browse/NIFI-3027
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Affects Versions: 1.1.0
Reporter: Byunghwa Yun
Priority: Minor


When ExecuteProcess executed with specified time argument, I needed the 
expression language like below.
e.g.)
Command: /home/hadoop/hive/bin/hive
Command Arguments: -e;ALTER TABLE TAB1 ADD IF NOT EXISTS PARTITION 
(LOG_DATE='${now():toNumber():plus(360):format('MMdd')}', 
LOG_HOUR='${now():toNumber():plus(360):format('HH')}')
Argument Delimiter: ;

Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3185) ConvertJSONToSQL supports UPSERT type

2016-12-12 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-3185:
--

 Summary: ConvertJSONToSQL supports UPSERT type
 Key: NIFI-3185
 URL: https://issues.apache.org/jira/browse/NIFI-3185
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Reporter: Byunghwa Yun
Priority: Minor


ConvertJSONToSQL supports UPSERT type.
Phonex doesn't support INSERT SQL statement.
Only this supports UPSERT SQL statement. I think this statement is not ANSI SQL 
but ReplaceText is so slow after ConvertJSONToSQL.
So I hope that ConvertJSONToSQL supports UPSERT statement.

Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

2017-04-05 Thread Byunghwa Yun (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958200#comment-15958200
 ] 

Byunghwa Yun commented on NIFI-3673:


[~bende]
I applied this 
https://patch-diff.githubusercontent.com/raw/apache/nifi/pull/1635.patch base 
master branch but I got the same exception still.
I confirmed to add cloneAncestorResources in RequiresInstanceClassLoading 
annotation.

Thanks for your comment.

> Loads the different class in classloader when Bumping NAR plugin
> 
>
> Key: NIFI-3673
> URL: https://issues.apache.org/jira/browse/NIFI-3673
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Byunghwa Yun
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> When I use master branch, Hadoop processor throws the exception related 
> ClassLoader.
> 2017-04-05 17:58:47,391 ERROR [StandardProcessScheduler Thread-1] 
> o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method 
> due to java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1466)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode.access$000(StandardProcessorNode.java:98)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1287)
>  ~[na:na]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> [na:1.8.0_101]
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1449)
>  ~[na:na]
> ... 9 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_101]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1291)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1287)
>  ~[na:na]
> ... 6 common frames omitted
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: class 
> org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not 
> org.apache.hadoop.security.GroupMappingServiceProvider
> at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2231) 
> ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:78) ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:74) ~[na:na]
> at 
> org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:303)
>  ~[na:na]
> at 
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
>  ~[na:na]
> at 
>

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

2017-04-13 Thread Byunghwa Yun (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967258#comment-15967258
 ] 

Byunghwa Yun commented on NIFI-3673:


[~bende] It's working. Thanks for your efforts.
But I got the another classloader problem. NiFi doesn't load the hadoop native 
library.
I attach the log. Thank you.

2017-04-13 16:49:26,430 DEBUG [StandardProcessScheduler Thread-6] 
org.apache.hadoop.util.NativeCodeLoader Trying to load the custom-built 
native-hadoop library...
2017-04-13 16:49:26,430 DEBUG [StandardProcessScheduler Thread-6] 
org.apache.hadoop.util.NativeCodeLoader Failed to load native-hadoop with 
error: java.lang.UnsatisfiedLinkError: Native Library 
/home/hadoop/hadoop-2.6.0-cdh5.5.1/lib/native/libhadoop.so already loaded in 
another classloader
2017-04-13 16:49:26,430 DEBUG [StandardProcessScheduler Thread-6] 
org.apache.hadoop.util.NativeCodeLoader 
java.library.path=/home/hadoop/hdfs/lib/native
2017-04-13 16:49:26,430 WARN [StandardProcessScheduler Thread-6] 
org.apache.hadoop.util.NativeCodeLoader Unable to load native-hadoop library 
for your platform... using builtin-java classes where applicable


> Loads the different class in classloader when Bumping NAR plugin
> 
>
> Key: NIFI-3673
> URL: https://issues.apache.org/jira/browse/NIFI-3673
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Byunghwa Yun
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> When I use master branch, Hadoop processor throws the exception related 
> ClassLoader.
> 2017-04-05 17:58:47,391 ERROR [StandardProcessScheduler Thread-1] 
> o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method 
> due to java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1466)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode.access$000(StandardProcessorNode.java:98)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1287)
>  ~[na:na]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> [na:1.8.0_101]
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1449)
>  ~[na:na]
> ... 9 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_101]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1291)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1287)
>  ~[na:na]
> ... 6 common frames omitted
> Caused by: java.lang.RuntimeException:

[jira] [Created] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

2017-04-05 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-3673:
--

 Summary: Loads the different class in classloader when Bumping NAR 
plugin
 Key: NIFI-3673
 URL: https://issues.apache.org/jira/browse/NIFI-3673
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Byunghwa Yun


When I use master branch, Hadoop processor throws the exception related 
ClassLoader.

2017-04-05 17:58:47,391 ERROR [StandardProcessScheduler Thread-1] 
o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method due 
to java.lang.RuntimeException: Failed while executing one of processor's 
OnScheduled task.
java.lang.RuntimeException: Failed while executing one of processor's 
OnScheduled task.
at 
org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1466)
 ~[na:na]
at 
org.apache.nifi.controller.StandardProcessorNode.access$000(StandardProcessorNode.java:98)
 ~[na:na]
at 
org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1287)
 ~[na:na]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_101]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[na:1.8.0_101]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_101]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 [na:1.8.0_101]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_101]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_101]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
Caused by: java.util.concurrent.ExecutionException: 
java.lang.reflect.InvocationTargetException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
[na:1.8.0_101]
at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
[na:1.8.0_101]
at 
org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1449)
 ~[na:na]
... 9 common frames omitted
Caused by: java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[na:1.8.0_101]
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
~[na:1.8.0_101]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[na:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
at 
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
 ~[na:na]
at 
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
 ~[na:na]
at 
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
 ~[na:na]
at 
org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
 ~[na:na]
at 
org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1291)
 ~[na:na]
at 
org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1287)
 ~[na:na]
... 6 common frames omitted
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: class 
org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not 
org.apache.hadoop.security.GroupMappingServiceProvider
at 
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2231) ~[na:na]
at org.apache.hadoop.security.Groups.(Groups.java:78) ~[na:na]
at org.apache.hadoop.security.Groups.(Groups.java:74) ~[na:na]
at 
org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:303)
 ~[na:na]
at 
org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
 ~[na:na]
at 
org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:311)
 ~[na:na]
at 
org.apache.nifi.hadoop.SecurityUtil.loginSimple(SecurityUtil.java:70) ~[na:na]
at 
org.apache.nifi.processors.hadoop.AbstractHadoopProcessor.resetHDFSResources(AbstractHadoopProcessor.java:300)
 ~[na:na]
at 
org.apache.nifi.processors.hadoop.AbstractHadoopProcessor.abstractOnScheduled(AbstractHadoopProcessor.java:228)
 ~[na:na]
at 
org.apache.nifi.processors.hadoop.GetHDFS.onScheduled(GetHDFS.java:236) ~[na:na]
... 16 common frames omitted
Caused by: java.lang.RuntimeException: class 
org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not 
org.apache.hadoop.security.GroupMappingServiceProvider
at

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

2017-04-05 Thread Byunghwa Yun (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956673#comment-15956673
 ] 

Byunghwa Yun commented on NIFI-3673:


[~bbende] 
Could you check this issue?
Thanks for your efforts.


> Loads the different class in classloader when Bumping NAR plugin
> 
>
> Key: NIFI-3673
> URL: https://issues.apache.org/jira/browse/NIFI-3673
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Byunghwa Yun
>
> When I use master branch, Hadoop processor throws the exception related 
> ClassLoader.
> 2017-04-05 17:58:47,391 ERROR [StandardProcessScheduler Thread-1] 
> o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method 
> due to java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1466)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode.access$000(StandardProcessorNode.java:98)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1287)
>  ~[na:na]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> [na:1.8.0_101]
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1449)
>  ~[na:na]
> ... 9 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_101]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1291)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1287)
>  ~[na:na]
> ... 6 common frames omitted
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: class 
> org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not 
> org.apache.hadoop.security.GroupMappingServiceProvider
> at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2231) 
> ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:78) ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:74) ~[na:na]
> at 
> org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:303)
>  ~[na:na]
> at 
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
>  ~[na:na]
> at 
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:311)
>  ~[na:na]
> at 
> org.apache.nifi.hadoop.SecurityUtil.loginSimple(SecurityUtil.java:70) ~[na:na]
> at 
> org.apache.nifi.processors.hadoop.AbstractHadoopProcessor.resetHDFSResources(AbstractHadoopProcessor.java:300)
>  ~[na:na]
> at 
>

[jira] [Updated] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

2017-04-18 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun updated NIFI-3673:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Loads the different class in classloader when Bumping NAR plugin
> 
>
> Key: NIFI-3673
> URL: https://issues.apache.org/jira/browse/NIFI-3673
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Byunghwa Yun
>Assignee: Bryan Bende
> Fix For: 1.2.0
>
>
> When I use master branch, Hadoop processor throws the exception related 
> ClassLoader.
> 2017-04-05 17:58:47,391 ERROR [StandardProcessScheduler Thread-1] 
> o.a.n.controller.StandardProcessorNode Failed to invoke @OnScheduled method 
> due to java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> java.lang.RuntimeException: Failed while executing one of processor's 
> OnScheduled task.
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1466)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode.access$000(StandardProcessorNode.java:98)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1.run(StandardProcessorNode.java:1287)
>  ~[na:na]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_101]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.reflect.InvocationTargetException
> at java.util.concurrent.FutureTask.report(FutureTask.java:122) 
> [na:1.8.0_101]
> at java.util.concurrent.FutureTask.get(FutureTask.java:206) 
> [na:1.8.0_101]
> at 
> org.apache.nifi.controller.StandardProcessorNode.invokeTaskAsCancelableFuture(StandardProcessorNode.java:1449)
>  ~[na:na]
> ... 9 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[na:1.8.0_101]
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.8.0_101]
> at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:137)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:125)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(ReflectionUtils.java:70)
>  ~[na:na]
> at 
> org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:47)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1291)
>  ~[na:na]
> at 
> org.apache.nifi.controller.StandardProcessorNode$1$1.call(StandardProcessorNode.java:1287)
>  ~[na:na]
> ... 6 common frames omitted
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: class 
> org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback not 
> org.apache.hadoop.security.GroupMappingServiceProvider
> at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2231) 
> ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:78) ~[na:na]
> at org.apache.hadoop.security.Groups.(Groups.java:74) ~[na:na]
> at 
> org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:303)
>  ~[na:na]
> at 
> org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
>  ~[na:na]
> at 
> org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:311)
>  ~[na:na]
> at 
> org.apache.nifi.hadoop.SecurityUtil.loginSimple(SecurityUtil.java:70) ~[na:na]
> at 
> org.apache.nifi.processors.hadoop.AbstractHadoopProcessor.resetHDFSResources(AbstractHadoopProcessor.java:300)
>

[jira] [Resolved] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

2017-05-01 Thread Byunghwa Yun (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Byunghwa Yun resolved NIFI-2867.

Resolution: Won't Fix

> The ColumnSize of datetime type is 19 length in MySQL JDBC.
> ---
>
> Key: NIFI-2867
> URL: https://issues.apache.org/jira/browse/NIFI-2867
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 1.1.0
>Reporter: Byunghwa Yun
>Priority: Minor
>
> When I use the ConvertJSONToSQL, it changes the field value for data capacity 
> of source datastore.
> {code}
> /nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ConvertJSONToSQL.java:
>  430 line
> if (colSize != null && fieldValue.length() > colSize) {
> fieldValue = fieldValue.substring(0, colSize);
> }
> {code}
> But the type of field is datetime in MySQL DB, JDBC driver returns 19 column 
> size. So above code truncate field value to 2016-10-05 12:00:00 from 
> 2016-10-05 12:00:00.0.
> PutSQL only resolve the TIMESTAMP type using -MM-dd HH:mm:ss.SSS 
> SimpleDateFormat. So it throws below exception.
> {quote}
> {code}
> 2016-10-05 13:05:56,526 ERROR [Timer-Driven Process Thread-14] 
> o.apache.nifi.processors.standard.PutSQL
> org.apache.nifi.processor.exception.ProcessException: The value of the 
> sql.args.7.value is '2016-10-05 13:05:43', which cannot be converted to a 
> timestamp
> at 
> org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:630) 
> ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processors.standard.PutSQL.onTrigger(PutSQL.java:241) 
> ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>  [nifi-api-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1064)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
>  [nifi-framework-core-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_51]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
> [na:1.8.0_51]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>  [na:1.8.0_51]
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>  [na:1.8.0_51]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [na:1.8.0_51]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [na:1.8.0_51]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_51]
> Caused by: java.text.ParseException: Unparseable date: "2016-10-05 13:05:43"
> at java.text.DateFormat.parse(DateFormat.java:366) ~[na:1.8.0_51]
> at 
> org.apache.nifi.processors.standard.PutSQL.setParameter(PutSQL.java:798) 
> ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> at 
> org.apache.nifi.processors.standard.PutSQL.setParameters(PutSQL.java:626) 
> ~[nifi-standard-processors-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]
> ... 13 common frames omitted
> {code}
> {quote}
> Thank you.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (NIFI-4370) View Details of NiFi Data Provenance throws NPE when cluster mode

2017-09-09 Thread Byunghwa Yun (JIRA)

Byunghwa Yun created NIFI-4370:
--

 Summary: View Details of NiFi Data Provenance throws NPE when 
cluster mode
 Key: NIFI-4370
 URL: https://issues.apache.org/jira/browse/NIFI-4370
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.4.0
Reporter: Byunghwa Yun
 Fix For: 1.4.0


When I got the Provenance Event, NiFi throws NPE.

{code:java}
2017-09-09 18:02:18,863 ERROR [NiFi Web Server-208] 
o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: 
java.lang.NullPointerException. Returning Internal Server Error response.
java.lang.NullPointerException: null
at 
org.apache.nifi.web.api.ProvenanceEventResource.getProvenanceEvent(ProvenanceEventResource.java:297)
{code}

I think the cause that below method removed at NIFI-4224.

{code:java}
protected Response replicate(final String method, final String nodeUuid)
{code}

Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (NIFI-3425) Cache prepared statements in PutCassandraQL

[jira] [Created] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

[jira] [Updated] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

[jira] [Updated] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns zero or a negative value.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns zero or a negative value.

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

[jira] [Created] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

[jira] [Updated] (NIFI-2866) The Initial Max Value of QueryDatabaseTable won't be case sensitive.

[jira] [Created] (NIFI-2811) JdbcCommon doesn't convert bigint(20) column.

[jira] [Created] (NIFI-2803) The pagination of GenerateTableFetch has a sort bug.

[jira] [Created] (NIFI-2802) The implementation classes don't support orderByClause.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Created] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Updated] (NIFI-2858) getSystemLoadAverage of OperatingSystemMXBean sometimes returns a negative value.

[jira] [Created] (NIFI-3027) ExecuteProcess supports the expression language

[jira] [Created] (NIFI-3185) ConvertJSONToSQL supports UPSERT type

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

[jira] [Created] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

[jira] [Commented] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

[jira] [Updated] (NIFI-3673) Loads the different class in classloader when Bumping NAR plugin

[jira] [Resolved] (NIFI-2867) The ColumnSize of datetime type is 19 length in MySQL JDBC.

[jira] [Created] (NIFI-4370) View Details of NiFi Data Provenance throws NPE when cluster mode

28 matches

Site Navigation

Mail list logo

Footer information