APIManager Prod issue help required
by Ashish Patel
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
6 years, 7 months
Apiman X-Fowarded-For on Simple Header Policy
by Renato Barros
Hi folks,
I'd like to know if there is some way to add the Client remote IP on my
Request Header from API Man.
I need to *add a Simple Header Policy with a "X-Forwarded-For" containing
the client remote ip*.
My backend is getting the APIMan IP as remote client, but what I need get
to client IP.
6 years, 7 months
Re: [Apiman-user] Transfer Quota Policy
by Ashish Patel
Hi Marc,
Sorry for sending direct mail, can you please help release below mail sent to group to all the audience ?
Thanks & Regards,
Ashish Patel
From: Ashish Patel
Sent: Friday, March 23, 2018 16:47
To: apiman-user(a)lists.jboss.org
Subject: Transfer Quota Policy
Hi,
I need small help understanding Transfer Quota policy.
Have applied transfer quota policy with below config - attached with one API , set up one client and tested with Rest Client.
“6000 Bytes” of “upload” data per “API” per “Second”.
1. Sent single request which has request payload (upload) > 6000 bytes - Instead of blocking it, it allowed the request and sent the response - However, Apiman is aware of the overshot transfer - can be seen from the Headers.
x-transferquota-limit →6000
x-transferquota-remaining →-4019
x-transferquota-reset →0
2. Sent back to back multiple request (same payload as above) and at times it failed with failure code : 10013, "Transfer quota exceeded.". This means it is applying the policy but after some requests , not sure how many.
x-policy-failure-code →10013
x-policy-failure-message →Transfer quota exceeded.
x-policy-failure-type →Other
x-powered-by →Undertow/1
x-transferquota-limit →6000
x-transferquota-remaining →-4019
x-transferquota-reset →0
Any idea, why it’s not failing in #1 scenario - Ideally it must fail in all requests as payload size is greater than defined.
Thanks & Regards,
Ashish Patel
6 years, 7 months
Transfer Quota Policy
by Ashish Patel
Hi,
I need small help understanding Transfer Quota policy.
Have applied transfer quota policy with below config - attached with one API , set up one client and tested with Rest Client.
“6000 Bytes” of “upload” data per “API” per “Second”.
1. Sent single request which has request payload (upload) > 6000 bytes - Instead of blocking it, it allowed the request and sent the response - However, Apiman is aware of the overshot transfer - can be seen from the Headers.
x-transferquota-limit →6000
x-transferquota-remaining →-4019
x-transferquota-reset →0
2. Sent back to back multiple request (same payload as above) and at times it failed with failure code : 10013, "Transfer quota exceeded.". This means it is applying the policy but after some requests , not sure how many.
x-policy-failure-code →10013
x-policy-failure-message →Transfer quota exceeded.
x-policy-failure-type →Other
x-powered-by →Undertow/1
x-transferquota-limit →6000
x-transferquota-remaining →-4019
x-transferquota-reset →0
Any idea, why it’s not failing in #1 scenario - Ideally it must fail in all requests as payload size is greater than defined.
Thanks & Regards,
Ashish Patel
6 years, 8 months
