Guillaume, If you look at the processors in the UI do the EvaluateXPath processors show as invalid and if you hover over them what do they show as the reason?
I just setup something similar to the configuration you describe and I cannot recreate what you're seeing yet. Thanks Joe On Mon, Apr 11, 2016 at 11:38 AM, Guillaume Pool <gp...@live.co.za> wrote: > Hi, > > > > If anyone could help I would appreciate it: > > > > After upgrading to 0.6.0 all my EvaluateXMLPath processors report as invalid > with nothing specific reported as the error. > > > > I use flowfile attribute as the destination, xpath query similar to > /message/address > > > > Return type auto-detect / string > > > > Error: > > > > 2016-04-11 17:37:12,465 INFO [NiFi Web Server-64629] > org.apache.nifi.web.filter.RequestLogger Attempting request for (anonymous) > PUT > http://sv-hdpdf1.hdp.supergrp.net:8443/nifi-api/controller/process-groups/d02a0bbc-c142-37ba-adaa-ee191b98790d/processors/e49acf40-76d1-3b6e-a67d-dc40153605ad > (source ip: 172.27.0.97) > > 2016-04-11 17:37:12,474 INFO [NiFi Web Server-64629] > o.a.n.w.a.c.IllegalStateExceptionMapper java.lang.IllegalStateException: > EvaluateXPath[id=e49acf40-76d1-3b6e-a67d-dc40153605ad] is not in a valid > state. Returning Conflict response. > > > > Reports this even if you drop a new processor in. > > > > Sent from Mail for Windows 10 > >
