| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMSInput Node with ActiveMQ Bindings issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| cc |
 Posted: Thu Jan 28, 2010 8:31 pm Post subject: JMSInput Node with ActiveMQ Bindings issue |
 |
|
Novice
Joined: 28 May 2008
Posts: 19
|
I am trying to connect a JMSInput Node using ActiveMQ as the JMSProvider. I am getting an error with the configuration of the JNDI Bindings file.
MB7BROKER.default ) WMB JMSClient. ''Broker 'MB7BROKER'; Execution Group 'default'; Message Flow 'JMSInputPOC.JMSInputMsgFlow'; Node 'ComIbmJMSClientInputNode::JMSInput' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''org.apache.activemq.jndi.ActiveMQInitialContextFactory''. Location of the bindings = ''file://D:/Applications/ActiveMQ/''. ConnectionFactory Name = ''queueConnectionFactory''. JMS destination = ''CSC_IN''. The exception text is : ''Failed to create InitialContext using factory specified in hashtable {java.naming.provider.url=file://D:/Applications/ActiveMQ/, java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory, java.naming.referral=throw}''.
The node could not obtain a JNDI Administered Object because some of the values specified in the node attributes are incorrect
Check the JNDI Administered configuration for the JMS provider used by the node. Either modify the JNDI Administered objects and rebuild the bindings, or change the node attributes and re-deploy the message
The jndi.properties file looks like this:
java.naming.factory.initial = org.apache.activemq.jndi.ActiveMQInitialContextFactory
D:\Applications\ActiveMQ\jndi.properties file:
# use the following property to configure the default connector
java.naming.provider.url = tcp://192.168.0.130:61616
# use the following property to specify the JNDI name the connection factory
# should appear as.
connectionFactoryNames = queueConnectionFactory
# register some queues in JNDI using the form
# queue.[jndiName] = [physicalName]
CSC_IN = CSC_IN
1. Where should the name of the bindings files be specified and does it have to be jndi.properties?
2. Any ideas on what the problem is with my bindings file? Anyone have a sample?
Thanks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jan 29, 2010 4:04 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well the part where you replace the url with the Active MQ is a start.
I hope you also have all the relevant Active MQ on the classpath....
Now for the syntax of the jndi bindings, I'd think I'd stick as close as to the one specified in the MQ manual... but you could potentially write your own java API using the Sun file context and the Active MQ jars... to create the context... Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 29, 2010 5:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You probably need to issue mqsisetdbparms for both the InitialContextFactory and for the ConnectionFactory object.
You probably need to go back to the InfoCenter, and the devWorks article on configuring JMS nodes, and be *very* precise in what you do and do not set on the predefined ActiveMQ configurable service. |
|
| 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
|
|
|
|
