cgmedina [
https://community.jboss.org/people/cgmedina] created the discussion
"Re: Error deploying EJB JBoss AS6"
To view the discussion, visit:
https://community.jboss.org/message/754929#754929
--------------------------------------------------------------
I solved the DataSourceBinding error message, after reading this post:
https://community.jboss.org/thread/167109 https://community.jboss.org/thread/167109
I only had to change the name for mappedName in my @resource anotation as follows:
@Resource(mappedName="jdbc/mhzap101")
private javax.sql.DataSource ds;
Now I only get the following error messages:
Deployment
"jboss.j2ee:ear=mhzap101.ear,jar=mhzap101-ejb-core.jar,name=UtilityProcessRequestMessageBean,service=EJB3"
is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException:
Required config property RequiredConfigPropertyMetaData@12b76b9[name=destination
descriptions=[DescriptionMetaData@a26765[language=es]]] for messagingType
'javax.jms.MessageListener' not found in activation config
[ActivationConfigProperty(destinationType=javax.jms.Queue),
ActivationConfigProperty(acknowledgeMode=Auto-acknowledge)]
ra=jboss.jca:service=RARDeployment,name='jms-ra.rar'
Deployment
"jboss.j2ee:ear=mhzap101.ear,jar=mhzap101-ejb-core.jar,name=UtilityProcessReturnMessageBean,service=EJB3"
is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException:
Required config property RequiredConfigPropertyMetaData@12b76b9[name=destination
descriptions=[DescriptionMetaData@a26765[language=es]]] for messagingType
'javax.jms.MessageListener' not found in activation config
[ActivationConfigProperty(destinationType=javax.jms.Queue),
ActivationConfigProperty(acknowledgeMode=Auto-acknowledge)]
ra=jboss.jca:service=RARDeployment,name='jms-ra.rar'
Deployment
"jboss.j2ee:ear=mhzap101.ear,jar=mhzap101-ejb-core.jar,name=UtilityProcessReplyMessageBean,service=EJB3"
is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException:
Required config property RequiredConfigPropertyMetaData@12b76b9[name=destination
descriptions=[DescriptionMetaData@a26765[language=es]]] for messagingType
'javax.jms.MessageListener' not found in activation config
[ActivationConfigProperty(destinationType=javax.jms.Queue),
ActivationConfigProperty(acknowledgeMode=Auto-acknowledge),
ActivationConfigProperty(messageSelector=JMSCorrelationID IS NULL)]
ra=jboss.jca:service=RARDeployment,name='jms-ra.rar'
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1370)
[:2.2.0.GA]
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1316)
[:2.2.0.GA]
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968)
[:2.2.0.GA]
at
org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:82)
[:6.0.0.Final]
at
org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.checkComplete(ProfileControllerContext.java:138)
[:0.2.2]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:246)
[:0.2.2]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192)
[:0.2.2]
at
org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:57)
[:0.2.2]
at
org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74)
[:0.2.2]
at
org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:95)
[:0.2.2]
at
org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87)
[:0.2.2]
at
org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234)
[:0.2.2]
at
org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213)
[:0.2.2]
at
org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150)
[:0.2.2]
at
org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135)
[:0.2.2]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.2.2]
at
org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
[:1.6.0_25]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
[:1.6.0_25]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_25]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
[:1.6.0_25]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
[:1.6.0_25]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
[:1.6.0_25]
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]
I think it might be because of the jms configuration. I created the jms queues by using
the hornetq-jms.xml
Can anybody explain me, I'm kind of newbie
Thanks
--------------------------------------------------------------
Reply to this message by going to Community
[
https://community.jboss.org/message/754929#754929]
Start a new discussion in Beginner's Corner at Community
[
https://community.jboss.org/choose-container!input.jspa?contentType=1&...]