[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto: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 <loek.maartens@xxxxxxxxx>
 To: 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]<sk@xxxxxxxxxxxxxxxx>
  To: HTTPAPI and FTPAPI Projects [2]<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]http://www.midrange.com
  [2][4]http://www.code400.com
  [3][5]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]http://www.scottklement.com/mailman/listinfo/ftpapi
  -----------------------------------------------------------------------

References

  1. [7]http://www.midrange.com/
  2. [8]http://www.code400.com/
  3. [9]http://forums.iprodeveloper.com/
  4. [10]http://www.scottklement.com/mailman/listinfo/ftpapi


-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
[11]http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

References

  1. mailto:sk@xxxxxxxxxxxxxxxx
  2. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
  3. http://www.midrange.com/
  4. http://www.code400.com/
  5. http://forums.iprodeveloper.com/
  6. http://www.scottklement.com/mailman/listinfo/ftpapi
  7. http://www.midrange.com/
  8. http://www.code400.com/
  9. http://forums.iprodeveloper.com/
  10. http://www.scottklement.com/mailman/listinfo/ftpapi
  11. 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
-----------------------------------------------------------------------


  
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------