- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
ApacheNifi HttpInvoke java.lang.IllegalStateException: closed Error
- Labels:
-
Apache NiFi
Created 10-22-2024 05:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello All,
Actually, I'm getting one error from my post call in nifi and in that I'm making post call with form data which contains file, JSon body but even after properly configuring the Httpinvoke it's giving me this error
java.lang.IllegalStateException: closed
Can you please help me in this these are my configuration which I have done
this preview which i got
And the configuration:-
and the Entire pipeline
Created 10-22-2024 10:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@pankajgaikwad Welcome to the Cloudera Community!
To help you get the best possible solution, I have tagged our NiFi experts @MattWho @SAMSAL who may be able to assist you further.
Please keep us updated on your post, and we hope you find a satisfactory solution to your query.
Regards,
Diana Torres,Community Moderator
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:
Created 10-27-2024 10:06 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no one answered yet.......just waiting for it
Created 10-28-2024 06:21 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@pankajgaikwad
while it is wonderful that you have shared your InvokeHTTP processor configurations, I don't think enough information has been provided to provide assistance here. All we know from you post is that some Post rest-api call was made against some service endpoint using some URL, to send form data of some content-type to which an illegal state exception was thrown.
Sharing details about your use case is always helpful.
- What is the target endpoint service (Polarion? which community members may not be familiar with)?
- What is the full rest-api call you are trying to make?
- Were you able to successfully make that same rest-api call via curl local to the NiFi server?
- What is the structure of your NiFi FlowFile (what is in the FlowFile's content and what are the FlowFile's attributes when the FlowFile reaches the InvokeHTTOP processor)?
- What are the complete configurations of the invokeHTTP processor? (Some property values are cut-off in your images)
- What documentation are you following for this rest-api call?
As far as the exception goes...
- Was the "java.lang.IllegalStateException: closed" accompanied by any stack trace in the the nifi-app.log?
- What was logged within the target service when this post request was made?
I see you shared your full dataflow in another community post:
An example of the original file you are obtaining via "GetFile", what attributes you are adding to the FlowFile, and how you are modifying that content before the InvokeHTTP may also be helpful here.
Sharing the additional input and details may make it possible for someone in the community to provide you with some suggestions and solutions.
Thank you,
Matt
Created 10-31-2024 08:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@pankajgaikwad Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. If you are still experiencing the issue, can you provide the information Thanks.
Regards,
Diana Torres,Community Moderator
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.
Learn more about the Cloudera Community:
