[Apiman-user] APIManager Prod issue help required

[Marc Savy]

Ashish/anyone else,

Just to follow up: did this solution work as expected for you?

On 9 March 2018 at 13:07, Marc Savy <marc.savy at redhat.com> wrote:
> You can set it in the API endpoint properties as:
>
> timeouts.read
> timeouts.connect
>
> Regards,
> Marc
>
> On 2 March 2018 at 17:38, Eric Wittmann <eric.wittmann at redhat.com> wrote:
>> I can't remember if there is a way to configure per-API timeouts in the
>> Gateway.
>>
>> @marcsavy any thoughts on that?
>>
>> On Fri, Mar 2, 2018 at 9:56 AM, Ashish Patel <ashish.patel at futuregroup.in>
>> wrote:
>>>
>>> Thanks Eric.
>>>
>>>
>>>
>>> Yes, after bit diagnosing found that one of our production API source was
>>> down/timing out (we have set timeout in apiman config) as we got just too
>>> many hits for same API and this has caused Production APIMan Wildfly server
>>> also clogging other requests.
>>>
>>>
>>>
>>> Though we resolved problem by solving thhe said Production API source –
>>> was wandering is that any way we can isolate the API response time issue
>>> only for the impacted API and not others (like in this case it impacted all
>>> API requests including from API Manager).
>>>
>>>
>>>
>>> I could think of one option to resolve is to  configure low timeouts in
>>> apiman config and also specifying API specific timeout to override if
>>> required (like for said Production API the timeout was higher due to it’s a
>>> Legacy App). Will that be enough ? how can we do it in APIMan ? or any other
>>> suggestions ?
>>>
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Ashish Patel
>>>
>>> (M) +91 93270 15128
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: Eric Wittmann [mailto:eric.wittmann at redhat.com]
>>> Sent: Thursday, March 01, 2018 03:15
>>> To: Ashish Patel
>>> Cc: apiman-user at lists.jboss.org
>>> Subject: Re: [Apiman-user] APIManager Prod issue help required
>>>
>>>
>>>
>>> What's happening when you ask the API Manager for the endpoint is that the
>>> manager tries to make an HTTP connection to the Gateway that the API has
>>> been published to.  The assumption is that the Gateway knows its own
>>> external URL and is therefore the only party that can report it.
>>>
>>>
>>>
>>> The error stack trace indicates that the HTTP connection between the
>>> manager and gateway resulted in a 502 error (Bad Gateway).
>>>
>>>
>>>
>>> Has anything changed with your deployed Gateway?  Can you still publish
>>> APIs to that Gateway?  You could try going to the Gateway admin page and try
>>> "testing" the Gateway link from there.
>>>
>>>
>>>
>>> -Eric
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Feb 28, 2018 at 2:22 AM, Ashish Patel
>>> <ashish.patel at futuregroup.in> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>> Issue help required: We are using APIMan 1.2.7 in production with Wildfly
>>> 10.
>>>
>>>
>>>
>>> In APIManager UI, I can see all API details, however whenever I click on
>>> Endpoin, I get below error. Even when I click on APIManager -> ClientApp ->
>>> click on APIs, it breaks with 500 page error. Any help on this is highly
>>> appreciated.
>>>
>>>
>>>
>>> io.apiman.manager.api.rest.contract.exceptions.SystemErrorException:
>>> java.lang.RuntimeException: Failed to get the API endpoint: 502
>>>
>>>                 at
>>> io.apiman.manager.api.rest.impl.OrganizationResourceImpl.getApiVersionEndpointInfo(OrganizationResourceImpl.java:1937)
>>>
>>>                 at
>>> io.apiman.manager.api.rest.impl.OrganizationResourceImpl$Proxy$_$$_WeldClientProxy.getApiVersionEndpointInfo(Unknown
>>> Source)
>>>
>>>                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> Method)
>>>
>>>                 at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>
>>>                 at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>>                 at java.lang.reflect.Method.invoke(Method.java:498)
>>>
>>>                 at
>>> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
>>>
>>>                 at
>>> org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295)
>>>
>>>                 at
>>> org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvok
>>>
>>> ….
>>>
>>>
>>>
>>> Caused by: java.lang.RuntimeException: Failed to get the API endpoint: 502
>>>
>>>                 at
>>> io.apiman.manager.api.gateway.rest.GatewayClient.getApiEndpoint(GatewayClient.java:120)
>>>
>>>                 at
>>> io.apiman.manager.api.gateway.rest.RestGatewayLink.getApiEndpoint(RestGatewayLink.java:156)
>>>
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Ashish Patel
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Apiman-user mailing list
>>> Apiman-user at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>