Not able to use QueueConnectionFactory JNDI name in ejb-jar.xml to avoid redundant code.
ponnuchamy.p Aug 19, 2014 3:36 PMHello, I'm working on application migrating from Websphere to JBoss. I picked jboss-eap-6.2.0 for deployment and Websphere RA(WebMq-7.5.0) to connect WMQ, it is connecting to both un-secured and secured Websphere Queue if I define all the information. like QMGR, QName, QHostname,QPort etc in ejb-jar.xml(no jboss.xml/jboss-ejb3.xml file. the same information had already defined in standalone-full.xml with JNDI name so I'm trying use QCF JNDI name with "connectionFactoryJndiName" activation-config-property-name in ejb-jar.xml file, but jboss is not recognizing qcf jndi name. In the server startup log, getting below warning message. As it's not recognizing qcf JNDI name, it tries to connect localhost(1414) by default. I really don't wanna define the queue details in both ejb-jar.xml and standalone-full.xml. has anyone encountered the same issue? and found the solution? your help is much appreciated. Thanks for you time in Advance.
18:04:07,630 WARN [org.jboss.as.ejb3] ActivationConfigProperty connectionFactoryJndiName/messagingType will be ignored since it is not allowed by resource adapter: wmq.jmsra.rar
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:209)
... 22 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2538;AMQ9204: Connection to host 'localhost(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2538;AMQ9213: A communications error for occurred. [1=java.net.ConnectException[Connection refused: connect],3=localhost]],3=localhost(1414),5=RemoteTCPConnection.connnectUsingLocalAddress]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2053)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)
at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:345)
... 21 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2538;AMQ9213: A communications error for occurred. [1=java.net.ConnectException[Connection refused: connect],3=localhost]
ejb-jar.xml
----------------
....
<message-driven>
<display-name>ProcessService</display-name>
<ejb-name>ProcessService</ejb-name>
<ejb-class>com.chase.chf.emi.common.framework.mdb.ProcessServiceBean</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>useJNDI</activation-config-property-name>
<activation-config-property-value>true</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>destination</activation-config-property-name>
<activation-config-property-value>java:jboss/jms/QueueJNDI</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>acknowledgeMode</activation-config-property-name>
<activation-config-property-value>Auto-acknowledge</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>connectionFactoryJndiName</activation-config-property-name>
<activation-config-property-value>java:jboss/jms/QCFJNDI</activation-config-property-value>
</activation-config-property>
<message-driven>
.....