|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Define TopicConnectionFactory resource in WebSphere question |
« View previous topic :: View next topic » |
Author |
Message
|
antelope |
Posted: Tue Oct 18, 2005 6:40 pm Post subject: Define TopicConnectionFactory resource in WebSphere question |
|
|
Novice
Joined: 26 Sep 2005 Posts: 15
|
I want to define TopicConnectionFactory resource that connect to MQ V6 in WebSphere Application Server V6, I have defined queue manage QM_APPLE in my MQ V6.
The following is the properties of resource in WS:
name:testTopicConnectionFactory
JNDI name:jms/testTopicConnectionFactory
HOST:192.168.0.56
PORT:1414
Transport Type:client
Queue Manage:QM_APPLE
Broker Queue Manage:QM_APPLE
Broker Version:base
those broker queues used default, like:
Broker control queue:SYSTEM.BROKER.CONTROL.QUEUE
etc...
save and restart WS, I want use JNDI to lookup the resource "jms/testTopicConnectionFactory", but failued: Context: xxx01Cell/nodes/xxx01/servers/server1, name: jms/testTopicConnectionFactory: First component in name testTopicConnectionFactory not found.
How to use Pub/Sub between WS and MQ? |
|
Back to top |
|
 |
antelope |
Posted: Thu Oct 20, 2005 7:29 am Post subject: |
|
|
Novice
Joined: 26 Sep 2005 Posts: 15
|
Could somebody help me?  |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Oct 20, 2005 7:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Did you confirm that the name was bound in WAS during startup?
Can you explain what you have done to troubleshoot this in the last two days? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
antelope |
Posted: Thu Oct 20, 2005 6:36 pm Post subject: |
|
|
Novice
Joined: 26 Sep 2005 Posts: 15
|
Quote: |
Did you confirm that the name was bound in WAS during startup? |
No, it cause error.
[10/21/05 9:59:12:156 CST] 0000000a ResourceMgrIm E WSVR0017E: Error encountered binding the J2EE resource, testTopicConnectionFactory, as jms/testTopicConnectionFactory from file:/D:/Program%20Files/IBM/WebSphere/AppServers/profiles/default/config/cells/billybaoNode01Cell/nodes/billybaoNode01/resources.xml
com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: Failed to create connection factory: Error raised constructing AdminObject, error code: Transport Type : Transport Type
at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>(JMSConnectionFactoryReferenceable.java:146)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:615)
...
When I change transport type to Binding and set the Broker Vesion to Advanced, other properties set default, JNDI can look up but can't createConnection.
Quote: |
Can you explain what you have done to troubleshoot this in the last two days? |
I have test for QueueConnectionFactory and Queue for JNDI in WAS, it success. I can look up them and send&receive message by JAVA application.
But when I test TopicConnectionFactory&Topic, it failued. I want to use WBI, but it should install more other application like DB2, so I give up.
I want to know why the broker for WMQ pub/sub can't be look up like Queue. I think Topic maybe same as Queue by using JNDI, right?
ps. I'm a newbie for WMQ, this term I read more document like IBM redbooks, but it's very complex, I don't have a clue. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|