| Author |
Message
|
| Sarvesh |
 Posted: Mon Mar 04, 2013 5:09 am Post subject: IBM MQ Integration with JBOSS EAP6.0.1 |
 |
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Hello,
We are trying to integrate JBOSS EAP6.0.1 with IBM MQ. We have an application working on Websphere 7 with IBM MQ for JMS.
We are in process of migration to JBOSS EAP6.0.1.
With regards to setup and information available on various JBOSS forums, we managed to perform a few setup for the Queue Connection factories and Queues.
With JBOSS EAP6.0.1, We have copied the "wmq.jmsra.rar" from the IBM MQ to JBOSS Standlalone deployment folder.
We modified the standalone-full.xml to include the resource-adapter pertaining to IBM MQ.
Snippet of configuration from standalone-full.xml:
<subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">
<resource-adapters>
<resource-adapter>
<archive>
wmq.jmsra.rar
</archive>
<transaction-support>NoTransaction</transaction-support>
<connection-definitions>
<connection-definition class-name="com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl" jndi-name="java:jboss/jms/myQCF" pool-name="jms/myQCF">
<config-property name="hostName">
XXXXXX (Server Name)
</config-property>
<config-property name="channel">
YYYYYY (Channel Name)
</config-property>
<config-property name="transportType">
CLIENT
</config-property>
<config-property name="queueManager">
ZZZZZ (Queue Manager Name)
</config-property>
</connection-definition>
</connection-definitions>
<admin-objects>
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/myOutPostQueue" pool-name="OUT_POST">
<config-property name="baseQueueName">
OUT_POST
</config-property>
</admin-object>
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/myOutAckQueue" pool-name="OUTPUT_REPLY_QUEUE">
<config-property name="baseQueueName">
OUTPUT_REPLY_QUEUE
</config-property>
</admin-object>
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/myOutRespQueue" pool-name="OUTPUT_PDF_RESP">
<config-property name="baseQueueName">
IVN_ADV_QUEUE
</config-property>
</admin-object>
</admin-objects>
</resource-adapter>
</resource-adapters>
</subsystem>
The connection-definition class-name are as per the ra.xml available under wmq.jmsra.rar\META-INF.
With the above setup We are able to see the JNDI created for the Queues and Queue Connection factory.
We have used Spring based JMS setup (JMSTemplate102) for getting the QCF and sending message.
However, at the time of calling send method on jmsTemplate102, we get below error:
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) Caused by: javax.resource.ResourceException: IJ000658: Unexpected throwable while trying to create a connection: null
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:378)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:302)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ConnectionFactoryImpl.createManagedJMSConnection(ConnectionFactoryImpl.java:189)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) ... 135 more
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) Caused by: com.ibm.mq.connector.DetailedResourceException: MQJCA1012: Failed to create a JMS connection factory., error code: MQJCA1012 A JCA ManagedConnectionFactory object was not able to create a WebSphere MQ classes for JMS ConnectionFactory object. Check the properties of the ConnectionFactory object.
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:124)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:100)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl.createConnection(ManagedQueueConnectionFactoryImpl.java:161)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:131)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedQueueConnectionImpl.<init>(ManagedQueueConnectionImpl.java:66)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl.createManagedConnection(ManagedQueueConnectionFactoryImpl.java:138)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:775)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:345)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) ... 141 more
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) Caused by: javax.jms.JMSException: com.ibm.msg.client.jms.internal.JmsFactoryFactoryImpl cannot be cast to com.ibm.msg.client.jms.JmsFactoryFactory
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.msg.client.jms.JmsFactoryFactory.getInstance(JmsFactoryFactory.java:199)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.ConnectionFactoryBuilder.constructJmsConnectionFactory(ConnectionFactoryBuilder.java:230)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.ConnectionFactoryBuilder.createConnectionFactory(ConnectionFactoryBuilder.java:124)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createConnectionFactory(ManagedConnectionFactoryImpl.java:431)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) at com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl.createConnection(ManagedQueueConnectionFactoryImpl.java:157)
17:15:22,852 ERROR [stderr] (http-localhost/127.0.0.1:8080-5) ... 146 more
Any help would be appreciated.
Also, if someone have configured IBM MQ with EAP6.0.1 (Without MDBs), pls guide us.
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 04, 2013 6:05 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So what is the linked Exception (extract it from the JMSException) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Sarvesh |
| Posted: Mon Mar 04, 2013 6:11 am Post subject: |
|
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Hello,
The exception generated is mentioned in the first post. Nothing more could be seen in the stacktrace.
It shows the root cause something as below:
Caused by: javax.jms.JMSException: com.ibm.msg.client.jms.internal.JmsFactoryFactoryImpl cannot be cast to com.ibm.msg.client.jms.JmsFactoryFactory
at com.ibm.msg.client.jms.JmsFactoryFactory.getInstance(JmsFactoryFactory.java:199) [com.ibm.msg.client.jms.jar:]
at com.ibm.mq.connector.ConnectionFactoryBuilder.constructJmsConnectionFactory(ConnectionFactoryBuilder.java:230) [com.ibm.mq.connector.jar:7.0.0.0-k700-L080820]
at com.ibm.mq.connector.ConnectionFactoryBuilder.createConnectionFactory(ConnectionFactoryBuilder.java:124) [com.ibm.mq.connector.jar:7.0.0.0-k700-L080820]
at com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl.createConnectionFactory(ManagedConnectionFactoryImpl.java:431) [com.ibm.mq.connector.jar:7.0.0.0-k700-L080820]
at com.ibm.mq.connector.outbound.ManagedQueueConnectionFactoryImpl.createConnection(ManagedQueueConnectionFactoryImpl.java:157) [com.ibm.mq.connector.jar:7.0.0.0-k700-L080820]
... 146 more
Above this are the wrapper implementations of the error occurred. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 04, 2013 6:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Sarvesh |
| Posted: Mon Mar 04, 2013 7:44 pm Post subject: |
|
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Thanks for the link. The link is for JBOSS AS5.1 or AS6.
We are using JBOSS EAP6.0.1 (which is JBOSS AS 7.1.3) and I think jbos-jmsra-ds.xml is not available in JBOSS AS7 onwards.
Can you pls help me with the configurations ? |
|
| Back to top |
|
|
| mvoegele |
| Posted: Mon Mar 04, 2013 10:39 pm Post subject: |
|
|
Newbie
Joined: 15 Feb 2013
Posts: 5
|
Hi
I setup mq with jboss-eap-6.0.1 and outbound as well as inbound communication is working.
Configuration:
<subsystem xmlns="urn:jboss:domain:resource-adapters:1.0">
<resource-adapters>
<resource-adapter>
<archive>wmq.jmsra.rar</archive>
<transaction-support>NoTransaction</transaction-support>
<connection-definitions>
<connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/jms/MqConnectionFactorySsl" pool-name="MqConnectionFactorySslPool">
<config-property name="connectionNameList">${jet.mq.connectionNameList}</config-property>
<config-property name="sslCipherSuite">${jet.mq.sslCipherSuite}</config-property>
<config-property name="channel">MC.MQJMSSAMP_SSL</config-property>
</connection-definition>
<connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/jms/MqConnectionFactory" pool-name="MqConnectionFactoryPool">
<config-property name="connectionNameList">${jet.mq.connectionNameList}</config-property>
<config-property name="channel">MC.MQJMSSAMP</config-property>
</connection-definition>
</connection-definitions>
<admin-objects>
<admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/jms/MqJmsSampleQueue" pool-name="MqJmsSampleQueuePool">
<config-property name="baseQueueName"> A.EPLATFORM.MQJMSSAMP
</config-property>
</admin-object>
</admin-objects>
</resource-adapter>
</resource-adapters>
</subsystem>
-> The first connection-definition uses an SSL enabled channel.
Outbound:
import javax.annotation.Resource;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.DeliveryMode;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.QueueSession;
import javax.jms.Session;
import javax.jms.TextMessage;
@Stateless
@Remote(JmsMqSender.class)
public class JmsMqSenderSslBean implements JmsMqSender {
@Resource(name = "java:jboss/jms/MqConnectionFactorySsl")
private ConnectionFactory connectionFactory;
@Resource(name = "java:jboss/jms/MqJmsSampleQueue")
private Queue destinationQueue;
@Override
public void sendMessage(String message) {
Connection connection = null;
try {
connection = connectionFactory.createConnection();
connection.start();
Session session = connection.createSession(false, QueueSession.AUTO_ACKNOWLEDGE);
MessageProducer messageProducer = session.createProducer(destinationQueue);
messageProducer.setDeliveryMode(DeliveryMode.PERSISTENT);
TextMessage textMessage = session.createTextMessage();
textMessage.setText(message);
messageProducer.send(textMessage);
} catch (JMSException e) {
throw new RuntimeException(e);
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
throw new RuntimeException(e);
}
}
}
}
}
Inbound:
import javax.ejb.MessageDriven;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@MessageDriven(activationConfig = {
// @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
// @ActivationConfigProperty(propertyName = "channel", propertyValue = "MC.MQJMSSAMP_SSL"),
// @ActivationConfigProperty(propertyName = "destination", propertyValue = "A.EPLATFORM.MQJMSSAMP")
})
// @ResourceAdapter(value = "wmq.jmsra.rar") not needed if mq is set as default jms provider in ejb3 subsystem
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public class MdbSampleSsl implements MessageListener {
private static final Logger LOGGER = LoggerFactory.getLogger(MdbSampleSsl.class);
@Override
public void onMessage(Message message) {
TextMessage textMessage = null;
try {
if (message instanceof TextMessage) {
textMessage = (TextMessage) message;
LOGGER.info("Received Message '{}'.", textMessage.getText());
} else {
LOGGER.warn("Message of wrong type: '{}'.", message.getClass().getName());
}
} catch (JMSException e) {
throw new RuntimeException(e);
}
}
}
You could define ActivationConfigProperties here, but we centralize it in ejb-jar.xml, because of stage dependent stuff.
Example:
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1">
<display-name>jet-demo-ejb</display-name>
<enterprise-beans>
<message-driven>
<ejb-name>MdbSampleSsl</ejb-name>
<ejb-class>com.axatech.jet.mdb.MdbSampleSsl</ejb-class>
<activation-config>
<!-- infrastructure specific properties -->
<activation-config-property>
<activation-config-property-name>connectionNameList</activation-config-property-name>
<activation-config-property-value>${jet.mq.connectionNameList}</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>sslCipherSuite</activation-config-property-name>
<activation-config-property-value>${jet.mq.sslCipherSuite}</activation-config-property-value>
</activation-config-property>
<!-- application specific properties -->
<activation-config-property>
<activation-config-property-name>channel</activation-config-property-name>
<activation-config-property-value>MC.MQJMSSAMP_SSL</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>A.EPLATFORM.MQJMSSAMP</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
</ejb-jar>
Mind that ${jet.mq.connectionNameList} and ${jet.mq.sslCipherSuite} reference system-properties.
Instead of defining connectionNameList, you can also define hostName and port, I did it before and it worked.
Version of resource-adapter I am using: 7.1.0.2-k710-002-120928.
Regards
Michael |
|
| Back to top |
|
|
| Sarvesh |
| Posted: Tue Mar 05, 2013 1:06 am Post subject: |
|
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Hello Michael,
Thanks for the detailed configuration. We also have a similar configuration as you have mentioned. We have non ssl channel.
However, with the code you have mentioned below for Outbound:
"connection = connectionFactory.createConnection(); " throws an error which is exactly the similar what we are getting.
We are using Resource-adapter : 7.0.0.0-k700-L080820
Can you pls provide me the list of jars you have kept under:
1. jboss-eap-6.0\standalone\deployments\wmq.jmsra.rar
We have created Module dependency under \jboss-eap-6.0\modules\com as \jboss-eap-6.0\modules\com\ibm\main.
Thanks.
Sarvesh |
|
| Back to top |
|
|
| mvoegele |
| Posted: Tue Mar 05, 2013 1:29 am Post subject: |
|
|
Newbie
Joined: 15 Feb 2013
Posts: 5
|
Hello Sarvesh
I am just using the original resource adapter from IBM. As mentioned before the resource-adapter has version 7.1.0.2-k710-002-120928. If you need a list of jars, you could have a look into the original resource adapter with the version you are using. It seems to me as if you have some version clash with the jars you are using (I guess that's why you asked for the list  ).
Regards
Michael |
|
| Back to top |
|
|
| Sarvesh |
| Posted: Tue Mar 05, 2013 1:43 am Post subject: |
|
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Hello Michael,
Thanks for prompt response.
Yes, I am also using the same. We are using the resource adapter (available under "WAS_HOME\lib\WMQ\ra" having the version "7.0.0.0-k700-L080820".
I feel then we are having a similar set of jars as you have.
We have extracted the "wmq.jmsra.rar" to the
"jboss-eap-6.0\standalone\deployments" folder.
Also, to provide runtime dependency (due to JBOSS AS 7 class loading structure), we have created a module under
"jboss-eap-6.0\modules\com".
jboss-eap-6.0 -> JBOSS_HOME
We have used a similar code as you have mentioned below for Outbound communication.
We are still getting the error as we have mentioned above.
Have you made any other configuration apart from mentioned here for JBOSS AS and MQ setup ?
Thanks.
Sarvesh |
|
| Back to top |
|
|
| mvoegele |
| Posted: Tue Mar 05, 2013 2:01 am Post subject: |
|
|
Newbie
Joined: 15 Feb 2013
Posts: 5
|
Hello Sarvesh
Well, another configuration I made is in ejb3 subsystem to tell jboss to use wmq.jmsra.rar as default jms provider, but this is only for mdb:
<mdb>
<resource-adapter-ref resource-adapter-name="wmq.jmsra.rar" />
<bean-instance-pool-ref pool-name="mdb-strict-max-pool" />
</mdb>
Why do you extract the rar file in the deployments folder? Maybe this causes the error. Just deploy the whole rar file, just put the whole rar in the deployment folder. I use domain mode normally to test it, so I deploy via web console or cli/dmr, as on linux, we will run jboss in domain mode, but it should be the same.
Regards
Michael |
|
| Back to top |
|
|
| Sarvesh |
| Posted: Thu Mar 07, 2013 11:31 pm Post subject: |
|
|
Newbie
Joined: 04 Mar 2013
Posts: 6
|
Hello Michael,
Good News!!! We got it working finally. Spring JMS on JBOSS EAP6.0.1 with Websphere MQ.
We were able to diagonise the issue and yes JBOSS AS7, classloading was the pin pointer.
We had IBM MQ jars in our classpath from Multiple locations. Indeed wmq.jmsra.rar is not be kept with exploded format. As suggested by you, We have kept the wmq.jmsra.rar as it is and removed some unnecessary locations from where the MQ jars were referred.
Thanks again to you and the forum for those responses.
Regards,
Sarvesh |
|
| Back to top |
|
|
| SMQS |
| Posted: Mon Jun 17, 2013 9:34 am Post subject: |
|
|
Newbie
Joined: 23 May 2013
Posts: 5
|
We are also running with same issue. We are trying to integrate MDB (on JBoss AS 5.1) with IBM MQ 7.1.0.0 via CCDT. We are using DS.XML to construct JNDI for JBoss. We are encountering errors which are appended below. May I seek some guidance please?
Datasource File (JMS-DS.XML)
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<!-- ==================================================================== -->
<!-- WSMQ connection factories -->
<!-- ==================================================================== -->
<!-- The WSMQ JMS provider loader -->
<mbean code="org.jboss.resource.deployment.AdminObject" name="jca.wmq:name=Q">
<attribute name="JNDIName">
queue/Q
</attribute>
<depends optional-attribute-name="RARName">
jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
</depends>
<attribute name="Type">javax.jms.Queue</attribute>
<attribute name="Properties">
baseQueueManagerName=*groupname (MQ Cluster Group Name)
baseQueueName=q (MQ Queue Name)
targetClient=JMS
</attribute>
</mbean>
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
<tx-connection-factory>
<jndi-name>WSMQJms</jndi-name>
<xa-transaction/>
<rar-name>wmq.jmsra.rar</rar-name>
<connection-definition>javax.jms.ConnectionFactory</connection-definition>
<config-property name="ccdtURL" type="java.lang.String">file:///C:/JNDI-Directory/AMQCLCHL.TAB</config-property>
<config-property name="queueManager" type="java.lang.String">*groupname</config-property>
<config-property name="transportType" type="java.lang.String">MQJMS_TP_CLIENT_MQ_TCPIP</config-property>
<use-java-context>false</use-java-context>
<max-pool-size>20</max-pool-size>
<!--<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Queue</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/WSMQJMSProvider</config-property>
<max-pool-size>20</max-pool-size> -->
<security-domain-and-application>JmsXARealm</security-domain-and-application>
<!-- <depends>jboss.messaging:service=ServerPeer</depends> -->
</tx-connection-factory>
</connection-factories>
Error Message:
ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-13) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@125d6d3(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@3b66f7 destination=queue/q destinationType=javax.jms.Queue 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)
javax.naming.NameNotFoundException: q not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
at org.jnp.server.NamingServer.lookup(NamingServer.java:443)
at org.jnp.server.NamingServer.lookup(NamingServer.java:399)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.util.naming.Util.lookup(Util.java:222)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2013-06-17 16:19:37,390 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-13) Attempting to reconnect |
|
| Back to top |
|
|
| @j0nnymac |
| Posted: Tue Apr 01, 2014 12:35 am Post subject: URL update |
|
|
Newbie
Joined: 31 Mar 2014
Posts: 6
|
|
| Back to top |
|
|
|
|
