API Connect

 View Only
Back to discussions
Expand all | Collapse all

Changes are not seen DP side and API calls failed with HTTP 404 Status.

  • 1.  Changes are not seen DP side and API calls failed with HTTP 404 Status.

    Posted Wed May 03, 2023 03:45 PM
    Reply

    Hi Folks, 

    We have an issue after migration from v2018 to v10 on a catalog issue details are below. 

    API calls failed with HTTPS 404 status. The DP log detail is below. 

    20230502T155424.964Z [0x88c00002][apigw][error] source-https(DP3XXX_https_XXXXX): tid(7732530)[ip]: The request URL 'https://XXXX.com/abc/xyz/qaz/uhy/olk' is not routed to any API collection.

    After that error, we check gateway status on the catalog via using apic UI and see below warning. How can we fix that issue? 

    Gateway processing status (Increased)

     



    ------------------------------
    Burak gorener
    ist
    +90262646 50 11
    ------------------------------


  • 2.  RE: Changes are not seen DP side and API calls failed with HTTP 404 Status.

    Posted Wed May 10, 2023 12:50 PM
    Reply

    Hi Burak,

    the team recommended that you file a support ticket instead as they might be able to get more details for you and help you out with the issue. 



    ------------------------------
    Gabriel Marte Blanco
    Austin TX
    ------------------------------

    Original Message


  • 3.  RE: Changes are not seen DP side and API calls failed with HTTP 404 Status.

    Posted Mon May 22, 2023 01:47 AM
    Reply

    Hi Gabriel,

    We restarted DP Cluster and waited 10-15 minutes after the restart in order to deploy defined APIs on DPs but could not see any APIs in the assembly section on DPs automatically. After that, we updated the catalogs comments via web UI and see APIs on DP's assembly section and finally works.  



    ------------------------------
    Burak Görener
    ist
    +90262646 50 11
    ------------------------------

    Original Message


Related Content