I confirmed that its only an issue for digest, so I switched to basic for the moment and moved on.
I also noticed I was not having the (digest) issue on the first batch of the InvokeHttp and it failed on subsequent batch attempts (and kept retrying & failing). On Tue, Jun 28, 2016 at 1:18 PM, Scott Stroud <[email protected]> wrote: > Is this only an issue for digest authentication? > > On Tue, Jun 28, 2016 at 11:05 AM, Scott Stroud <[email protected]> > wrote: > >> If your sense is its triggering this based on http headers (or body) >> characteristics, I can play with those since its my own service thats being >> called. Thanks. >> >> On Tue, Jun 28, 2016 at 10:43 AM, Joey Frazee <[email protected]> >> wrote: >> >>> OkHttp which InvokeHTTP is using has some Android support, including >>> logging. It's almost as if it's detected the wrong platform. >>> >>> Not an answer but the Android reference is probably from there. >>> >>> > On Jun 28, 2016, at 7:37 AM, Joe Witt <[email protected]> wrote: >>> > >>> > Scott >>> > >>> > What is throwing me off is the android reference there in the class >>> > name. In the logs/nifi-app.log are you seeing the full stack traces >>> > that follow those messages. If not we will want to turn those on and >>> > see them unless someone has a better idea. >>> > >>> > Thanks >>> > Joe >>> > >>> >> On Tue, Jun 28, 2016 at 7:27 AM, Scott Stroud <[email protected]> >>> wrote: >>> >> java version "1.8.0_72" >>> >> >>> >> Java(TM) SE Runtime Environment (build 1.8.0_72-b15) >>> >> >>> >> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode) >>> >> >>> >> >>> >>> On Tue, Jun 28, 2016 at 10:27 AM, Joe Witt <[email protected]> >>> wrote: >>> >>> >>> >>> Agreed - it should work out of the box. >>> >>> >>> >>> When you run 'java -version' can you please share the output. >>> >>> >>> >>> Thanks >>> >>> Joe >>> >>> >>> >>> On Tue, Jun 28, 2016 at 7:23 AM, Scott Stroud <[email protected] >>> > >>> >>> wrote: >>> >>>> Im attempting to use the InvokeHTTP component with the 0.6.1 >>> release and >>> >>>> keep seeing this error. My JAVA_HOME is 1.8.0_72-b15 on my Mac. Im >>> >>>> sure I >>> >>>> could go find the jar and manually add it to the classpath, but I >>> assume >>> >>>> it >>> >>>> should work OOB straight from the NiFi download or maybe its some >>> path >>> >>>> nuance to my local system. Any insight is appreciated. >>> >>>> >>> >>>> InvokeHTTP[id=908a3005-b216-4458-aeee-489e6ec7c462] failed to >>> process >>> >>>> session due to java.lang.NoClassDefFoundError: android/util/Log: >>> >>>> java.lang.NoClassDefFoundError: android/util/Log >>> >>>> 09:50:51 EDTWARNING908a3005-b216-4458-aeee-489e6ec7c462 >>> >>>> InvokeHTTP[id=908a3005-b216-4458-aeee-489e6ec7c462] Processor >>> >>>> Administratively Yielded for 1 sec due to processing failure >>> >>>> 09:50:54 EDTWARNING908a3005-b216-4458-aeee-489e6ec7c462 >>> >>>> InvokeHTTP[id=908a3005-b216-4458-aeee-489e6ec7c462] Processor >>> >>>> Administratively Yielded for 1 sec due to processing failure >>> >>>> 09:50:54 EDTERROR908a3005-b216-4458-aeee-489e6ec7c462 >>> >>>> InvokeHTTP[id=908a3005-b216-4458-aeee-489e6ec7c462] >>> >>>> InvokeHTTP[id=908a3005-b216-4458-aeee-489e6ec7c462] failed to >>> process >>> >>>> session due to java.lang.NoClassDefFoundError: android/util/Log: >>> >>>> java.lang.NoClassDefFoundError: android/util/Log >>> >> >>> >> >>> >> >> >
