When I call NiFi's API (/flow/about), I get 'unexpected end of stream on' .. in invokehttp.java.exception.message flow file's attribute after it passes from InvokeHTTP processor. (NiFi v1.19.1 running on Linux VM).
Other API tools are also failing when I call NiFi's API.
I would like to use NiFi API, but I suspect that something is not working properly in this version.
(Examples: (1) HTTP GET to google.com is working properly, (2) I receive some raw content from the browser when I call http://localhost:8443/nifi/flow/about)
Could you please advise?
Thank you.
Update #20230130#1
Some errors in nifi-user.log:
No errors in nifi-app logs:
Meanwhile, I learned that in order to make any calls to NiFi by Rest API, I have to use a token for access (before of this I supposed that this is optional).
I was able to get the token and use it in subsequent calls to "nifi-api".
I'm expecting that the same procedure is going to work also in the latest NiFi version (current procedure was tested with NiFi 1.16.3).
Related
I have a dynamic action that is executing a javascript function. The function is reached ok but as soon as I try to fetch the api data it fails with TypeError: Failed to fetch.
The API is set to allow all origins and is also working when called from console or any other method.
Is there something in APEX that is blocking my calls to the external api? I have also added ACL just in case that was causing the issue but it still fails.
We are using Oracle 19 and Apex 22.1.
The call should return JSON and then I should be able to use the JSON to get the path to a report. The call fails and does not reach the external server. When looking at the error I can also see
TypeError: Cannot read properties of undefined (reading 'requestContent')
Any ideas would be appreciated.
I have changed the call to a jQuery ajax call with success callback and this is working.
I also found that the ACL was not set with the correct principal. I used the schema but it was actually a user in apex that seemed to work.
I have recorded script by using Blazemeter. It worked fine for the first day. Now when I am running the same jmx file, it gives me Response code 500.
Please help me to understand what I did wrong.
Sampler Result:
This is how my parameters are posted at login.
BodyData tab does not open for me.
Login parameters:
When you say that it ran successfully yesterday and today it is failing, there is some parameter like session / token that was valid for like 12 hours / 24 hours and now it has expired. You will need to identify that and parameterize it. I cannot help you much right now as I don't know what is that variable value and how does it differ each day. Perhaps checking with developers will help.
It seems you're trying to test a secure web service and most probably there is a current timestamp included somewhere in your request body so the request was passing when it was more or less "recent" and after some time the request became invalid due to expiration.
I cannot state where exactly the problem is and how to fix it by looking at partial screenshot so I can give you only a generic piece of advice: consider using WS-Security Plugin for JMeter for adding the relevant SOAP header containing up-to-date information like timestamp and eventually a signature.
More information: Running SOAP WS-Security Load Tests in JMeter
We have an application that uses asyncresponse and writes the data into a stream.
I upgraded to spring2 from 1.5.
And not sure if it could be releated but now with postman I get this error "Unexpected end of file".
Even in a java client , I get error "java.IO.EOFException: Unexpected end of zlib input stream".
But I get expected result in a curl command.
Now I suspect, this could be something either with user-agent or somewhere in spring2 or jersey , I need to set some properties to get rid of this.
There is no security , I excluded SecurityAutoConfiguration.java, in case somewhere it checks some user-agent.
Because of error I see in java client, I tried with server.compression.enabled=false (which is default anyway), but no luck.
I suppose I need to edit the question.
It seems there is some issue using StreamingOutput using spring2x. This is not streaming which I assumes results in all of above stated issues.
Any help is appreciated.
Please help me understand the possible causes of an 'x-method' missing error when using HttpDelete.
There is a Windows 7 user using Chrome 23 but HttpDelete isn't working. This test website http://www.mnot.net/javascript/xmlhttprequest/ reports the following for the "What Methods Are Available?" section:
DELETE: fail (Test execution problem: expected response header field ('x-method') missing.)
The machine also fails to use DELETE when using a custom web application accessing a REST service using jQuery ajax. It reports a 405 exception for any DELETE requests. The application works fine for other machines with the exact same actions.
Information about what could cause the delete verb to fail under these circumstances is appreciated.
I recently recorded a test script in Jmeter intended for use as a load test script (using this handy set of instructions. The recording itself worked great and I even figured out how to grab and parametrize the session ids and timestamps. However, if I run the recorded steps just as they were recorded some of them don't work -- they generate "500--Server encountered and internal error ...nested exception is java.lang.NullPointerException" The failing steps are all Ajax calls that populate sidebar elements. If I copy the request GET call (Request tab, ViewResultsTree) and paste it into a browser I get the exact same error. Do I need to record my script differently, or hand-code the ajax calls? Other, earlier steps work correctly and send the expected POST data, so it isn't the application under test or forgotten proxy settings. Currently running against Firefox 3.6.10
Any suggestions on how I can debug this would be greatly appreciated.
The first thing I'd do is determine if the java.lang.NullPointerException is happening on the client side (JMeter) or on your server. If it is happening in JMeter, than something is terribly wrong with either your script or with JMeter.
But assuming that the error is encountered on your server, then looking into the cause of the exception may shed light on what is wrong with the request issued by JMeter. Do you have access to the code where the exception is thrown?
I would also recommend comparing the request in the recording with the request that generated the error. You may need to determine which parts of the request are session-specific and ensure those fields are populated correctly.
It sounds like Jmeter isn't executing the AJAX calls, and this can be fine depending on your site. Can you simply do an HTTP request to get the pages the AJAX calls populate?
I would recommend reading this post, as it looks pretty good.
I've seen that situation caused by a few things:
a page is required to load and be cached BEFORE making the failing request;
the failing page needs to automatically redirected to work properly;
the failing page has sub-requests JMeter failed to record. Devs can help with this.
Hope this helps.