× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I agree that you need to get a working response.

The OP didn’t mention if he had done this but I would start by trying to use the service via SOAPUI or one of the other tools available and then I know for sure if my request data is valid.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jun 25, 2016, at 10:24 AM, Alasdair Macdonald <wewalkforonereason@xxxxxxxxx> wrote:

500 errors are a pain, since they generally don't provide you with any
information other than "I cannot cope with the data that you have
sent".

On the other hand, *sometimes* they do provide additional information.
I cannot figure out from your debug log if that is the case here, but
this part of the log could be useful:

<faultstring>[invalid field] [invalid field]</faultstring>

What's singluarly unhelpful is that the invalidness is not spelt out for you.

Normally I would test with a simplified version of the data that is to
be sent to the service; if you can do this off the iSeries then you
can happily forget about any EBCDIC / ASCII translation issues
(because sending EBCDIC data to a web service is probably a good way
of getting a 500 error).

Once I have well-formed data that is acceptable to the service, I
would then try to send that from the iSeries.

I can't remember how the debug file is put together, and I can't tease
apart everything that you've copied & pasted here - but on the face of
it, you've sent bad or very bad data. Others here might be able to be
a bit more forensic about the debug log.


On 25 June 2016 at 15:09, pat <p.caroti@xxxxxxxx> wrote:
I all
i'm try to consume a Web services with Scott Klement HTTAPI, the Web service
return "HTTP/1.1 500 Internal Server Error" . Below see httpapi_debug.txt
and http_result.txt content

which could be the problem ?

Thanks in advance

httpapi_debug.txt content

SetError() #25: SSL environment was already initialized!

http_url_post_stmf(): entered

getting post file size...

opening file to be sent...

opening file to be received

http_persist_open(): entered

http_long_ParseURL(): entered

DNS resolver retrans: 2

DNS resolver retry : 2

DNS resolver options: x'00000136'

DNS default domain: MyComp.Com

DNS server found: 192.168.10.xxx

DNS server found: 192.168.10.zzz

-------------------
Dump of server-side certificate information:

---------------------
Cert Validation Code = 0

-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
Serial Number: zzz
Common Name: zzzz
Country: ZZ
State/Province
Locality:
Org Unit: Firm
Protocol Used: TLS Ve
http_persist_post():
http_long_ParseURL():
do_post(): entered
POST /ZZZZZZZ
Host: host
User-Agent: http-api/
Expect: 100-continue
Content-Length: 1280
recvresp(): entered
HTTP/1.1 100 Continue

SetError() #13: HTTP/1.1 100 Continue
sendraw(): entered
<soapenv:Envelope xmlns:soapenv="http:..............
..............

recvresp(): entered
HTTP/1.1 500 Internal Server Error
Date: Sat, 01 Feb 2016 13:56:46 GMT
Server: Gateway
Connection: close
X-CorrelationID: xxxx
Host: ffff
User-Agent: http-api/1.23
Content-Type: text/xml;
charset="utf-8"

SetError() #13: HTTP/1.1 500 Internal Server Error

recvdoc parms: identity 0

header_load_cookies() entered

recvdoc(): entered

SetError() #0:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";>

<env:Header></env:Header>

<env:Body>

<env:Fault>

<faultcode>env:Server</faultcode>

<faultstring>[invalid field] [invalid field]</faultstring>

<detail fault:type="faultDetails"
xmlns:fault="http://www.vordel.com/soapfaults";></detail>
</env:Fault>

</env:Body>

</env:Envelope>
SetError() #44: CommSSL_read: connection broken
SetError() #13: HTTP/1.1 500 Internal Server Error
http_close(): entered

http_result.txt content

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";>

<env:Header></env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>[invalid field] [invalid field]</faultstring>

<detail fault:type="faultDetails"
xmlns:fault="http://www.vordel.com/soapfaults";></detail>
</env:Fault>
</env:Body>
</env:Envelope>



--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.