<div dir="ltr">Hmm, that error looks like corruption of some sort. How often does it happen?</div><br><div class="gmail_quote"><div dir="ltr">On Mon, 24 Sep 2018 at 16:59, Balu S <<a href="mailto:sbalu27@gmail.com">sbalu27@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Marc,<div><br></div><div>Thanks for your reply. If I republish the API, then it works. But if I have 100s of API, then it seems a quite a work.</div><div>I wish this can be auto registered when using export/import.</div><div><br></div><div>FYI, I noticed an old exception (which did not occur in 1.3.1) version when loading the custom plugin. It looks like it is related to snapshot versions.</div><div>I shall check further.</div><div><br></div><div><div>2018-09-24 16:16:57,376 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 82) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-h</div><div>ost./apiman-gateway-api: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./apiman-gateway-api: java.lang.RuntimeException: ja</div><div>va.lang.RuntimeException: java.lang.Exception: Invalid plugin file at: /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHO</div><div>T/apimancustom-failure.war/plugin.war</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:84)</div><div> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)</div><div> at java.util.concurrent.FutureTask.run(FutureTask.java:266)</div><div> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)</div><div> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)</div><div> at java.lang.Thread.run(Thread.java:748)</div><div> at org.jboss.threads.JBossThread.run(JBossThread.java:320)</div><div>Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.Exception: Invalid plugin file at: /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war</div><div> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:241)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:99)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)</div><div> ... 6 more</div><div>Caused by: java.lang.RuntimeException: java.lang.Exception: Invalid plugin file at: /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/</div><div>0.0.1-SNAPSHOT/apiman-custom-failure.war/plugin.war</div><div> at io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:314)</div><div> at io.apiman.gateway.platforms.war.WarEngineConfig.getPolicyFailureWriterClass(WarEngineConfig.java:212)</div><div> at io.apiman.gateway.platforms.war.WarGateway.loadFailureFormatter(WarGateway.java:70)</div><div> at io.apiman.gateway.platforms.war.WarGateway.init(WarGateway.java:56)</div><div> at io.apiman.gateway.platforms.war.listeners.WarGatewayBootstrapper.contextInitialized(WarGatewayBootstrapper.java:42)</div><div> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)</div><div> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:205)</div><div> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:174)</div><div> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)</div><div> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)</div><div> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)</div><div> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)</div><div> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:239)</div><div> ... 8 more</div><div>Caused by: java.lang.Exception: Invalid plugin file at: /data/wildfly-11.0.0.Final/standalone/data/apiman/plugins/org.test/apiman-custom-failure/0.0.1-SNAPSHOT/apiman-custom</div><div>-failure.war/plugin.war</div><div> at io.apiman.gateway.engine.impl.DefaultPluginRegistry.readPluginFile(DefaultPluginRegistry.java:309)</div><div> at io.apiman.gateway.engine.impl.DefaultPluginRegistry.loadPlugin(DefaultPluginRegistry.java:246)</div><div> at io.apiman.gateway.platforms.war.WarEngineConfig.loadConfigClass(WarEngineConfig.java:311)</div><div> ... 23 more</div></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 21, 2018 at 4:40 PM Marc Savy <<a href="mailto:marc.savy@redhat.com" target="_blank">marc.savy@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Have you tried republishing those APIs and/or migrating the api_gateway index?<br>
<br>
On 21 September 2018 at 15:04, Balu S <<a href="mailto:sbalu27@gmail.com" target="_blank">sbalu27@gmail.com</a>> wrote:<br>
> Further to this email.<br>
><br>
> The export/import tool provided in Apiman manager seems not complete. After<br>
> I have imported the apimanager configuration to new environment using the<br>
> tool, accessing the public API URL gives below error. It tries to check the<br>
> existence of API in the Elasticsearch. But the import/export tool never<br>
> imports anything to ES index.<br>
><br>
> Does it mean we have to explicitly migrate the existing ES index to new ES<br>
> server ?<br>
><br>
> io.apiman.gateway.engine.beans.exceptions.ApiNotFoundException: API not<br>
> found.<br>
> at<br>
> io.apiman.gateway.engine.impl.ApiRequestExecutorImpl.lambda$execute$5(ApiRequestExecutorImpl.java:340)<br>
> at<br>
> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:123)<br>
> at<br>
> io.apiman.gateway.engine.impl.SecureRegistryWrapper$1.handle(SecureRegistryWrapper.java:112)<br>
> at<br>
> <a href="http://io.apiman.gateway.engine.es" target="_blank">io.apiman.gateway.engine.es</a>.CachingESRegistry.getApi(CachingESRegistry.java:117)<br>
><br>
><br>
> On Tue, Sep 18, 2018 at 12:38 PM Balu S <<a href="mailto:sbalu27@gmail.com" target="_blank">sbalu27@gmail.com</a>> wrote:<br>
>><br>
>> Hi Eric, Marc,<br>
>><br>
>> I have used this export/import option in Apiman to migrate data from 1.3<br>
>> to 1.5.1 version.The tools works fine and I can see the apis, policies and<br>
>> client apps, users are created in migrated environment.<br>
>><br>
>> However if I notice, there are some config information stored in<br>
>> Elasticsearch under the index apiman_gateway. There are like 21 records for<br>
>> this index in Kibana. These data seems to resemble the client and api<br>
>> information.<br>
>><br>
>> What are these data ? Is the exported "api manager"data different from<br>
>> "apiman gateway" data ? If so why are these not migrated using export/import<br>
>> utility ?<br>
>><br>
>> Thanks for reading my post.<br>
>><br>
>> Best regards<br>
>> Balu.<br>
</blockquote></div>
</blockquote></div>