-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In one api fails, all other edge functionality gets blocked #339
Comments
@ravindrasingh22 thanks for logging the issue. To help us reproduce the issue, could you share details of the error thrown by edge when the product fetch fails? You can enable debug module to get the response from edge: https://www.drupal.org/docs/8/modules/apigee-edge/monitor-apigee-edge-debug-logs |
its 500 error on apigee for that particular api product with message. The way simple way to simulate the apiproducts error is put the dummy reponse in api call |
Thanks @ravindrasingh22 for sharing the error details. - we will prioritize this issue in our current sprint and update soon. |
Thanks for the details @ravindrasingh22. I'd like to point out that the API products are not synced into Drupal, they are remote entities (read from Edge), and if configured within Drupal, only cached temporarily to improve performance.
From your comment, it looks like the error is getting thrown on step 2, when specifying the |
@arlina-espinoza - Yes, you understood correctly, there is an issue on Edge only with one specific which I can't fix/delete that. [Request is already raised on APIGEE support for that], but my concern is one buggy product should not block the other functionalities. And being a coder I feel it is doable on this edge module. it should capture that product in logs like unable to fetch XXX product. but it should not block other functionality. |
I think we can update the code that does the listing so that if a call with
And also what is the ID of the product that is failing, to see if it could be causing an issue when URL encoding it? |
@ravindrasingh22 I posted a PR for this, feel free to try and let us know your feedback: #340 |
@arlina-espinoza - I have tested your PR I still get the same problem. { |
From Drupal this is the log - |
@ravindrasingh22 this issue seems to be a problem with the Edge API, and it seems like the fix should be on the API side instead of us putting in code changes to work around this bug for all paging API calls where this could happen. I would also like to get more details on the root cause of the issue that you are seeing. Would you be able to give me the case # you put into support for this issue? Feel free to email me directly if you do not want to share the case in this issue. Thanks! |
I am going to close this ticket since there is a ticket in to Apigee support to fix the Apigee API that we call, but let us know if you need more help @ravindrasingh22 by adding more comments. It is hard to fix this issue since we cannot reproduce it without access to your org with this error, too bad @arlina-espinoza 's fix did not help the issue. |
Describe the bug
APIGEE edge executes management APIs to fetch API products, developers etc.
If the endpoint for API product fails with some particular product detail fetch somehow it is not allowing developers to do anything else on the page.
To Reproduce
1- There is a private product on the instance that has some issue on APIGEE cloud.
2- When I enable the module it fetches all of the products available on apigee orgs
3- When a particular product comes in a loop system start throwing en error and page doesn't get executed.
Expected behavior
If there is an error on a particular product should not be synced to the devportal rest of the product should work fine.
Version Info
8.x-1.6 Apigee Edge module.
The text was updated successfully, but these errors were encountered: