nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Doran <kdoran.apa...@gmail.com>
Subject Re: Java exception when attempting to update version from registry
Date Thu, 10 Jan 2019 16:15:33 GMT
Sorry, forgot to add -- can you include the full stack trace for the
IllegalStateException as well? It should be in the nifi-app.log file.

Thanks,
Kevin


On January 10, 2019 at 11:13:33, Kevin Doran (kdoran@apache.org) wrote:
> Hi Russ,
>
> You mentioned you're using NiFi 1.6. What version of NiFi Registry are you running? Is
> the error message consistent?
>
> What is the sequence of steps you are using to move the flow snapshot from DEV to QA?
Is it
> all through the NiFi UI (i.e., both environments are pointed to the same NiFi Registry
> instance, and you save a version from DEV and then change version in QA), or is there
more
> to it than that?
>
> I find it interesting that change version is failing but delete and import is working...
> That seems to indicate that the flow snapshot is being saved to registry correctly and
> completly, but there is some error in the logic of change version that is applying the
> changes in the wrong order.
>
> I know this may not be super helpful, but you may be running into a bug in the Change
Version
> logic that has alreay been fixed in the latest version of NiFi. (To others on the mailing
> list, does that ring any bells?) If you're not able to test this on the NiFi 1.8 and
Registry
> 0.3, can you provide the steps to reproduce it so that I can try?
>
> Thanks,
> Kevin
>
>
> On January 10, 2019 at 10:57:19, Russ Weiher (russ.weiher@progenity.com) wrote:
> > Hello -
> >
> >
> >
> > I'm trying to move changes from my DEV instance to the QA instance (via the= Registry),
> > but it's giving me the following error:
> >
> >
> >
> > "Failed to update flow to new version due to java.lang.IllegalStateException: The
> > input port name or identifier is not available to be added."
> >
> >
> >
> > I had a similar issue in the past where it wouldn't update to a new version= , but
due to
> deadlines
> > I ended up just deleting the QA version and re-impor= ting the flow from the registry.
> > However, that approach means that dozens o= f variables have to be double checked
and/or
> > updated for the new environmen= t (QA and then again for PROD which gives the same
error).
> >
> >
> >
> > If this is going to keep happening, I'd rather try and get to the bottom of= it,
but haven't
> > been able to find other examples of people having issues w= hen updating flow versions
> > using the registry.
> >
> >
> >
> > Currently running Nifi version 1.6.
> >
> >
> > Russ Weiher
> > BI CI Solutions Architect
> > Progenity, Inc.
> >
> > 5230 S. State Road
> > Ann Arbor, MI 48108
> > www.progenity.com
> >
> > (734) 794-9488 Office
> >
> > IMPORTANT: This email (and any attachments) is intended for the use of only the
person
> > or entity to which it is addressed, and may contain information that is privileged
and
> > confidential. You, the recipient, are obligated to maintain it in a safe, secure
and
> > confidential manner. Unauthorized redisclosure or failure to maintain confidentiality
> > may subject you to federal and state penalties. If you are not the intended recipient,
> > please immediately notify us by return email, and delete this message from your
computer.
> >
>

Mime
View raw message