Mule vm: Connector scheitert in Mule 3.8 Laufzeit mit Domain-Projekt

Question

Ich bin neu in Mule Community 3.8 Edition. Wenn ich versuche, ein Domänenprojekt mit der vm: connector-Komponente zu erstellen, schlägt die Bereitstellung fehl und der folgende Fehler wird angezeigt. Looks Mule Community unterstützt keine vm: connector-Komponente. Kann jemand bitte beraten.

Code-Snippet

<?xml version="1.0" encoding="UTF-8"?> 
<mule-domain xmlns="http://www.mulesoft.org/schema/mule/domain" xmlns:core="http://www.mulesoft.org/schema/mule/core" 
     xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:context="http://www.springframework.org/schema/context" xmlns:spring="http://www.springframework.org/schema/beans" 
     xmlns:vm="http://www.mulesoft.org/schema/mule/vm" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:https="http://www.mulesoft.org/schema/mule/https" 
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xsi:schemaLocation=" 
http://www.mulesoft.org/schema/mule/domain http://www.mulesoft.org/schema/mule/domain/current/mule-domain.xsd 
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd 
http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-current.xsd 
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd 
http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/current/mule-vm.xsd 
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd 
http://www.mulesoft.org/schema/mule/https http://www.mulesoft.org/schema/mule/https/current/mule-https.xsd"> 

<vm:connector name="vm-shared" validateConnections="true" doc:name="VM Connector"> 
      <core:receiver-threading-profile poolExhaustedAction="WAIT" /> 
      <vm:queue-profile maxOutstandingMessages="50"> 
        <core:default-in-memory-queue-store /> 
      </vm:queue-profile> 
</vm:connector> 

Fehlerprotokolle

org.mule.module.launcher.DeploymentInitException: SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'vm:connector'. One of '{"http://www.springframework.org/schema/beans":beans, "http://www.springframework.org/schema/beans":bean, "http://www.springframework.org/schema/context":property-placeholder, "http://www.mulesoft.org/schema/mule/core":abstract-shared-connector, "http://www.mulesoft.org/schema/mule/core":abstract-shared-transaction-manager, "http://www.mulesoft.org/schema/mule/core":abstract-shared-extension}' is expected. 
    at org.mule.module.launcher.domain.DefaultMuleDomain.init(DefaultMuleDomain.java:192) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.artifact.ArtifactWrapper$2.execute(ArtifactWrapper.java:63) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:136) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.artifact.ArtifactWrapper.init(ArtifactWrapper.java:58) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:309) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:296) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:95) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DomainArchiveDeployer.deployExplodedArtifact(DomainArchiveDeployer.java:60) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DomainArchiveDeployer.deployExplodedArtifact(DomainArchiveDeployer.java:32) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DeploymentDirectoryWatcher.deployExplodedDomains(DeploymentDirectoryWatcher.java:472) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:143) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.MuleDeploymentService.start(MuleDeploymentService.java:134) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:172) ~[mule-module-launcher-3.8.3.jar:3.8.3] 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_111] 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_111] 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111] 
    at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111] 
    at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:52) ~[mule-module-reboot-3.8.3.jar:3.8.3] 
    at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) ~[wrapper-3.2.3.jar:3.2.3] 

Answer 1

VM als Shared Resource ist nur in Unternehmen: https://docs.mulesoft.com/mule-user-guide/v/3.8/shared-resources

Verwenden Sie den Standard-Connector von nur einfach mit:

vm: Outbound-Endpunkt Austausch-pattern = "Request-Response" path = "yourPathName" vm: Inbound-Endpunkt Austausch-pattern = "Request-Response" path = "yourPathName"

ziehe ich JMS-Warteschlangen über vms in vielen Fällen. Zumindest ist es möglich, JMS Connector in Domain-Projekten zu teilen.