User development,
A new message was posted in the thread "Failed Attempt to integrate JBOSS AS with
Websphere MQ":
http://community.jboss.org/message/524658#524658
Author : Jeremy O'Donohue
Profile :
http://community.jboss.org/people/jeremyojeremy
Message:
--------------------------------------------------------------
Good Morning Ben,
Back at work today, had a look at your code snippets, but still run into issues we have
seen before:
Most of the properties you are using in your MDB are rejected on deployment by our JBOSS
server:
Heres the Error:
Failed to create Resource wmp-mdb-test-v1.jar - cause:
java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException:
Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR:
Deployment "jboss.j2ee:jar=wmp-mdb-test-v1.jar,name=WMQMDBTest,service=EJB3" is
in error due to the following reason(s): java.beans.IntrospectionException: No property
found for: transportType on JavaBean:
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@9d87a0(ra=null
destination=TEST.QUEUE destinationType=null tx=true durable=false reconnect=10
provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15
keepAlive=60000 useDLQ=true
DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler
DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) ->
org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment
"jboss.j2ee:jar=wmp-mdb-test-v1.jar,name=WMQMDBTest,service=EJB3" is in error
due to the following reason(s): java.beans.IntrospectionException: No property found for:
transportType on JavaBean:
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@9d87a0(ra=null
destination=TEST.QUEUE destinationType=null tx=true durable=false reconnect=10
provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15
keepAlive=60000 useDLQ=true
DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler
DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
I've had a look into this in the past and is seems to happen because there are no
getters / setters for some of the properties defined in the MDB ie. hostName in the
org.jboss.resource.adapter.jms.inflow.JmsActivationSpec class
(
http://docs.huihoo.com/javadoc/jboss/4.0.2/org/jboss/resource/adapter/jms...).
Did you have to extend this class to have a successful deployment?
FYI setting : @ActivationConfigProperty(propertyName = "useJNDI", propertyValue
= "false"), allows you to reference the QUEUE by it's WSMQ Name as it tells
the MDB to bypass JNDI lookup and go straight to WS.
My New Test MDB code:
package au.com.loftusit.mqtest;
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import org.jboss.annotation.ejb.ResourceAdapter;
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="messagingType",propertyValue="javax.jms.MessageListener"),
@ActivationConfigProperty(propertyName = "destinationType",propertyValue
= "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue =
"TEST.QUEUE"),
@ActivationConfigProperty(propertyName = "useJNDI", propertyValue =
"false"),
@ActivationConfigProperty(propertyName = "channel", propertyValue =
"SYSTEM.DEF.SVRCONN"),
@ActivationConfigProperty(propertyName = "hostName", propertyValue =
"172.19.1.14"),
@ActivationConfigProperty(propertyName = "queueManager", propertyValue =
"ExampleQM"),
@ActivationConfigProperty(propertyName = "port", propertyValue =
"1414"),
@ActivationConfigProperty(propertyName = "transportType", propertyValue
= "CLIENT")
})
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
@ResourceAdapter(value = "wmq.jmsra.rar")
class WMQMDBTest implements MessageListener {
public void onMessage(Message message) {
System.out.println(message.toString());
}
}
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/524658#524658