Forum Discussion

mirza's avatar
mirza
New Member
4 years ago
Solved

HTTP/1.1 500 Internal Server Error received when Testing any wsdl api

Dear All,

 

We received HTTP/1.1 500 Internal Server Error when Testing any wsdl api or any rest api in soap ui

 

For Checking complete details

 

Server: Oracle-HTTP-Server
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, max-age=0
Pragma: no-cache
X-ORACLE-DMS-ECID: 005fwxbE8MEA9Te5xbWByW0001qZ0001r6
X-Forwarded-Server: ehhi-test.fa.em2.oraclecloud.com
X-RESOURCE-IDENTITY-DOMAIN-NAME: ehhi-test
SOAPAction: "http://xmlns.oracle.com/apps/financials/generalLedger/journals/desktopEntry/journalImportService/importJournals"
X-WebLogic-Request-ClusterInfo: true
X-Forwarded-Host: ehhi-test.fa.em2.oraclecloud.com
X-USER-IDENTITY-DOMAIN-NAME: ehhi-test
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
WWW-Authenticate: BASIC realm="owsm",Bearer
IS_SSL: ssl
Akamai-Origin-Hop: 2
X-Forwarded-For: 203.101.162.59, 79.140.80.245, 23.62.98.166
Accept-Encoding: gzip,deflate
X-RESOURCE-SERVICE-NAME: gsi
VIRTUAL_HOST_TYPE: external
ECID-Context: 1.005fwxbE8MEA9Te5xbWByW0001qZ0001r6;kYjE
X-Akamai-CONFIG-LOG-DETAIL: true
X-RESOURCE-SERVICE-TYPE: FA_GSI
Host: ehhi-test.fa.em2.oraclecloud.com
X-DataStream-Session-Id: 63467a99-5f687110-1d0401b2
Content-Encoding: gzip
Content-Type: text/xml; charset=UTF-8
Content-Language: en
X-Content-Type-Options: nosniff
Content-Length: 650
Date: Mon, 21 Sep 2020 09:23:28 GMT
Connection: close
Vary: Accept-Encoding

 

Thanks

  • Hey mirza,

    500s relates to the server end of things and looking at the client side of things (SoapUI) doesnt normally help to diagnose the cause of the issue.
    When ive received 500s before ive checking the logging on the appserver that hosts the endpoint im hitting and so id suggest you do the same. I.e. check the logs on the server....the SoapUI logs wont help in this regard.

    Cheers

    Rich

2 Replies

  • richie's avatar
    richie
    Community Hero
    Hey mirza,

    500s relates to the server end of things and looking at the client side of things (SoapUI) doesnt normally help to diagnose the cause of the issue.
    When ive received 500s before ive checking the logging on the appserver that hosts the endpoint im hitting and so id suggest you do the same. I.e. check the logs on the server....the SoapUI logs wont help in this regard.

    Cheers

    Rich
    • sonya_m's avatar
      sonya_m
      SmartBear Alumni (Retired)

      Thank you Richie!

       

      mirza , does the advice help?