Support Questions
Find answers, ask questions, and share your expertise

java.lang.reflect.InvocationTargetException: : For custom Processor

I have created a Custom processor to use AWS Encryption SDK as a separate processor in NiFi version 1.7.1

I have implemented Abstract class with required Properties and createClient functions and processor main class with getSupportedPropertyDescriptors, onTrigger funtions.

But when I am trying to run the processor it gives below error:-

2018-08-15 23:15:39,732 ERROR [Timer-Driven Process Thread-5] o.a.n.p.a.encryption.EncryptorProcessor EncryptorProcessor[id=3eaf70a8-0165-1000-a4d1-6cfa42125382] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.lang.reflect.InvocationTargetException: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotations(
at org.apache.nifi.util.ReflectionUtils.invokeMethodsWithAnnotation(
at org.apache.nifi.controller.StandardProcessorNode.lambda$initiateStart$4(
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.NullPointerException: null
... 15 common frames omitted



I am also getting the same error


I am developing a AWS Translate processor (which I hope to contribute back) but I am getting the same error. It is a relatively simple subclass of AbstractAWSCredentialsProviderProcessor. Looks like I'll be digging deeper but in the meantime I'm curious if anyone has made progress on debugging this?

New Contributor

You can check if is the propertydescription TIMEOUT that is missing.