<div dir="ltr">Hello, <div><br></div><div>rm ${APIMAN_HOME}/standalone/deployments/apiman-es.war<br></div><div><br></div><div>Removing the deployment is all you need to do. </div><div><br></div><div>Jakub.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 14, 2015 at 11:57 AM, Tim Dudgeon <span dir="ltr"><<a href="mailto:tdudgeon.ml@gmail.com" target="_blank">tdudgeon.ml@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK, I tried that and now the gateway is working after a restart.<br>
I have no idea why is didn't work when running with the built in ES.<br>
<br>
Now one more question - how to disable the ES within apiman (I mean stop<br>
it running, not reconfigure the connection)?<br>
<span class="HOEnZb"><font color="#888888"><br>
Tim<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 13/10/2015 14:50, Eric Wittmann wrote:<br>
> Since you have to do it anyway, I'd suggest going with an external<br>
> elasticsearch instance. It's easy to hook apiman up to it. It's just<br>
> a couple properties in apiman.properties.<br>
><br>
> -eric<br>
><br>
> On 10/13/2015 9:48 AM, Tim Dudgeon wrote:<br>
>> If you restart a container it will contain the same state as when it was<br>
>> stopped.<br>
>> If you were to create a new container from the image it would of course<br>
>> not contain the state of other containers created from that image<br>
>> (unless you were re-using volumes).<br>
>><br>
>> And with the jboss/apiman-wildfly image its working OK. I stop the<br>
>> container and restart it and the gateway is configured.<br>
>> But in my image, adapted from that image the gateway looses it<br>
>> configuration, so its clearly something I've done. I just don't know<br>
>> what.<br>
>><br>
>> What I've discovered so far is that when restarted ES contains<br>
>> information in the apiman_manger index but has lost all info in the<br>
>> apiman_gateway index.<br>
>><br>
>> Tim<br>
>><br>
>><br>
>> On 13/10/2015 13:44, Marc Savy wrote:<br>
>>> Not a container expert either, but:<br>
>>><br>
>>> I think it's standard practice for containers to be non-persistent<br>
>>> (i.e. no persistent state), so you'd need an external ES instance. or<br>
>>> set the ES data-store to be on a data volume (which is persistent).<br>
>>><br>
>>> Regards,<br>
>>> Marc<br>
>>><br>
>>> On 13/10/2015 12:57, Eric Wittmann wrote:<br>
>>>> Hm. Without digging into it, I'm not sure what to suggest. I'm also<br>
>>>> not a docker expert by any stretch, so that complicates things. :)<br>
>>>><br>
>>>> I can tell you that the default elasticsearch instance that comes with<br>
>>>> the apiman quickstart stores data in the standalone/data/es directory.<br>
>>>> You could perhaps poke around that area. See if data is getting<br>
>>>> written<br>
>>>> there, and whether it's still there when you restart the container?<br>
>>>><br>
>>>> -Eric<br>
>>>><br>
>>>><br>
>>>> On 10/13/2015 7:37 AM, Tim Dudgeon wrote:<br>
>>>> > Right now I'm using the ES that's bundled with Apiman (though do<br>
>>>> intend<br>
>>>> > to switch to a separate container).<br>
>>>> > The baffling thing is that with the Docker image on Dockerhub<br>
>>>> > (jboss/apiman-wildfly) it restarts OK, but with my partly Dockerised<br>
>>>> > version (with Keycloak and Postgres currently as separate<br>
>>>> containers) it<br>
>>>> > fails. The APIMan and ES parts are still pretty well the same as the<br>
>>>> > jboss/apiman-wildfly image.<br>
>>>> ><br>
>>>> > So I seem to have messed something up, but don't have much of an<br>
>>>> idea as<br>
>>>> > to what.<br>
>>>> ><br>
>>>> > Tim<br>
>>>> ><br>
>>>> > On 13/10/2015 12:23, Eric Wittmann wrote:<br>
>>>> >> When a service is published to the gateway, that configuration is<br>
>>>> >> saved in the gateway's persistent registry. By default (in the<br>
>>>> latest<br>
>>>> >> version of apiman) the gateway uses elasticsearch to store its<br>
>>>> >> registry information. So ideally you should run elasticsearch as a<br>
>>>> >> separate docker container, making sure that you have an appropriate<br>
>>>> >> persistent volume attached so that any data added to ES survives a<br>
>>>> >> docker restart. Then you can configure apiman to use that<br>
>>>> external ES.<br>
>>>> >><br>
>>>> >> There is documentation in the Installation Guide that explains<br>
>>>> how to<br>
>>>> >> use an external elasticsearch cluster.<br>
>>>> >><br>
>>>> >> -Eric<br>
>>>> >><br>
>>>> >> On 10/11/2015 7:30 AM, Tim Dudgeon wrote:<br>
>>>> >>> I'm hitting a problem where I'm running apiman in a docker<br>
>>>> container.<br>
>>>> >>> When I first set up a public service it runs fine.<br>
>>>> >>> But when I restart the container the service definition is still<br>
>>>> there,<br>
>>>> >>> but the gateway does not respond to requests for the service. If I<br>
>>>> >>> create a new version of the service and publish it then it works<br>
>>>> fine.<br>
>>>> >>><br>
>>>> >>> Seems like the service definition is not being published to the<br>
>>>> gateway<br>
>>>> >>> after a restart?<br>
>>>> >>> I've tried it with the basic Docker container similar to<br>
>>>> >>> jboss/apiman-wildfly on Dockerhub and it seems OK with that, so<br>
>>>> it looks<br>
>>>> >>> like its something I've done to cause this, but I don't see any<br>
>>>> errors<br>
>>>> >>> and don't know where to look to try to fix it.<br>
>>>> >>> Any ideas what's wrong?<br>
>>>> >>> This is with version 1.1.8.Final.<br>
>>>> >>><br>
>>>> >>> Tim<br>
>>>> >>><br>
>>>> >>> _______________________________________________<br>
>>>> >>> Apiman-user mailing list<br>
>>>> >>> <a href="mailto:Apiman-user@lists.jboss.org">Apiman-user@lists.jboss.org</a><br>
>>>> >>> <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
>>>> >>><br>
>>>> ><br>
>>>> > _______________________________________________<br>
>>>> > Apiman-user mailing list<br>
>>>> > <a href="mailto:Apiman-user@lists.jboss.org">Apiman-user@lists.jboss.org</a><br>
>>>> > <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
>>>> ><br>
>>>> _______________________________________________<br>
>>>> Apiman-user mailing list<br>
>>>> <a href="mailto:Apiman-user@lists.jboss.org">Apiman-user@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
>>>><br>
>>><br>
>><br>
<br>
_______________________________________________<br>
Apiman-user mailing list<br>
<a href="mailto:Apiman-user@lists.jboss.org">Apiman-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/apiman-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/apiman-user</a><br>
</div></div></blockquote></div><br></div>