[mnovak]

Thanks Wayne for checking it. Currently it behaves as designed but to be honest it's flaw in design. I don't there is something what can be done from Artemis pov but WF server should be able to count with it. I'll do some tests with:

deploy ~/tmp/luckywinner.ear --unmanaged --headers={rollback-on-runtime-failure=false}

as if deployments to servers are deployed this way then it should be able to recover once live on instance #1 activates and deploys all destinations/connection factories. I'll try it once I get to it.

Also I've created jira - [WFLY-8828] Creating cluster-connection in CLI must require discovery-group or static-connector - all credit for this goes to you. Thanks!

[mnovak]

Yes, if MDB is deployed to instance #1 using CLI like:

deploy ~/tmp/luckywinner.ear --unmanaged --headers={rollback-on-runtime-failure=false}

then I can see that MDB on instance #1 starts to receive messages once live on instance #1 activates. You'll still see error like:

10:54:11,888 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "mdb2.jar")]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.ra.activemq-ra",
        "jboss.naming.context.java.jboss.DefaultJMSConnectionFactory",
        "jboss.naming.context.java.JmsXA"
    ],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => [
        "jboss.deployment.unit.\"mdb2.jar\".component.mdb.CREATE is missing [jboss.ra.activemq-ra]",
        "jboss.naming.context.java.comp.mdb2.mdb2.mdb.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]",
        "jboss.naming.context.java.comp.mdb2.mdb2.mdb.env.\"org.jboss.qa.hornetq.apps.mdb.LocalMdbFromQueue\".cf is missing [jboss.naming.context.java.JmsXA]"
    ]
}
10:54:12,026 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.naming.context.java.JmsXA (missing) dependents: [service jboss.naming.context.java.comp.mdb2.mdb2.mdb.env."org.jboss.qa.hornetq.apps.mdb.LocalMdbFromQueue".cf] 
      service jboss.naming.context.java.jboss.DefaultJMSConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.mdb2.mdb2.mdb.DefaultJMSConnectionFactory] 
      service jboss.ra.activemq-ra (missing) dependents: [service jboss.deployment.unit."mdb2.jar".component.mdb.CREATE] 

but MDB starts to consume messages once live on instance #1 activates.

[wwang2016]

Hi Miroslav,

The deploy command is not part of wildfly. Did you tested in Red Hat JEAP 7.0?

Is there a way that I can try it in wildfly 10?

Thanks,

Wayne

[mnovak]

Yes, I tried with EAP 7.1.0 but the command is present in WF10/10.1/11 as well. I should probably mention that it's CLI command :-)

This is what I did to deploy it (there WF server already running on 127.0.0.1):

$~/tmp/wildfly-10.0.0.Final/bin $ sh jboss-cli.sh 
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect 127.0.0.1:9990
[standalone@127.0.0.1:9990 /] deploy /tmp/mdb.jar --unmanaged --headers={rollback-on-runtime-failure=false}