【问题标题】:Unable to start WSO2 API Manager with Traffic Manager Profile无法使用流量管理器配置文件启动 WSO2 API 管理器
【发布时间】:2020-08-21 13:00:44
【问题描述】:

我正在分布式设置中配置 WSO2 API Manager 3.1.0 的开源版本。我已完成所有配置,但是当我尝试使用流量管理器(或任何其他配置文件)启动 API 管理器时,我收到以下错误。

 org.apache.axis2.AxisFault: Exception occured while loading the Axis configuration from /wso2am-3.1.0/repository/conf/axis2/axis2.xml
        at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:194) ~[org.wso2.carbon.core_4.6.0.jar:?]
        at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65) ~[org.wso2.carbon.core_4.6.0.jar:?]
        at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:415) [org.wso2.carbon.core_4.6.0.jar:?]
        at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:305) [org.wso2.carbon.core_4.6.0.jar:?]
        at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118) [org.wso2.carbon.core_4.6.0.jar:?]
        at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:973) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) [org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
Caused by: org.apache.axis2.deployment.DeploymentException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v41
        at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:713) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:125) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341) ~[org.wso2.carbon.core_4.6.0.jar:?]
        at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192) ~[org.wso2.carbon.core_4.6.0.jar:?]
        ... 8 more
Caused by: java.lang.ClassNotFoundException: org.apache.synapse.transport.passthru.PassThroughHttpSender cannot be found by axis2_1.6.1.wso2v41
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:512) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:423) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:415) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:155) ~[org.eclipse.osgi_3.14.0.v20190517-1309.jar:?]
        at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
        at java.lang.Class.forName0(Native Method) ~[?:?]
        at java.lang.Class.forName(Class.java:315) ~[?:?]
        at org.apache.axis2.util.Loader.loadClass(Loader.java:261) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:687) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:125) ~[axis2_1.6.1.wso2v41.jar:?]
        at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341) ~[org.wso2.carbon.core_4.6.0.jar:?]
        at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192) ~[org.wso2.carbon.core_4.6.0.jar:?]
        ... 8 more

请让我知道我必须做哪些更改才能顺利启动服务器。

提前致谢。

【问题讨论】:

  • 它抱怨axis2.xml 配置不正确。你有没有以任何方式改变这个?
  • 不,我没有改变它。当我在一个 API Manager 中启动时,它会毫无问题地启动。每当我从特定配置文件(在本例中为流量管理器配置文件)开始时,就会出现此问题。
  • 运行以前版本的 API manager 是否也会出现此错误?
  • 是的,在以前的版本中,尝试启动流量管理器时也会出现这种情况。

标签: wso2 wso2-am


【解决方案1】:

尝试按照这些步骤来避免此错误

  1. 解压缩一个新的发行版,不要启动它,
  2. 导航到 APIM-HOME/bin 文件夹并运行 sh profileSetup.sh -Dprofile=traffic-manager 这将删除流量管理器不需要的文件和配置
  3. 接下来将您的配置添加到 deployment.toml 中,流量管理器和密钥库配置只需要共享数据库
  4. 启动服务器sh wso2server.sh -Dprofile=traffic-manager

【讨论】:

  • 嗨@dushansilva,我为 api-publisher 配置文件尝试了相同的步骤,但问题仍然存在。发布者资料还有其他事情要做吗?
  • @PrabakaranThodithotSembiyan 你还有这个问题吗?
  • 不@Jananath Banuka
【解决方案2】:
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多