[jboss-jira] [JBoss JIRA] (AS7-3380) Changing MDB configuration in jboss-ejb3.xml causes ClassCastException
Ondřej Chaloupka created AS7-3380:
-------------------------------------
Summary: Changing MDB configuration in jboss-ejb3.xml causes
ClassCastException
Key: AS7-3380
URL: https://issues.jboss.org/browse/AS7-3380
Project: Application Server 7
Issue Type: Bug
Reporter: Ondřej Chaloupka
Assignee: jaikiran pai
I did change of destination of mdb queue in jboss-ejb3.xml file in following way:
https://github.com/ochaloup/jboss-as/commit/5a0501387821994b6a94ddb508f6f...
But during deployment I get exception:
java.lang.ClassCastException: org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData
cannot be cast to org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData
{code}
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start
service jboss.deployment.unit."mdb.jar".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."mdb.jar".PARSE: Failed to process phase PARSE of
deployment "mdb.jar"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119)
[jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_23]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
Caused by: java.lang.ClassCastException:
org.jboss.metadata.ejb.spec.MessageDrivenBean31MetaData cannot be cast to
org.jboss.metadata.ejb.jboss.ejb3.JBossGenericBeanMetaData
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.merge(MessageDrivenBeanMetaData.java:353)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:85)
at
org.jboss.metadata.ejb.spec.MessageDrivenBeanMetaData.createMerged(MessageDrivenBeanMetaData.java:36)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.merge(EnterpriseBeansMetaData.java:73)
at
org.jboss.metadata.ejb.spec.EnterpriseBeansMetaData.createMerged(EnterpriseBeansMetaData.java:52)
at org.jboss.metadata.ejb.spec.EjbJarMetaData.merge(EjbJarMetaData.java:175)
at
org.jboss.metadata.ejb.spec.EjbJarMetaData.createMerged(EjbJarMetaData.java:668)
at
org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:125)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
... 5 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira