You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Devin Fisher <de...@perfectsearchcorp.com> on 2016/10/12 22:01:41 UTC
Error: Self-suppression not permitted
I'm having an issue with an in-house processor (not for email inboxes).
Only seems to happen periodically on heavy loads, not in dev environments.
Based on the stack trace the Illegal self-suppression is happening in the
framework code and it seems to be masking the original exception that was
thrown (maybe?).
Going to be continuing to trace this one down but was wondering if anyone
has seen something like and what might be the likely cause.
version: 0.7.0
os: centOS 7
java: openjdk version "1.8.0_101"
71088 2016-10-12 15:07:19,503 ERROR [Timer-Driven Process Thread-16]
c.imatsolutions.nifi.processor.GetInbox
GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb]
GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb] f
ailed to process due to java.lang.IllegalArgumentException:
Self-suppression not permitted; rolling back session:
java.lang.IllegalArgumentException: Self-suppression not permitted
71089 2016-10-12 15:07:19,505 ERROR [Timer-Driven Process Thread-16]
c.imatsolutions.nifi.processor.GetInbox
71090 java.lang.IllegalArgumentException: Self-suppression not permitted
71091 at java.lang.Throwable.addSuppressed(Throwable.java:1043)
~[na:1.8.0_101]
71092 at
org.apache.nifi.controller.repository.StandardProcessSession.write(StandardProcessSession.java:1999)
~[na:na]
71093 at com.imatsolutions.nifi.processor.GetInbox.processInboxItem(
GetInbox.java:219) [legacy-1.0.0.jar:na]
71094 at com.imatsolutions.nifi.processor.GetInbox.processInboxBatch(
GetInbox.java:118) [legacy-1.0.0.jar:na]
71095 at com.imatsolutions.nifi.processor.GetInbox.onTrigger(GetInbox.java:76)
[legacy-1.0.0.jar:na]
71096 at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1054)
[nifi-framework-core-0.7.0.jar:0.7.0]
71097 at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
[nifi-framework-core-0.7.0.jar:0.7.0]
71098 at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
[nifi-framework-core-0.7.0.jar:0.7.0]
71099 at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:127)
[nifi-framework-core-0.7.0.jar:0.7.0]
71100 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_101]
71101 at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
[na:1.8.0_101]
71102 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
[na:1.8.0_101]
71103 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
[na:1.8.0_101]
71104 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_101]
71105 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_101]
71106 at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
71107 Suppressed: java.lang.NullPointerException: null
71108 Caused by: java.lang.NullPointerException: null
Re: Error: Self-suppression not permitted
Posted by Devin Fisher <de...@perfectsearchcorp.com>.
Thanks, I'll see if I can do that. Might be difficult since we don't build
our own nifi binaries. I could use the 0.7.x RC when it comes out.
But could you tell me what processor you were using when you had that issue
because the error looks different? Also, if that processor was an
in-house one, did it like the ticket mention write the content more than
once? I don't believe our processors are writing more than once the
content of the flowfile.
Devin
On Wed, Oct 12, 2016 at 4:07 PM, Michael Moser <mo...@gmail.com> wrote:
> Devin,
>
> This sounds a lot like the issue documented in NIFI-2551 [1]. Since you
> are using NiFi 0.7.0, you might try to build the latest code in the 0.x
> branch and see if this version resolves your problem.
>
> -- Mike
>
> [1] - https://issues.apache.org/jira/browse/NIFI-2551
>
>
> On Wed, Oct 12, 2016 at 6:01 PM, Devin Fisher <
> devin.fisher@perfectsearchcorp.com> wrote:
>
> > I'm having an issue with an in-house processor (not for email inboxes).
> > Only seems to happen periodically on heavy loads, not in dev
> environments.
> > Based on the stack trace the Illegal self-suppression is happening in the
> > framework code and it seems to be masking the original exception that was
> > thrown (maybe?).
> >
> > Going to be continuing to trace this one down but was wondering if anyone
> > has seen something like and what might be the likely cause.
> >
> > version: 0.7.0
> > os: centOS 7
> > java: openjdk version "1.8.0_101"
> >
> >
> >
> > 71088 2016-10-12 15:07:19,503 ERROR [Timer-Driven Process Thread-16]
> > c.imatsolutions.nifi.processor.GetInbox
> > GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb]
> > GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb] f
> > ailed to process due to java.lang.IllegalArgumentException:
> > Self-suppression not permitted; rolling back session:
> > java.lang.IllegalArgumentException: Self-suppression not permitted
> > 71089 2016-10-12 15:07:19,505 ERROR [Timer-Driven Process Thread-16]
> > c.imatsolutions.nifi.processor.GetInbox
> > 71090 java.lang.IllegalArgumentException: Self-suppression not permitted
> > 71091 at java.lang.Throwable.addSuppressed(Throwable.java:1043)
> > ~[na:1.8.0_101]
> > 71092 at
> > org.apache.nifi.controller.repository.StandardProcessSession.write(
> > StandardProcessSession.java:1999)
> > ~[na:na]
> > 71093 at com.imatsolutions.nifi.processor.GetInbox.processInboxItem(
> > GetInbox.java:219) [legacy-1.0.0.jar:na]
> > 71094 at com.imatsolutions.nifi.processor.GetInbox.
> processInboxBatch(
> > GetInbox.java:118) [legacy-1.0.0.jar:na]
> > 71095 at com.imatsolutions.nifi.processor.GetInbox.onTrigger(
> > GetInbox.java:76)
> > [legacy-1.0.0.jar:na]
> > 71096 at
> > org.apache.nifi.controller.StandardProcessorNode.onTrigger(
> > StandardProcessorNode.java:1054)
> > [nifi-framework-core-0.7.0.jar:0.7.0]
> > 71097 at
> > org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> > ContinuallyRunProcessorTask.java:136)
> > [nifi-framework-core-0.7.0.jar:0.7.0]
> > 71098 at
> > org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> > ContinuallyRunProcessorTask.java:47)
> > [nifi-framework-core-0.7.0.jar:0.7.0]
> > 71099 at
> > org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(
> > TimerDrivenSchedulingAgent.java:127)
> > [nifi-framework-core-0.7.0.jar:0.7.0]
> > 71100 at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> > [na:1.8.0_101]
> > 71101 at
> > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> > [na:1.8.0_101]
> > 71102 at
> > java.util.concurrent.ScheduledThreadPoolExecutor$
> > ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> > [na:1.8.0_101]
> > 71103 at
> > java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(
> > ScheduledThreadPoolExecutor.java:294)
> > [na:1.8.0_101]
> > 71104 at
> > java.util.concurrent.ThreadPoolExecutor.runWorker(
> > ThreadPoolExecutor.java:1142)
> > [na:1.8.0_101]
> > 71105 at
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > ThreadPoolExecutor.java:617)
> > [na:1.8.0_101]
> > 71106 at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> > 71107 Suppressed: java.lang.NullPointerException: null
> > 71108 Caused by: java.lang.NullPointerException: null
> >
>
Re: Error: Self-suppression not permitted
Posted by Michael Moser <mo...@gmail.com>.
Devin,
This sounds a lot like the issue documented in NIFI-2551 [1]. Since you
are using NiFi 0.7.0, you might try to build the latest code in the 0.x
branch and see if this version resolves your problem.
-- Mike
[1] - https://issues.apache.org/jira/browse/NIFI-2551
On Wed, Oct 12, 2016 at 6:01 PM, Devin Fisher <
devin.fisher@perfectsearchcorp.com> wrote:
> I'm having an issue with an in-house processor (not for email inboxes).
> Only seems to happen periodically on heavy loads, not in dev environments.
> Based on the stack trace the Illegal self-suppression is happening in the
> framework code and it seems to be masking the original exception that was
> thrown (maybe?).
>
> Going to be continuing to trace this one down but was wondering if anyone
> has seen something like and what might be the likely cause.
>
> version: 0.7.0
> os: centOS 7
> java: openjdk version "1.8.0_101"
>
>
>
> 71088 2016-10-12 15:07:19,503 ERROR [Timer-Driven Process Thread-16]
> c.imatsolutions.nifi.processor.GetInbox
> GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb]
> GetInbox[id=cb72b2ca-02da-4508-b619-8884713db8cb] f
> ailed to process due to java.lang.IllegalArgumentException:
> Self-suppression not permitted; rolling back session:
> java.lang.IllegalArgumentException: Self-suppression not permitted
> 71089 2016-10-12 15:07:19,505 ERROR [Timer-Driven Process Thread-16]
> c.imatsolutions.nifi.processor.GetInbox
> 71090 java.lang.IllegalArgumentException: Self-suppression not permitted
> 71091 at java.lang.Throwable.addSuppressed(Throwable.java:1043)
> ~[na:1.8.0_101]
> 71092 at
> org.apache.nifi.controller.repository.StandardProcessSession.write(
> StandardProcessSession.java:1999)
> ~[na:na]
> 71093 at com.imatsolutions.nifi.processor.GetInbox.processInboxItem(
> GetInbox.java:219) [legacy-1.0.0.jar:na]
> 71094 at com.imatsolutions.nifi.processor.GetInbox.processInboxBatch(
> GetInbox.java:118) [legacy-1.0.0.jar:na]
> 71095 at com.imatsolutions.nifi.processor.GetInbox.onTrigger(
> GetInbox.java:76)
> [legacy-1.0.0.jar:na]
> 71096 at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(
> StandardProcessorNode.java:1054)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> 71097 at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> ContinuallyRunProcessorTask.java:136)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> 71098 at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(
> ContinuallyRunProcessorTask.java:47)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> 71099 at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(
> TimerDrivenSchedulingAgent.java:127)
> [nifi-framework-core-0.7.0.jar:0.7.0]
> 71100 at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_101]
> 71101 at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> [na:1.8.0_101]
> 71102 at
> java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_101]
> 71103 at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(
> ScheduledThreadPoolExecutor.java:294)
> [na:1.8.0_101]
> 71104 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> [na:1.8.0_101]
> 71105 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> [na:1.8.0_101]
> 71106 at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101]
> 71107 Suppressed: java.lang.NullPointerException: null
> 71108 Caused by: java.lang.NullPointerException: null
>