首页 文章

如何更改WSO2 Enterprise Integrator的部署顺序

提问于
浏览
0

在我的ESB项目中,我有很多数据服务和代理服务 . 代理服务按顺序调用数据服务 . 在版本5.x.x中,DSS和ESB是分开的,但是从EI 6.x.x它们相互组合 . 问题是当我启动EI时,代理服务是在数据服务之前部署的 . EI找不到名为Data Services的服务,因此无法部署Proxy Services .

我是guest,我必须修复部署顺序,以便Data Services在代理服务之前启动 . 我怎么能这样做?

以下是部署的代理服务失败之一:

TID:[ - 1234] [] [2017-11-03 08:14:35,121] INFO - 为代理服务构建Axis服务:COMPLAIN_px TID:[ - 1234] [] [2017-11-03 08:14:35,122] ERROR - 从wsdl URI {org . apache.synapse.core.axis2.ProxyService} java.net.ConnectException:在java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)的java.net.PlainSocketImpl.socketConnect(Native Method)处拒绝连接(连接被拒绝)at java.net.SocksSocketImpl.connect(AbstractPlainSocketImpl.java:206)java.net.SocksSocketImpl.connect(AbstractPlainSocketImpl.java:188)java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)java.net.Socket上的java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) .connect(Socket.java:589)at sun.net.NetworkClient.doConnect(NetworkClient.java:175)at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)at sun.net.www . http.HttpClient.openServe r(HttpClient.java:558)at sun.net.www.http.HttpClient . (HttpClient.java:242)at sun.net.www.http.HttpClient.New(HttpClient.java:339)at sun.net . www.http.HttpClient.New(HttpClient.java:357)在sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)在sun.net.www.protocol.http.HttpURLConnection.plainConnect0( HttpURLConnection.java:1138)at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)at sun .net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1546)在sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)在org.apache.synapse.config.SynapseConfigUtils .getOMElementFromURL(SynapseConfigUtils.java:316)在org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:318)在org.apache.synapse.Axis2SynapseController.deployProxyServices(Axis2SynapseController.jav一:701)在org.apache.synapse.Axis2SynapseController.createSynapseEnvironment(Axis2SynapseController.java:390)在org.apache.synapse.ServerManager.start(ServerManager.java:182)在org.wso2.carbon.mediation.initializer.ServiceBusInitializer .initESB(ServiceBusInitializer.java:468)atg.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:206)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)在sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)在java.lang.reflect.Method.invoke(Method.java:498)在org.eclipse.equinox.internal.ds . 在org.eclipse.equinox.internal.ds.model.ServiceComponentProp的org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)上的model.ServiceComponent.activate(ServiceComponent.java:260) . 在org.eclipse.equinox.internal.ds.In上构建(ServiceComponentProp.java:345) stanceProcess.buildComponent(InstanceProcess.java:620)atg.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java: 343)org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)atg.eclipse.osup.invice.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)org.eclipse.osgi .framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)在org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)在org.eclipse.osgi.framework.eventmgr.ListenerQueue .dispatchEventSynchronous(ListenerQueue.java:148)位于org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)at at或者在org.eclipse.osgi.internal的org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)上的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) . serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)位于org.eclipse.osgi.framework.internal.core.BundleContextImpl的org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) . registerService(BundleContextImpl.java:451)位于sun.reflect的sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)的org.wso2.carbon.inbound.endpoint.persistence.service.InboundEndpointPersistenceServiceDSComponent.activate(InboundEndpointPersistenceServiceDSComponent.java:49) . NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)位于org.eclipse.equin的java.lang.reflect.Method.invoke(Method.java:498)的sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)位于org.eclipse.equinox.internal的org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) . ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)atg.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents( InstanceProcess.java:197)org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)atg.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)org位于org.eclipse.osgi.framework的org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)的.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107) org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchr中的.eventmgr.EventManager.dispatchEvent(EventManager.java:230) orous(ListenerQueue.java:148)org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) org.eclipse.osgi.invice.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)位于org.eclipse.osgi.framework的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214) .internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)位于org.wso2.carbon.core.init.CarbonServerManager的org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451) .initializeCarbon(CarbonServerManager.java:514)org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)at org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:94 )在sun.reflect.NativeMethodAccess orImpl.invoke0(本机方法)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method . java:498)org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146) org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)atg.eclipse.equinox .internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)位于org.eclipse.equinox.internal.ds.SCRManager.serviceChanged的org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343) (SCRManager.java:222)org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.jav) a:107)org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)at org org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)中的.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)at或者在org.eclipse.osgi.internal的org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)上的org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771) . servicegistry.ServiceRegistry.registerService(ServiceRegistry.java:214)位于org.eclipse.equinox.http.servlet.internal.Activator的org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433) . registerHttpService(Activator.java:81)位于org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet . java:40)org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)atg.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1269)org.apache .catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1182)at org.apache.catalina.core.StandardWrapper.load(Sta ndardWrapper.java:1072)org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5368)org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5660)atg.apache.catalina .util.LifecycleBase.start(LifecycleBase.java:145)位于org.apache.catalina.core.ContainerBase $ StartChild.call(ContainerBase.java:1571)org.apache.catalina.core.ContainerBase $ StartChild.call(ContainerBase) .java:1561)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor $ Worker . 在java.lang.Thread.run(Thread.java:748)上运行(ThreadPoolExecutor.java:617)TID:[ - 1234] [] [2017-11-03 08:14:35,124] WARN - 无法部署代理服务COMPLAIN_px - 在代理服务故障安全模式下继续 . {} org.apache.synapse.Axis2SynapseController

2 回答

  • 0

    从体系结构的角度来看,将代理和服务提供者(DSS)放在同一节点中并不是一个好习惯 .

    建议分为不同的节点,在一种情况下,WSO2 EI或ESB是服务的容器(数据服务);在另一个提供代理服务的节点中 .

    使用这种方法,您将无法获得您描述的事件 .

    我希望它对你有所帮助;

  • 0

    我刚试过这个 . 解压缩CAPP . 将artifacts.xml中的依赖项定义(工件)的顺序更改为您想要的顺序 . 再次归档并部署 . 检查神奇!

相关问题