尝试运行WSO2 API管理器3.1.0时收到错误

尝试运行WSO2 API管理器3.1.0时收到错误,wso2,wso2-am,Wso2,Wso2 Am,** [2020-09-16 13:25:32090]错误-尝试连接到终结点时发生DataEndpointConnectionWorker错误。无法借用客户的帐户ssl://10.1.31.61:9711. org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException:无法借用客户机ssl://10.1.31.61:9711. 在org.wso2.carbon.databridge.agent.endpoint.Dat

**

[2020-09-16 13:25:32090]错误-尝试连接到终结点时发生DataEndpointConnectionWorker错误。无法借用客户的帐户ssl://10.1.31.61:9711. org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException:无法借用客户机ssl://10.1.31.61:9711. 在org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:145)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]在org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.run(DataEndpointConnectionWorker.java:59)[.wso2.carbon.databridge.agent_5.2.24.jar:?]在java.util.concurrent.Executors$runnableapter.call(Executors.java:511)[?:1.8.0_261]在java.util.concurrent.FutureTask.run(FutureTask.java:266)[?:1.8.0_261]在java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[?:1.8.0_261]在java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.624)java.lang.Thread.run(Thread.java:748)上的[?:1.8.0_261]由以下原因引起的[?:1.8.0_261]:org.wso2.carbon.databridge.agent.exception.dataendpointlogin异常:尝试登录到数据接收器时出错:/10.1.31.61:9711,位于org.wso2.carbon.databridge.agent.endpoint.binary.rydataendpoint.login(BinaryDataEndpoint.java:50)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]位于org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:139)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]…另外6个原因是:org.wso2.carbon.databridge.commons.exception.AuthenticationException:java.lang.IllegalStateException:在sun.reflect.NativeConstructorAccessorImpl.newInstance0(本机方法)~[?:1.8.0ą]在sun.reflect.NativeConstructorAccessorImpl.newInstance上找不到适合本地声明的映射属性(NativeConstructorAccessorImpl.java:62)~[?:1.8.0_261]在sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)~[?:1.8.0_261]在java.lang.reflect.Constructor.newInstance(Constructor.java:423)~[?:1.8.0_261]在org.wso2.carbon.databridge.agent.endpoint.binary.BinaryEventSender.processResponse(BinaryEventSender.java:163)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]位于org.wso2.carbon.databridge.agent.endpoint.binary.BinaryDataEndpoint.login(BinaryDataEndpoint.java:44)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]位于org.wso2.carbon.databridge.agent.endpoint.dataendpoint.DataEndpointConnectionWorker.connectionworker.connect(DataEndpointConnectionWorker.java:139)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]…6更多[2020-09-16 13:25:32169]信息-QpidServiceComponent激活安第斯消息代理引擎…[Broker]BRK-1001:启动:版本:0.11构建:90784:90849[Broker]MNG-1001:启动[Broker]MNG-1004:准备:使用平台JMX代理[Broker]BRK-1002:开始:侦听TCP端口5672[2020-09-16 13:25:32878]信息-侦听[Broker]BRK-1002:开始:侦听TCP端口5672[Broker]BRK-1002:开始:侦听TCP/SSL端口8672[2020-09-16 13:25:32924]信息-侦听[Broker]BRK-1002:开始:侦听TCP/SSL端口8672[Broker]BRK-1004:Qpid代理就绪原因:org.wso2.carbon.databridge.commons.exception.AuthenticationException:java.lang.IllegalStateException:在sun.reflect.NativeConstructorAccessorImpl.newInstance0(本机方法)~[?:1.8.0\u 261]在sun.reflect.NativeConstructorAccessorImpl.newInstance上找不到适合本地声明的映射属性(NativeConstructorAccessorImpl.java:62)~[?:1.8.0_261]在sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)~[?:1.8.0_261]在java.lang.reflect.Constructor.newInstance(Constructor.java:423)~[?:1.8.0_261]在org.wso2.carbon.databridge.agent.endpoint.binary.BinaryEventSender.processResponse(BinaryEventSender.java:163)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]位于org.wso2.carbon.databridge.agent.endpoint.binary.BinaryDataEndpoint.login(BinaryDataEndpoint.java:44)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]位于org.wso2.carbon.databridge.agent.endpoint.dataendpoint.DataEndpointConnectionWorker.connectionworker.connect(DataEndpointConnectionWorker.java:139)~[org.wso2.carbon.databridge.agent_5.2.24.jar:?]
**

请检查以下通用配置:

  • 如果是分布式安装,请检查TM是否已启动并正在运行
  • 检查TM的端口是否正确,7611和7711是否打开
  • 根据TM检查节流相关凭证是否正确

  • 根据日志,索赔属性映射发生了更改。索赔似乎映射到了用户存储中不存在的属性。请检查并设置为正确的可用属性,

    您运行的是分布式还是无