Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
3 replies Latest Post - ‏2010-01-21T21:04:14Z by dbgantt2
dbgantt2
dbgantt2
26 Posts
ACCEPTED ANSWER

Pinned topic API and eclipse error 503 for URL: http://www.w3.org/TR/html4/loose.dtd

‏2010-01-20T22:11:11Z |
I started getting this error while using the RAM API and eclipse client on RAM 7.1.1.1. A www.w3.org doc indicated they were returning 503 to requests that were deemed invalid. Is there a fix for this problem for 7.1.1.1. I have a large upload of data that will requried the use of the api's. Any assistance is greatly appreciated.
Updated on 2010-01-21T21:04:14Z at 2010-01-21T21:04:14Z by dbgantt2
  • kbauer
    kbauer
    22 Posts
    ACCEPTED ANSWER

    Re: API and eclipse error 503 for URL: http://www.w3.org/TR/html4/loose.dtd

    ‏2010-01-20T22:27:26Z  in response to dbgantt2
    Can you get the error logged on the server side it may contain more information. You said this is a large file it may be that your server is not setup to accept a large file. Restrictions can be placed on the app server or any front end servers (http servers, proxy servers, load balancers etc).
  • dbgantt2
    dbgantt2
    26 Posts
    ACCEPTED ANSWER

    Re: API and eclipse error 503 for URL: http://www.w3.org/TR/html4/loose.dtd

    ‏2010-01-21T21:04:03Z  in response to dbgantt2
    While I do have a bulk upload of data that I need to process, this error is occuring with a trivial asset put. I haven't even gotten to the large file load. Looking at the webshere logs show now reference to the failure.
  • dbgantt2
    dbgantt2
    26 Posts
    ACCEPTED ANSWER

    Re: API and eclipse error 503 for URL: http://www.w3.org/TR/html4/loose.dtd

    ‏2010-01-21T21:04:14Z  in response to dbgantt2
    While I do have a bulk upload of data that I need to process, this error is occuring with a trivial asset put. I haven't even gotten to the large file load. Looking at the webshere logs show now reference to the failure.