java.lang.RuntimeException: java.io.IOException: http://NIGGMDEMO:8500/ComponentInstanceManager/?wsdl returned response code 404

Oracle Community | Esha Prasad | 5 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Issue with CAS services & initializa_servcies

    Oracle Community | 5 years ago | Esha Prasad
    java.lang.RuntimeException: java.io.IOException: http://NIGGMDEMO:8500/ComponentInstanceManager/?wsdl returned response code 404
  2. 0

    crs endeca integration error

    Oracle Community | 4 years ago | 977766
    atg.repository.search.indexing.IndexingException: java.lang.RuntimeException: java.io.IOException: http://localhost:8500/ATGPuben_en_dimvals/?wsdl returned response code 404
  3. 0

    crs-endeca integration errors

    Oracle Community | 4 years ago | 977766
    java.lang.RuntimeException: java.io.IOException: http://localhost:8500/ATGPuben_en_schema/?wsdl returned response code 404
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    ATG Endeca-Crs indexing errors

    Oracle Community | 4 years ago | 977766
    java.lang.RuntimeException: java.io.IOException: http://localhost:8500/ATGPuben_en_dimvals/?wsdl returned response code 404
  6. 0

    Baseline index for CRS 11.2 fails: "Could'nt find the Component in cas registry"

    Oracle Community | 1 year ago | Andreas Badelt
    java.lang.RuntimeException: java.io.IOException: Could'nt find the Component Instance in cas registry: http://localhost:8500/StagingCRS-dimvals/?wsdl

    Root Cause Analysis

    1. java.io.IOException

      http://NIGGMDEMO:8500/ComponentInstanceManager/?wsdl returned response code 404

      at com.endeca.itl.util.UrlUtils.ping()
    2. com.endeca.itl
      UrlUtils.ping
      1. com.endeca.itl.util.UrlUtils.ping(UrlUtils.java:129)
      1 frame