Pierre Villard created NIFI-3447:
------------------------------------

             Summary: PutSplunk - Broken Pipe - Fails to reconnect
                 Key: NIFI-3447
                 URL: https://issues.apache.org/jira/browse/NIFI-3447
             Project: Apache NiFi
          Issue Type: Bug
          Components: Extensions
    Affects Versions: 1.1.1
            Reporter: Pierre Villard
            Assignee: Pierre Villard


PutSplunk processor is not able to recover from a connection loss: if the 
Splunk server goes down, the processor will indefinitely fail sending data when 
the server is back:

{noformat}
2017-02-07 13:17:29,044 ERROR [Timer-Driven Process Thread-2] 
o.a.nifi.processors.splunk.PutSplunk 
PutSplunk[id=015a101d-be60-183a-7e7e-6437f7600da5] Failed to send 
StandardFlowFileRecord[uuid=940bd376-adc1-4a7a-8f86-8a635fab621a,claim=StandardContentClaim
 [resourceClaim=StandardResourceClaim[id=1485896025601-1, container=default, 
section=1], offset=67695, 
length=2963],offset=2582,name=nifi-app.27253-30216.log,size=128]; routing to 
'failure'; last failure reason reported was java.io.IOException: Broken pipe;: 
java.io.IOException: Broken pipe
2017-02-07 13:17:29,045 ERROR [Timer-Driven Process Thread-2] 
o.a.nifi.processors.splunk.PutSplunk
java.io.IOException: Broken pipe
        at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[na:1.8.0_77]
        at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) 
~[na:1.8.0_77]
        at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) 
~[na:1.8.0_77]
        at sun.nio.ch.IOUtil.write(IOUtil.java:65) ~[na:1.8.0_77]
        at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471) 
~[na:1.8.0_77]
        at 
org.apache.nifi.remote.io.socket.SocketChannelOutputStream.write(SocketChannelOutputStream.java:87)
 ~[nifi-utils-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.remote.io.socket.SocketChannelOutputStream.write(SocketChannelOutputStream.java:76)
 ~[nifi-utils-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.processor.util.put.sender.SocketChannelSender.write(SocketChannelSender.java:83)
 ~[nifi-processor-utils-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.processor.util.put.sender.ChannelSender.send(ChannelSender.java:83)
 ~[nifi-processor-utils-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.processors.splunk.PutSplunk.processSingleMessage(PutSplunk.java:202)
 ~[nifi-splunk-processors-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.processors.splunk.PutSplunk.onTrigger(PutSplunk.java:162) 
~[nifi-splunk-processors-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_77]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_77]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_77]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_77]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_77]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_77]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
{noformat}



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

Reply via email to