restarting the container requires a republish of the api

[ayrtonsin]

Description:
when deploying the container wso2/wso2am:3.2.0-alpine (or centos) with seperate mysql db & following mounts the api is kept on container restart, however a republish/redeploy is required before the api is accessible again. The subscriptions & tokens still work.

• /home/wso2carbon/wso2am-3.2.0/repository/conf/deployment.toml
• /home/wso2carbon/wso2am-3.2.0/repository/components/dropins/mysql-connector-java-8.0.22.jar
• /home/wso2carbon/wso2am-3.2.0/repository/conf/axis2/axis2.xml
• /home/wso2carbon/wso2-tmp/synapse-configs
• /home/wso2carbon/wso2-tmp/executionplans
• /home/wso2carbon/wso2am-3.2.0/solr

Suggested Labels:

Suggested Assignees:

Affected Product Version:
wso2am:3.2.0

Steps to reproduce:

• start container
• configure an Api, publish, assign subscriptions, request a token (using postman), use token to access Api
• restart container
• use the token to acces the Api:
  <am:fault xmlns:am="http://wso2.org/apimanager"> <am:code>404</am:code> <am:type>Status report</am:type> <am:message>Not Found</am:message> <am:description>The requested resource is not available.</am:description> </am:fault>
• request new token (works)
• use new token
  <am:fault xmlns:am="http://wso2.org/apimanager"> <am:code>404</am:code> <am:type>Status report</am:type> <am:message>Not Found</am:message> <am:description>The requested resource is not available.</am:description> </am:fault>

Related Issues:

[rcusnir]

this can be fixed by move to persistent volume following folders:
<WSO2_CARBON_HOME>/repository/tenants
<WSO2_CARBON_HOME>/repository/deployment/server