java.lang.RuntimeException: <message-driven> element parsing hasn't yet been implemented

[mphillip]

I have an ear file which I can sucessfully deploy on AS6, but on AS7 I get the following error trying to deploy it.

Is this something wrong in my ejb-jar.xml, or in the jboss.xml? (is that even needed any more for AS7?)

11:11:10,187 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "wmq.jmsra.ivt.ear"

11:11:10,343 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "WMQ_IVT.war"

11:11:10,343 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "WMQ_IVT_MDB.jar"

11:11:10,609 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."wmq.jmsra.ivt.ear"."WMQ_IVT_MDB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."wmq.jmsra.ivt.ear"."WMQ_IVT_MDB.jar".PARSE: Failed to process phase PARSE of subdeployment "WMQ_IVT_MDB.jar" of deployment "wmq.jmsra.ivt.ear"

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)

    at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]

    at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]

Caused by: java.lang.RuntimeException: <message-driven> element parsing hasn't yet been implemented

    at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:70)

    at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseEjbJarElements(EjbJarMetaDataParser.java:274)

    at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:142)

    at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:145)

    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)

    ... 5 more

11:11:10,906 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "wmq.jmsra.ivt.ear" was rolled back with failure message {"Failed services" => {"jboss.deployment.subunit.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT_MDB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT_MDB.jar\".PARSE: Failed to process phase PARSE of subdeployment \"WMQ_IVT_MDB.jar\" of deployment \"wmq.jmsra.ivt.ear\""}}

11:11:10,906 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment WMQ_IVT_MDB.jar in 9ms

11:11:10,921 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment WMQ_IVT.war in 22ms

11:11:10,937 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment wmq.jmsra.ivt.ear in 30ms

11:11:10,937 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.subunit.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT_MDB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT_MDB.jar\".PARSE: Failed to process phase PARSE of subdeployment \"WMQ_IVT_MDB.jar\" of deployment \"wmq.jmsra.ivt.ear\""}}}}

[jaikiran]

It's not implemented in AS 7.0.0.Final but is available in the latest AS7 nightly builds. See this thread http://community.jboss.org/thread/170228?tstart=60

[mphillip]

I've had a go with the nightly build as you suggested - it certainly gets further, but seems to be trying to use hornetq-ra, while I've (hopefully) configured it to use my own RA (see the jboss.xml attached to the original post).

Admittadly I've not yet managed to get my RA to deploy properly yet (see my other discussion on  "Non-explicit JNDI bindings not supported"), but would you expect it to be even trying the hornet one when I've configured it to use something else?

13:57:53,203 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "WMQ_IVT_MDB.jar"

13:57:53,218 WARN  [org.jboss.as.ejb3.deployment.processors.dd.SecurityRoleRefDDProcessor] (MSC service thread 1-3) secu

rity-role-ref for message driven beans isn't yet implemented

13:57:53,218 INFO  [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api dependency to wmq.jmsra.ivt.e

ar

13:57:53,218 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api dependency to WMQ_IVT_MDB.jar

13:57:53,218 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) added javax.persistence.api dependency to WMQ_IVT.war

13:57:53,234 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deploym

ent.subunit."wmq.jmsra.ivt.ear"."WMQ_IVT_MDB.jar".component.WMQ_IVT_MDB.CREATE: org.jboss.msc.service.StartException in

service jboss.deployment.subunit."wmq.jmsra.ivt.ear"."WMQ_IVT_MDB.jar".component.WMQ_IVT_MDB.CREATE: Failed to start ser

vice

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1786)

        at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]

        at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]

Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service hornetq-ra not found

        at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447)

        at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.getRequiredService(MessageDrive

nComponentCreateService.java:92)

        at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenCo

mponentCreateService.java:73)

        at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:78)

        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)

        ... 4 more

[jaikiran]

AS7 upstream currently doesn't pick up the resource adapter name from the jboss.xml. You can for now use the @org.jboss.ejb3.annotation.ResourceAdapter on the MDB to configure a custom one. Without that, it does default to hornetq.

[mphillip]

So in order to have an MDB using something other than Hornet, I need to add specific code into the MDB class itself?

Unfortunately I'm not able to do that.  The application cannot have JBoss specific code in it, or need to rely on JBoss specific code to be compiled.

Do you have any idea when the capability to do this will actually be in a released/available version of JBoss?

[jaikiran]

Martin Phillips wrote:

Do you have any idea when the capability to do this will actually be in a released/available version of JBoss?

I'm currently working on this to allow configuring this at subsystem level in the xml. You'll be able to test this in the next few days. I'll update this thread once it's available.

[jaikiran]

Martin, the latest nightly build should allow you to configure the default resource adapter name to be used by MDBs, at the subsystem level in the standalone.xml/domain.xml https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/standalone/configuration/standalone-preview.xml#L147