WSO2-AM 3.1.0 - 负载均衡端点未被添加。

问题描述 投票:0回答:1

我们在All in One HA部署配置上配置了两个WSO2AM节点。两个节点都工作正常,如果我们在节点1上添加一个API,节点2也显示API。我们使用IS作为KM,它也在HA上。

事实上,当我们试图在API上配置负载均衡端点时,我们遇到了问题。我们在API中添加了它,但保存更改后,端点没有配置。请看下面的截图。第一张截图是在配置负载均衡端点时。第二张截图是保存更改后的截图。

第一张图片First Image

第二张图片Second Image

正如你所看到的,最后端点没有配置好,或者只是没有保存。在图像上,端点显示为 "node1",但它被正确配置为http节点。

下面是WSO2AM节点的日志(wso2carbon.log)

TID: [-1234] [AuthenticationAdmin] [2020-06-08 13:21:51,723]  INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - '[email protected] [-1234]' logged in at [2020-06-08 13:21:51,723-0300]
TID: [-1234] [AuthenticationAdmin] [2020-06-08 13:21:52,093]  INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - '[email protected] [-1234]' logged in at [2020-06-08 13:21:52,093-0300]
TID: [-1234] [AuthenticationAdmin] [2020-06-08 13:21:52,196]  INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - '[email protected] [-1234]' logged in at [2020-06-08 13:21:52,196-0300]
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,587]  INFO {org.apache.synapse.rest.API} - Destroying API: admin--mdrestsolicitudnominado
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,592]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - API : admin--mdrestsolicitudnominado was removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,595]  INFO {org.apache.synapse.rest.API} - Destroying API: admin--mdrestsolicitudnominado:v1
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,597]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - API : admin--mdrestsolicitudnominado:v1 was removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,628]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--Fault was  removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,655]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--Out was  removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,656]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--In was  removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,659]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Local entry : 97617dba-2d20-43ff-a263-ae54d357d238 was removed from the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,659] ERROR {org.wso2.carbon.localentry.service.LocalEntryAdmin} - Entry with the key 97617dba-2d20-43ff-a263-ae54d357d238 does not exist
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,662]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Local entry : 97617dba-2d20-43ff-a263-ae54d357d238 was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,666]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Endpoint : mdrestsolicitudnominado--v1_APIproductionEndpoint was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,669]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Endpoint : mdrestsolicitudnominado--v1_APIsandboxEndpoint was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,726]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--Fault was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,734]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--Out was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,754]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - Sequence : admin--mdrestsolicitudnominado:v1--In was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,762]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - API : admin--mdrestsolicitudnominado:v1 was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,763]  INFO {org.apache.synapse.rest.API} - Initializing API: admin--mdrestsolicitudnominado:v1
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,773]  INFO {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} - API : admin--mdrestsolicitudnominado was added to the Synapse configuration successfully
TID: [-1234] [APIGatewayAdmin] [2020-06-08 13:21:52,773]  INFO {org.apache.synapse.rest.API} - Initializing API: admin--mdrestsolicitudnominado
TID: [-1234] [AuthenticationAdmin] [2020-06-08 13:21:52,814]  INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - '[email protected] [-1234]' logged in at [2020-06-08 13:21:52,814-0300]
TID: [-1] [] [2020-06-08 13:21:53,059]  INFO {org.wso2.carbon.databridge.core.DataBridge} - user admin connected
TID: [-1] [] [2020-06-08 13:21:53,062]  INFO {org.wso2.carbon.databridge.core.DataBridge} - user admin connected

为什么会出现这种情况?我检查了另一个日志,没有什么特别的地方。

如果你需要进一步的信息,请告诉我。

wso2 wso2-am
1个回答
2
投票

你必须点击输入框中的+按钮,以添加负载平衡或失败的端点。

© www.soinside.com 2019 - 2024. All rights reserved.