Problem Getting Connected (I think)

[Scott Klement]

http_stmf() has a limit of, I believe, 2 gb. For sure its nothing close to as small as 177,000 -- that's a very small document, actually.

[emhill]

I don't think it is the certificate now, either. My JSON data seems to be getting truncated. If I send it formatted (yajl_genOPEN(*ON)) then this particular string is over 177,000 characters. In the debug text file, the JSON is truncated and I get the pipe broken error. If I use yajl_genOpen(*OFF) then it shrinks the string to a little over 9,000 characters and I don't get the pipe broken error. I get a bad request 400 error. So I think that tells me something is wrong with the JSON string even though I've run it through a couple of verifiers. I've even emailed a copy of the JSON to the company that is going to receive the file and they say they see nothing wrong with it.

I'm trying to get them to monitor when I attempt to send the data to see if that will tell them something. I will keep you guys posted.

Thanks for all the suggestions!

[Scott Klement]

Is the entire document there if you look at the IFS file that you're putting it (before sending it)?

[emhill]

Hey Scott,

The entire document is in the IFS and is formatted correctly.

It seems to get truncated when I send the formatted JSON. That is when I get the broken pipe error. When the JSON is unformatted I don't get the broken pipe error and the string is not truncated. I just get a "400 Bad Request" error. I sent the folks at Allison Transmission the JSON file via email and they ran it through their system. They said it was ok. Go figure...

The head engineer is supposedly going to get with me and monitor what is happening on their end when I transmit the data to them. This is a completely new process for them and they have 3 companies working on the transition. That sounds like trouble....

I will let you know what we find. Thanks for the assistance.