5.1.0: Error for com.ibm.mq.connector.inbound.ActivationSpec
sebbay Jul 1, 2009 5:11 AMHello,
When deploying an application using Websphere MQ, I get the following exception:
Caused by: org.jboss.deployers.spi.DeploymentException: Error for ActivationSpec class com.ibm.mq.connector.inbound.ActivationSpecImpl as JavaBean at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:135) at org.jboss.resource.deployers.RARDeployment.createActivationSpec(RARDeployment.java:313) at org.jboss.resource.deployers.RARDeployment.internalInvoke(RARDeployment.java:276) 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:668) at org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory.createActivationSpec(JBossMessageEndpointFactory.java:449) ... 137 more Caused by: java.beans.IntrospectionException: No property found for: acknowledgeMode on JavaBean: javax.jms.Queue:SYSTEM.DEFAULT.LOCAL.QUEUE@@localhost at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:354) at org.jboss.util.propertyeditor.PropertyEditors.mapJavaBeanProperties(PropertyEditors.java:285) at org.jboss.resource.deployment.ActivationSpecFactory.createActivationSpec(ActivationSpecFactory.java:129)
I recently get out, that WMQ Resource Adapter doesn't support the property acknowledgeMode. How can I configure JBoss 5.1.0 that this exception is not thrown?
Abridgment of the ejb-jar.xml:
<message-driven> <ejb-name>ServiceImpl</ejb-name> <ejb-class>test.ServiceImpl</ejb-class> <messaging-type>javax.jms.MessageListener</messaging-type> <transaction-type>Bean</transaction-type> <activation-config> <activation-config-property> <activation-config-property-name>destination</activation-config-property-name> <activation-config-property-value>TEST_QUEUE</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>destinationType</activation-config-property-name> <activation-config-property-value>javax.jms.Queue</activation-config-property-value> </activation-config-property> <!-- activation-config-property> <activation-config-property-name>messagingType</activation-config-property-name> <activation-config-property-value>javax.jms.MessageListener</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>useJNDI</activation-config-property-name> <activation-config-property-value>false</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>hostName</activation-config-property-name> <activation-config-property-value>localhost</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>queueManager</activation-config-property-name> <activation-config-property-value>QM_TEST</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>port</activation-config-property-name> <activation-config-property-value>1414</activation-config-property-value> </activation-config-property> <activation-config-property> <activation-config-property-name>transportType</activation-config-property-name> <activation-config-property-value>CLIENT</activation-config-property-value> </activation-config-property--> </activation-config> <ejb-local-ref> <ejb-ref-name<Service</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local>test.Service</local> </ejb-local-ref> </message-driven>
Abridgment of the jboss.xml:
<?xml version="1.0" encoding="UTF-8"?> <jboss> <enterprise-beans> <message-driven> <resource-adapter-name>wmq.jmsra.rar</resource-adapter-name> <ejb-name>OutboundMessageListenerServiceImpl</ejb-name> <configuration-name>Standard Message Driven Bean</configuration-name> </message-driven> </enterprise-beans> </jboss>
Best regards,
Sebastian