没有在集群模式下商店中发布的API - WSO2 API管理2.0.0

Question

我部署的集群API经理2.0.0安装与五个VM：

VM1 共享密钥管理器+分析节点：

与运行

• 专用密钥管理器/var/wso2am/bin/wso2server.sh -Dprofile = API-密钥管理与默认端口运行
• wso2am分析偏移（1）由在/ var/wso2am-分析/ bin中/wso2server.sh

VM2

与默认运行专用网关节点偏移（0）由/var/wso2am/bin/wso2server.sh -Dprofile =网关管理器

VM3

通过/var/wso2am/var/wso2am/bin/wso2server.sh -Dprofile = api-store运行默认偏移量（+0）的专用存储节点

V M4与默认运行

专用业务管理器节点通过/var/wso2am/bin/wso2server.sh -Dprofile =交通管理器

VM5

专用出版商节点运行偏移（0）使用默认偏移（0）由/var/wso2am/bin/wso2server.sh -Dprofile = API-出版商

我完成所有步骤在Clustering API Manager 2.0.0

I S使用VM3和VM5设置两个群集节点，并在存储节点和发布程序节点上看到/ _system/governance/apimgt/applicationdata注册表。 我也可以浏览商店碳管理界面（元数据 - >列表> API>）上的发布者节点中创建的API

但是，在VM3（“VM3/store”）的专用存储前端没有出现API。

在，如果我打开出版商节点上“VM5 /存储”页面的同时，我可以看到发布的API就好

我应该怎么检查？

UPD：

这些API推到“创造”用错了生命周期状态店里节点未相应更新。我试图在商店节点上手动更改生命周期状态，并且API在商店模式下发布得很好。

所以看起来问题是生命周期状态实时更新存储节点。我该如何解决它？

UPD2：

这里是我的店配置axis2.xml（IP是x.x.x.15）

<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" 
       enable="true"> 
    <parameter name="membershipScheme">wka</parameter> 
    <parameter name="domain">wso2.carbon.domain</parameter> 
    <parameter name="localMemberHost">x.x.x.15</parameter> 
    <parameter name="localMemberPort">4000</parameter> 
     <members> 
      <member> 
       <hostName>x.x.x.17</hostName> 
       <port>4000</port> 
      </member> 
      <member> 
       <hostName>x.x.x.15</hostName> 
       <port>4000</port> 
      </member>    
     </members> 

`

这里是我的出版商配置axis2.xml（IP是xxx17）在存储日志文件

<clustering class="org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent" 
       enable="true"> 
    <parameter name="membershipScheme">wka</parameter> 
    <parameter name="domain">wso2.carbon.domain</parameter> 
    <parameter name="localMemberHost">x.x.x.17</parameter> 
    <parameter name="localMemberPort">4000</parameter> 

     <members> 
      <member> 
       <hostName>x.x.x.15</hostName> 
       <port>4000</port> 
      </member> 
      <member> 
       <hostName>x.x.x.17</hostName> 
       <port>4000</port> 
      </member>    
     </members> 

消息

Cluster domain: wso2.carbon.domain 
    Loading hazelcast configuration from axis2 clustering configuration 
    Using wka based membership management scheme 
    Added member: Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true 
    Added member: Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true 
    Hazelcast initialized in 9167ms 
    Local member: [3c9c1b66-9ad9-4e4f-8d7e-de2864e8d56d] - Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:8280, HTTPS:8243, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true 
    Cluster initialization completed 
    Task service starting in CLUSTERED mode... 
    Successfully Initialized Eventing on Registry 

消息在发布者日志文件

Cluster domain: wso2.carbon.domain 
Loading hazelcast configuration from axis2 clustering configuration 
Using wka based membership management scheme 
Added member: Host:x.x.x.15, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true 
Added member: Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true 
Hazelcast initialized in 10380ms 
Local member: [094f544b-1cfe-41b1-9a5f-0664aefc1ba5] - Host:x.x.x.17, Remote Host:null, Port: 4000, HTTP:8280, HTTPS:8243, Domain: wso2.carbon.domain, Sub-domain:worker, Active:true 
Cluster initialization completed 
Error in instantiating class : org.wso2.carbon.apimgt.usage.publisher.APIMgtThrottleUsageHandler 
Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed. 
Deployment of the Synapse Artifact from file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed! 
The file has been backed up into : NO_BACKUP_ON_WORKER.INFO 
Deployment of synapse artifact failed. Error reading /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed. 
org.apache.axis2.deployment.DeploymentException: Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/_throttle_out_handler_.xml : Failed. 
Error in instantiating class : org.wso2.carbon.apimgt.usage.publisher.APIMgtFaultHandler 
Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed. 
Deployment of the Synapse Artifact from file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed! 
The file has been backed up into : NO_BACKUP_ON_WORKER.INFO 
Deployment of synapse artifact failed. Error reading /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed. 
org.apache.axis2.deployment.DeploymentException: Sequence Deployment from the file : /var/wso2am/repository/deployment/server/synapse-configs/default/sequences/fault.xml : Failed. 
Task service starting in CLUSTERED mode... 
Successfully Initialized Eventing on Registry 

Answer 1

可能有2个原因。

1）使用axis2.xml中<localMemberHost>和<members>部分的主机名。改用IP。

2）不具有存储和出版商对于<parameter name="domain">wso2.carbon.domain</parameter>在axis2.xml

更新相同的值： 连接的配置看起来很好。所以另一种可能性是这是一个注册表索引问题。为此，您可以尝试重新索引。

更新<lastAccessTimeLocation>registry.xml的值存储在这样的节点中，然后重新启动服务器。

<lastAccessTimeLocation>/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime2</lastAccessTimeLocation>