[Apiman-user] Any expiry settings for Clients ?
Ashish Patel
ashish.patel at futuregroup.in
Thu Aug 10 06:19:31 EDT 2017
Thanks Marc.
Yes I can see apiman_gateway index there. It's QA setup so using embedded ES/KeyCloak. Another update is Issue doesn't go after restarting services.
Thanks & Regards,
Ashish Patel
(M) +91 93270 15128
-----Original Message-----
From: Marc Savy [mailto:marc.savy at redhat.com]
Sent: Thursday, August 10, 2017 15:15
To: Ashish Patel
Cc: apiman-user at lists.jboss.org
Subject: Re: [Apiman-user] Any expiry settings for Clients ?
Correction:
> and seeing whether the `apiman-gateway` index is there
Should read:
> and seeing whether the `apiman_gateway` index is there
On 10 August 2017 at 10:43, Marc Savy <marc.savy at redhat.com> wrote:
> It sounds like someone might have accidentally deleted your gateway's
> indexes in Elasticsearch.
>
> Apiman Gateway and Apiman Manager have separate storage (even if you
> use the same Elasticsearch instance, they have separate indices).
>
> I suggest looking into your ES instance (using a management tool like
> elasticsearch-head might be helpful [1]) and seeing whether the
> `apiman-gateway` index is there, and that it contains the entries you
> expect.
>
> If you are feeling more adventurous, then you might try find the
> following query useful[2]:
>
> curl -XGET '<YOUR_ELASTICSEARCH>:9200/apiman_gateway/_search?pretty'
> -H 'Content-Type: application/json' -d'
> {
> "query": { "match_all": {} }
> }
> '
>
> Regards,
> Marc
>
> [1] https://github.com/dzharii/awesome-elasticsearch
> [2]
> https://www.elastic.co/guide/en/elasticsearch/reference/current/_intro
> ducing_the_query_language.html
>
> On 10 August 2017 at 10:18, Ashish Patel <ashish.patel at futuregroup.in> wrote:
>> Hi,
>>
>>
>>
>> We recently faced a strange issue on our APIman setup (QA/UAT
>> environment so far). Suddenly one by one (not all APIs yet) API
>> Clients are complaining that they are getting below exception. Here,
>> none of the Client details (register / unregister) changed under
>> APIManUI and even though below exception. The fix we applied
>> selectively is, break any one API from client and add the same again
>> through “New Contract” -> it will enable the “Re-Register” button ->
>> click it and issue is resolved. This leads me to think, is there any
>> Client API expiry settings – after which we have to re-register the client ? OR am I missing something here ?
>>
>>
>>
>> Any help is greatly appreciated.
>>
>>
>>
>> App Server: Wildfly 10.0.0-Final
>>
>> APIMan: 1.2.7.Final
>>
>> OS: Ubuntu
>>
>>
>>
>> Exception:
>>
>>
>>
>> [apiResponse] => Array
>>
>> (
>>
>> [responseCode] => 500
>>
>> [message] => No client found for API Key
>> 9c561c16-e866-44fe-b5d6-c11c5629f0d6
>>
>> [trace] =>
>> io.apiman.gateway.engine.beans.exceptions.InvalidContractException:
>> No client found for API Key 9c561c16-e866-44fe-b5d6-c11c5629f0d6
>>
>> at
>> io.apiman.gateway.engine.es.CachingESRegistry.getContract(CachingESRe
>> gistry.java:78)
>>
>> at
>> io.apiman.gateway.engine.impl.SecureRegistryWrapper.getContract(Secur
>> eRegistryWrapper.java:154)
>>
>> at
>> io.apiman.gateway.engine.impl.ApiRequestExecutorImpl.execute(ApiReque
>> stExecutorImpl.java:357)
>>
>> at
>> io.apiman.gateway.platforms.servlet.GatewayServlet.doAction(GatewaySe
>> rvlet.java:179)
>>
>> at
>> io.apiman.gateway.platforms.servlet.GatewayServlet.service(GatewaySer
>> vlet.java:79)
>>
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>>
>> at
>> io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHand
>> ler.java:85)
>>
>> at
>> io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.hand
>> leRequest(ServletSecurityRoleHandler.java:62)
>>
>> at
>> io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(
>> ServletDispatchingHandler.java:36)
>>
>>
>>
>>
>>
>> Thanks & Regards,
>>
>> Ashish Patel
>>
>>
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/apiman-user
>>
More information about the Apiman-user
mailing list