End of script output before headers

[barnettc2]

I have some apps that will occasionally return a 'failed to receive a response from server error. It works probably 90% of the time. We checked the error log on the apache server when this happens, and we see this:

[Wed Feb 18 09:48:51.730136 2015] [cgi:error] [pid 99:tid 27] [client 10.10.8.181:56744] AH01215: CGI PROGRAM /QSYS.LIB/VALENCE41.LIB/VVCALL.PGM RETURNED EXCEPTION ID CEE9901, referer: http://208.147.215.8:7022/desktop/au...y=9944&lang=en


[Wed Feb 18 09:48:51.863160 2015] [cgi:error] [pid 99:tid 27] [client 10.10.8.181:56744] AH01215: SEE JOBLOG FOR JOB 131009/QTMHHTTP /VALENCE41 , referer: http://208.147.215.8:7022/desktop/au...689944&lang=en


[Wed Feb 18 09:48:51.988904 2015] [core:error] [pid 99:tid 27] [client 10.10.8.181:56744] ZSRV_MSG0947: End of script output before headers: File name is VVCALL.PGM, referer: http://208.147.215.8:7022/desktop/au...key=1424270689


This seemed to work flawlessly on 3.2, not sure why the upgrade would cause intermittent failures.

[robert.swanson]

Which IBM i OS are you running? We've had reports that IBM i 7.2 has some issues with the HTTP Apache server. PTF group SF99713 seems to fix it.

Also it might be useful to see what's in the response that the back-end is attempting to send. If you're on Valence 4.1, you can turn on response logging (in Portal Admin > Settings > Log Settings > "Log all data sent to browser") to help pinpoint what's specifically being sent back to the browser when those failures occur. The response data will be in VVCALLLOG, field LOGRESP.

[barnettc2]

Sorry it's been a while since I've worked on this. We are on version 7, and have applied that PTF group.

I updated to the latest version of Valence this weekend, in hopes that it might solve this issue, but with no success. I tried the 'Log all data sent to browser' and left in on until I encountered the error, but the VVCALLLOG file remains empty.

[robert.swanson]

I should have mentioned you need to check all three boxes in the "Log Settings" section (the first one in particular, which activates the logging). Soon as you do that you should start seeing data in that file.

With data being logged, next time you see that phenomenon happen please give us a call at the support line so we can take a look at it with you.