|
以上代码在发布到Jboss4.2.3时报:
00:09:05,828 WARN [MessagingContainer] No message-driven-destination given; using; guessing type
00:09:05,828 WARN [MessagingContainer] Could not determine destination type, defaults to: javax.jms.Topic
00:09:05,843 WARN [ServiceController] Problem starting service jboss.j2ee:jar=ebj_three.jar,name=MyTopicMDBBean,service=EJB3
org.jboss.deployment.DeploymentException: Required config property RequiredConfigPropertyMetaData@1544e44[name=destination descriptions=[DescriptionMetaData@373a9c[language=zh]]] for messagingType 'javax.jms.MessageListener' not found in activation config [ActivationConfigProperty(destionationType=javax.jms.Topic), ActivationConfigProperty(destionation=topic/testTopic)] ra=jboss.jca:service=RARDeployment,name='jms-ra.rar'
at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:95)
at org.jboss.resource.deployment.RARDeployment.createActivationSpec(RARDeployment.java:254)
at org.jboss.resource.deployment.RARDeployment.internalInvoke(RARDeployment.java:218)
at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:156)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.ejb3.JmxClientKernelAbstraction.invoke(JmxClientKernelAbstraction.java:44)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:285)
at org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory.start(JBossMessageEndpointFactory.java:189)
at org.jboss.ejb3.mdb.MessagingContainer.startProxies(MessagingContainer.java:190)
at org.jboss.ejb3.mdb.MessagingContainer.start(MessagingContainer.java:156)
at org.jboss.ejb3.mdb.MDB.start(MDB.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
查了很久,也不知道为什么destionationType不能为javax.jms.Topic