ContributionsMost RecentMost LikesSolutionsRe: Feedmaster queue pileup and the response time for ultra pipeline Hi Aditya, As per my understanding it was happening because of network hops. The client/jmeter was running on one network and ultra pipes were on different so due to hop it was taking time. I was running 4 instances of 1 ultra pipe so first req on each instance was taking some time(~10sec) due to some security constraints/checks on our network, 1st req onward it was processing smoothly. Thanks! Re: How to fail a Snap for Invalid json as i/p doc(Duplicate keys) Hi Team, Below workaround i did to using Python script to validate invalid json - 1-Have binary to doc snap as first snap and land i/p as encodedBase64 2-Add next snap as Script snap with python lang. Decode back the i/p doc in script and use json.loads module for parsing json it will raise error on dup key. Refer below link for script- stackoverflow.com json.loads allows duplicate keys in a dictionary, overwriting the first value python, json asked by Anuj Acharya on 07:52PM - 15 Feb 13 UTC Thanks, Kumar Re: How to fail a Snap for Invalid json as i/p doc(Duplicate keys) tstack: Most (all?) JSON parsers don’t consider duplicate keys as a problem. Why are you concerned about this? Hi Tim, Yes other errors like non-terminated strings are giving proper validation erros. Concern for dup key is because our testing team has this scenario of sending invalid json for the automation testing and they want this case to be failed, but as dup key is not problem for most of snaps so they will get success response. Testing team will expect invalid json error for this but getting success. We have test pattern in all interfaces for all tools. As apigee and tibco have solution for this. Apigee has policy regExp and tibco parser has Staxon function for json parsers, so i am looking for similar option in snaps. Please let me know any thoughts to validate this invalid json due to dup keys. With Regards, KumarR Re: How to fail a Snap for Invalid json as i/p doc(Duplicate keys) The i/p feed itself was json so can’t use JSON.parse. To use parse need to make it string first i.e JSON.parse(JSON.stringify($)) However JSON.stringify($) itself removing duplicate key. Re: How to fail a Snap for Invalid json as i/p doc(Duplicate keys) Hi Anubhav, Thanks for looking in this! I gave example of copy snap to show that it removes dup keys in invalid json. As per your suggestion i tried using Json generator by having i/p view and template to snap as below- [ { “www” : $www } ] But Json generator also has removed dup key and provided output. I want this to be failed as i supplied invalid json from psotman. $www has dup key inside it as ‘station’ How to fail a Snap for Invalid json as i/p doc(Duplicate keys) Hi Team, I am sending a invalid json payload from the postman to my pipeline. The pipeline has first snap as Copy, when i checked the output of copy it has removed duplicated keys from the invalid json payload. My expectation was that it will throw error as i have sent invalid json. Any thought on how can i fail the pipeline if the payload coming as invalid json into pipeline/snap? Below was payload i sent to pipe from postman tool- { “www”: { “station”: “3333”, “station”: “22222”, “station”: “44444”, “dd”: 24224, “dd1”: “34224”, “dd2”: “sfsf”, “dd3”: “dddsfsf” } } The output of copy snap came as below(i wannt the snap to be failed as it was invalid json data)- { “www”: { “station”: “44444”, “scaleId”: “wrwr”, “dd”: 24224, “dd1”: “34224”, “dd2”: “sfsf”, “dd3”: “dddsfsf” } } Thanks, Kumar R Re: Mixed content is not supported Hi team, Please suggest if anyone come across this, Soap snap parsing the xml output response which has mixed contents and so its failing as not able to create josn of the response, Is there a way we can get xml as is as output from soap snap so that json parsing by soap snap will not fail due to mixed contents. By mean of any header or something by which snap can give xml as output. Thanks! Kumar Mixed content is not supported Hi Team, I am getting below error from soap execute snap, My webservice returns me the mixed content and seems the soap snap is not able to digest/ parse it to json response. Can you please suggest how can we get this response in soap snap output view? Below is the response which i captured from SOAP UI for the web service which has mixed content in this,. Soap UI response for service- <soap:Envelope xmlns:soap=“http://www.w3.org/2003/05/soap-envelope” xmlns:ns=“http://www.inlandrevenue.gov.uk/SOAP/Response/1” xmlns:ns1=“http://www.hmrc.gov.uk/successresponse/2” xmlns:xd=“XML-Signature Syntax and Processing” xmlns:err=“http://www.govtalk.gov.uk/CM/errorresponse”> soap:Header/ soap:Body ns:HMRCSOAPResponse <ns1:SuccessResponse TestInLive=“true”> ns1:IRmarkReceipt <xd:Signature Id=“YY”> <xd:SignedInfo Id=“RR”> <xd:CanonicalizationMethod Algorithm=“?”> </xd:CanonicalizationMethod> <xd:SignatureMethod Algorithm=“?”> cum <xd:HMACOutputLength>?</xd:HMACOutputLength> sonoras <!--You may enter ANY elements at this point--> aeoliam </xd:SignatureMethod> </xd:SignedInfo> </xd:Signature> </ns1:IRmarkReceipt> </ns1:SuccessResponse> </ns:HMRCSOAPResponse> </soap:Body> </soap:Envelope> Best Regards, Kumar Re: Feedmaster queue pileup and the response time for ultra pipeline Hi Dmiller, There is only one pipeline main and it has just a mapper as pass through so nothing related to pipe design. I thought it may be needing some configuration etc so asked here instead of support, however i will reach to support on this, please let me know if you have any input as pipe design is not concern here. Thank you! Feedmaster queue pileup and the response time for ultra pipeline Hi team, I am getting huge variation in the response time while processing request in ultra pipeline(sample pipe not much logic or processing). I have one ultra pipe running with multiple instances, and hitting 11000+ records to pipe from jmeter. Most of the request 90% are getting response in less than 2 sec and 99% are at around 4 sec. Avg time process is 1.2 sec but 1% request are taking more than 10 sec. My usecase can not accept latency beyond 4 sec but i am facing issue here as some req. are taking over 10 sec. What is the reason and what should i do for this to make it consistent, please suggest ? Avg time is ~1.2 sec so variation of 1 or 2 sec is still ok but i am experiencing too much variation of over 8 sec. Please check status below. Thanks,