[Apiman-user] Failing Service

Eric Wittmann eric.wittmann at redhat.com
Thu Sep 17 08:05:17 EDT 2015


Are you using a standalone instance of elastic or the one that comes 
with the apiman quickstart.  The quickstart is only intended as a way to 
get started evaluating apiman.  The production guide describes how 
better to configure apiman for prod.

-Eric

On 9/16/2015 6:00 PM, Fadi Abdin wrote:
> Hi Marc,
>
> I followed your recommendation and installed apiman database everything
> is connected and i'm able to create a new services and i see them in the
> database and the apiman gateway in Elastic search. is that what you was
> saying ?
>
> I also noticed that the Elastic Search UI plugin you was recommended was
> working fine in the previous version 1.1.8-SNAPSHOT , but recently i
> installed 1.1.8.Final and i'm getting a cors issue . I'm using the
> standalone elastic search ui and not the plugin. When i googled it a bit
> , it seems there are some properties need to be added to the
> elasticsearch.yml to enable cors.
>
>
>
> On Tue, Sep 8, 2015 at 2:45 PM, Eric Wittmann <eric.wittmann at redhat.com
> <mailto:eric.wittmann at redhat.com>> wrote:
>
>     Hi Fadi.
>
>     It looks like you're using all the apiman quickstart defaults, so
>     that's OK.  I wonder - are you trying to build apiman on the same
>     machine?
>
>     Also: it would be interesting to get the output from this:
>
>     http://localhost:19200/apiman_gateway/service/_search?pretty=true
>
>     -Eric
>
>     PS: if this system is running in production you should refer to our
>     production guide for help with a more appropriate configuration:
>
>     http://www.apiman.io/latest/production-guide.html
>
>     On 9/8/2015 1:47 PM, Fadi Abdin wrote:
>
>         here is it attached .. , do you see anything weird ?
>
>         On Tue, Sep 8, 2015 at 9:50 AM, Eric Wittmann
>         <eric.wittmann at redhat.com <mailto:eric.wittmann at redhat.com>
>         <mailto:eric.wittmann at redhat.com
>         <mailto:eric.wittmann at redhat.com>>> wrote:
>
>              +1 - we definitely need more information here.  :)
>
>
>              On 9/6/2015 10:09 AM, Marc Savy wrote:
>
>                  Will need a lot more information than this to
>         understand what's
>                  going on.
>
>                  1) Which version are you using (apiman & plugins)
>                  2) Gist your apiman.properties (feel free to delete any
>                  sensitive info)
>                  3) Provide a more detailed on  your ES setup. Do you
>         set it to
>                  delete old records (age-based reaping)? Could someone
>         have reset
>                  the DB overnight? i.e. use a UI tool like
>         https://mobz.github.io/elasticsearch-head/ to see what data is
>                  in there.
>
>                  ----- Original Message -----
>                  From: "Fadi Abdin" <fadiabdeen at gmail.com
>         <mailto:fadiabdeen at gmail.com>
>                  <mailto:fadiabdeen at gmail.com
>         <mailto:fadiabdeen at gmail.com>>>
>                  To: "apiman-user" <apiman-user at lists.jboss.org
>         <mailto:apiman-user at lists.jboss.org>
>                  <mailto:apiman-user at lists.jboss.org
>         <mailto:apiman-user at lists.jboss.org>>>
>                  Sent: Sunday, 6 September, 2015 12:56:11 PM
>                  Subject: [Apiman-user] Failing Service
>
>                  Hey Guys,
>
>                  for one of the setup servers , i have woke up friday with a
>                  failing service .. nothing really changed overnight on
>         Friday
>
>                  /3.1/....
>
>                  All i did is create a new version of the service and
>         publishing it
>                  /3.2/....
>
>                  and here is my exception, do you have any explanation
>         or thinks
>                  might make this happened that i can investigate and
>         avoid ? :
>
>         io.apiman.gateway.engine.beans.exceptions.InvalidServiceException:
>                  Service not found.
>                           at
>
>         io.apiman.gateway.engine.impl.ServiceRequestExecutorImpl$3.handle(ServiceRequestExecutorImpl.java:261)
>                           at
>
>         io.apiman.gateway.engine.impl.ServiceRequestExecutorImpl$3.handle(ServiceRequestExecutorImpl.java:255)
>                           at
>
>         io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:107)
>                           at
>
>         io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:97)
>                           at io.apiman.gateway.engine.es
>         <http://io.apiman.gateway.engine.es>
>
>         <http://io.apiman.gateway.engine.es>.ESRegistry$10.completed(ESRegistry.java:415)
>                           at io.apiman.gateway.engine.es
>         <http://io.apiman.gateway.engine.es>
>
>         <http://io.apiman.gateway.engine.es>.ESRegistry$10.completed(ESRegistry.java:407)
>
>                           at
>
>         io.searchbox.client.http.JestHttpClient$DefaultCallback.completed(JestHttpClient.java:195)
>                           at
>
>         io.searchbox.client.http.JestHttpClient$DefaultCallback.completed(JestHttpClient.java:178)
>                           at
>
>         org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119)
>                           at
>
>         org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177)
>                           at
>
>         org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:412)
>                           at
>
>         org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:305)
>                           at
>
>         org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:267)
>                           at
>
>         org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
>                           at
>
>         org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
>                           at
>
>         org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:116)
>                           at
>
>         org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164)
>                           at
>
>         org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:339)
>                           at
>
>         org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317)
>                           at
>
>         org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278)
>                           at
>
>         org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
>                           at
>
>         org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590)
>                           at java.lang.Thread.run(Thread.java:745)
>
>
>
>
>                  _______________________________________________
>                  Apiman-user mailing list
>         Apiman-user at lists.jboss.org <mailto:Apiman-user at lists.jboss.org>
>         <mailto:Apiman-user at lists.jboss.org
>         <mailto:Apiman-user at lists.jboss.org>>
>         https://lists.jboss.org/mailman/listinfo/apiman-user
>                  _______________________________________________
>                  Apiman-user mailing list
>         Apiman-user at lists.jboss.org <mailto:Apiman-user at lists.jboss.org>
>         <mailto:Apiman-user at lists.jboss.org
>         <mailto:Apiman-user at lists.jboss.org>>
>         https://lists.jboss.org/mailman/listinfo/apiman-user
>
>
>


More information about the Apiman-user mailing list