[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Web Services question
still getting http 500 when I call this service from one as400 to
another [lpar] . Every one else when they call it works
Here is what SOAPUI looks like
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:cna="http://cna_sfdmax.wsbeans.iseries/">
<soapenv:Header/>
<soapenv:Body>
<cna:cst111xml_XML>
<arg0>
<XMLREQUEST>?</XMLREQUEST> <==== I embedd encoded xml
in this field
</arg0>
</cna:cst111xml_XML>
</soapenv:Body>
</soapenv:Envelope>
SetError() #13: HTTP/1.1 500 Internal Server Error
recvresp(): end with 500
recvdoc parms: identity 316
header_load_cookies() entered
recvdoc(): entered
SetError() #0:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Bodyy><soa
p:Fault><faultcode>soap:Server</faultcode><faultstring>The given
SOAPAction http://WEBERVICE NAM doesnot match an
operation.</faultstring></soap:Fault></soap:Body></soap:Envelope>
SetError() #13: HTTP/1.1 500 Internal Server Error
http_close(): entered
senddoc(): entered
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmln
<soapenv:Header/>
<soapenv:Body>
<cna:cst111xml_XML>
<arg0>
<XMLREQUEST><?xml version="1.0"?>
<uniEnvelope>
<header>
<requester>
<applicationName>Universe</applicationName>
<requestedService>PriceCostAndAvailability</requestedService&g
t;
<applicationInstance>Laptop</applicationInstance>
<authenticationUserId>WAKEUPWS</authenticationUserId+gt;>
<requestedByUserId>WAKEUPEW</requestedByUserId>
<sendTimeStamp>20150105T041213.13-6</sendTimeStamp>
</requester>
<exchange>
<applicationName>Universe</applicationName>
<requestedService>PriceCostAndAvailability</requestedService&g
t;
<applicationInstance>Laptop</applicationInstance>
<authenticationUserId>DBARROW1</authenticationUserId+gt;>
<requestedByUserId>DBARROW1</requestedByUserId>
<sendTimeStamp>20150105T041213.13-6</sendTimeStamp>
</exchange>
</header>
<body>
<pcaRequestMain>
<TransferProcessFlag></TransferProcessFlag>
<ReturnType></ReturnType>
<HomeDivisionItem>
<SystemId>03</SystemId>
<DivisionId>32</DivisionId>
<ItemDetailList>
<ItemDetail>
<ItemID>10004761</ItemID>
</ItemDetail>
</ItemDetailList>
</HomeDivisionItem>
<TransferItemLst>
<TransferItem>
<SystemId>X</SystemId>
<DivisionId>CA</DivisionId>
<ItemDetailLst>
<ItemDetail>
<ItemId>1004761</ItemId>
</ItemDetail>
</ItemDetailLst>
</TransferItem>
</TransferItemLst>
</pcaRequestMain>
</body>
</uniEnvelope>
</XMLREQUEST>
</arg0>
</cna:cst111xml_XML>
</soapenv:Body>
</soapenv:Envelope>
__________________________________________________________________
From: Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, April 21, 2015 2:21 PM
Subject: RE: Web Services question
Another thought is that I see your body tag is lowercase. Maybe you
just need to Proper case that?
-----Original Message-----
From: [1]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[2]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike
Krebs
Sent: Tuesday, April 21, 2015 1:02 PM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Web Services question
The debug is actually pretty helpful.
<faultcode>soap:VersionMismatch</faultcode>
<faultstring>No namespaace on "body" element. You must send a SOAP
request.</faultstring>
It is looking for a correct namespace on the "body" element. Googling
that error shows example of something like:
<soap:body>
As the namespace requirement. What to use where I put "soap" can be
seen in the WSDL file if you have one. This is where soapUI would also
be useful. If you run the WSDL through there, it will figure out the
request for you.
-----Original Message-----
From: [3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Donnie
Barrow
Sent: Tuesday, April 21, 2015 12:24 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Web Services question
Mike This is what I am seeing [see attached file]
I tried sending the exact xml another entity does which goes through
without issue. so i condensed it down and got the same issue
From: Mike Krebs <[5]mkrebs@xxxxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects <[6]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Monday, April 20, 2015 1:53 PM
Subject: RE: Web Services question
500 errors are generally internal "server" errors - something like "you
sent me some data that was so distasteful and I didn't know what to do
with it so I decided to spit on the stage and then I puked a little in
my mouth".
If the web service otherwise works, you should check your server logs
on PAR2 and see what it received and why it didn't like what you sent
it.
As always...kind of hard to help you without a debug log, code snippets
and the wsdl. Those will be the key to 99% of the problems. If your
debug looks correct up to the point of the 500 error, then there is not
much we can help with. But if anything looks odd (something you
overlooked?), someone on the list can usually spot those things.
I think a common cause of the 500 error as regards HTTPAPI clients is
not sending the address of the data correctly. It seems to me that has
been the problem as some servers do not deal well with the length being
sent to the web service, so be sure you are doing %addr(xmlField:*data)
on the post data.
After further thought, it might be okay you are getting 500. Your
desire is to wake up the service and I think the fact that the service
said keep your tongue out of my mouth probably woke it up fine.
-----Original Message-----
From: [7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:[8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Donnie
Barrow
Sent: Monday, April 20, 2015 12:09 PM
To: HTTPAPI and FTPAPI Projects
Subject: Re: Web Services question
I havent done anything like that before so any assistance with this
would help. In the meantime here is what i did. I created a small
program on PAR1 to call the webservice on PAR2 but I'm geting a http
500 error.
From: Loek Maartens <[9]loek.maartens@xxxxxxxxx>
To: [10]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
Sent: Thursday, April 16, 2015 3:19 PM
Subject: Re: Web Services question
Donnie,
You could even do this from Prod to Prod, using the localhost /
loopback ip address 127.0.0.1 to "wake-up" the service.
On 16-4-2015 11:44, Donnie Barrow wrote:
rephrase the question
I have an LPAR'd iseries. Par1 is dev and Par2 is Prod.
I am having issues with the first run of web services on Prod.
When we first start our services the first run is slow. What I want
to know is can i call out with HTTPAPI from par 1 to par2 webservice
to wake it up? The ip address on par 1 is different than par 2.
Is this doable? Any foreseen issues?
__________________________________________________________________
From: Scott Klement [1]<[11]sk@xxxxxxxxxxxxxxxx>
To: HTTPAPI and FTPAPI Projects
[2]<[12]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 16, 2015 9:41 AM
Subject: Re: Web Services question
As far as I can tell, this doesn't have anything to do with HTTPAPI
or
FTPAPI. Please only use this WSDL2RPG, HTTPAPI, or FTPAPI topics.
For other things, please consider using sites like this:
[1][3][13]http://www.midrange.com
[2][4][14]http://www.code400.com
[3][5][15]http://forums.iprodeveloper.com
On 4/16/2015 8:24 AM, Donnie Barrow wrote:
> I developed a web service where an entity calls me, but the very
first
> call of the day is extremely slow. This is the case even when I
first
> go and test a new service with SOAPUI. But once it is awake i
get
great
> response time.
> is there anything I should do to "wake up" the service or any
setting
> within the web service itself?
>
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[4][6][16]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. [7][17]http://www.midrange.com/
2. [8][18]http://www.code400.com/
3. [9][19]http://forums.iprodeveloper.com/
4. [10][20]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[11][21]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. mailto:[22]sk@xxxxxxxxxxxxxxxx
2. mailto:[23]ftpapi@xxxxxxxxxxxxxxxxxxxxxx
3. [24]http://www.midrange.com/
4. [25]http://www.code400.com/
5. [26]http://forums.iprodeveloper.com/
6. [27]http://www.scottklement.com/mailman/listinfo/ftpapi
7. [28]http://www.midrange.com/
8. [29]http://www.code400.com/
9. [30]http://forums.iprodeveloper.com/
10. [31]http://www.scottklement.com/mailman/listinfo/ftpapi
11. [32]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[33]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[34]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[35]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
[36]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
References
1. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
2. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
3. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
4. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
5. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
6. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
9. mailto:loek.maartens@xxxxxxxxx
10. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
11. mailto:sk@xxxxxxxxxxxxxxxx
12. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
13. http://www.midrange.com/
14. http://www.code400.com/
15. http://forums.iprodeveloper.com/
16. http://www.scottklement.com/mailman/listinfo/ftpapi
17. http://www.midrange.com/
18. http://www.code400.com/
19. http://forums.iprodeveloper.com/
20. http://www.scottklement.com/mailman/listinfo/ftpapi
21. http://www.scottklement.com/mailman/listinfo/ftpapi
22. mailto:sk@xxxxxxxxxxxxxxxx
23. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
24. http://www.midrange.com/
25. http://www.code400.com/
26. http://forums.iprodeveloper.com/
27. http://www.scottklement.com/mailman/listinfo/ftpapi
28. http://www.midrange.com/
29. http://www.code400.com/
30. http://forums.iprodeveloper.com/
31. http://www.scottklement.com/mailman/listinfo/ftpapi
32. http://www.scottklement.com/mailman/listinfo/ftpapi
33. http://www.scottklement.com/mailman/listinfo/ftpapi
34. http://www.scottklement.com/mailman/listinfo/ftpapi
35. http://www.scottklement.com/mailman/listinfo/ftpapi
36. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------