ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JMSOutput Node - JNDI issue on connecting with ActiveMQ

Post new topic  Reply to topic
 JMSOutput Node - JNDI issue on connecting with ActiveMQ « View previous topic :: View next topic » 
Author Message
mqued
PostPosted: Mon Dec 11, 2017 6:58 am    Post subject: JMSOutput Node - JNDI issue on connecting with ActiveMQ Reply with quote

Novice

Joined: 27 Feb 2013
Posts: 14

Hi All,

I am getting a JNDI error from JMSOutput node which is connecting to ActiveMQ. Below are the configurations

A configurable service is defined as follows
Code:
mqsichangeproperties XXX.BRKR.XXXX -c JMSProviders -o ActiveMQ -n connectionFactoryName,initialContextFactory, jndiBindingsLocation,jndiEnvironmentParms -v ConnectionFactory,org.apache.activemq.jndi.ActiveMQInitialContextFactory,ssl://<IP>:<Port>,queue.jmsABCREGQ=aq;queue.jmsOUTQ=hq;


A keystore and truststore are configured with the certifcates for ssl connection.


The user trace of the error is as below
Code:

   About to pass a message to the evaluate() method of  the specified node.
                                       No user action required.
2017-12-11 18:03:24.144432    16252   UserTrace   BIP12034E: Failed to find JNDI definition for connection factory ''ConnectionFactory''.
                                       The node cannot obtain a JNDI Administered Object, because some of the values specified are incorrect. The JMS Exception text is: ''ConnectionFactory''.
                                       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 Configurable Service attributes associated with this JMS Provider and restart the execution group 
                                        or 
                                        Change the node attributes and redeploy the message flow.
2017-12-11 18:03:24.688486    16252   UserTrace   BIP2231E: Error detected whilst processing a message in node 'mw.RegRequest.JMS Output1'.
                                       The message broker detected an error whilst processing a message in node 'mw.RegRequest.JMS Output1'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
                                       See the following messages for details of the error.
2017-12-11 18:03:24.688508    16252   RecoverableException  BIP4640E: WMB JMSClient. ''Broker 'XXX.BRK.XXX'; Execution Group 'XXXX'; Message Flow 'mw.RegRequest'; Node 'JMS Output1::ComIbmJMSClientOutputNode' '' There is a configuration problem with the JNDI Administered objects where:  Initial Context Factory  = ''org.apache.activemq.jndi.ActiveMQInitialContextFactory''.  Location of the bindings = ''ssl://XXXXX:XXXX''.  ConnectionFactory Name   = ''ConnectionFactory''.  JMS destination  = ''jmsABCREGQ''.  The exception text is : ''ConnectionFactory''.
                                       The node cannot obtain a JNDI Administered Object, because some of the values specified 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 Configurable Service attributes associated with this JMS Provider and restart the execution group 
                                        or 
                                        Change the node attributes and redeploy the message flow.


The same configuration is working perfectly in pre production environments without any issues. We are using WMB 8.0.0.1 on windows. Please advice on anything that i might be missing.
Back to top
View user's profile Send private message
mqued
PostPosted: Mon Dec 11, 2017 8:35 pm    Post subject: Reply with quote

Novice

Joined: 27 Feb 2013
Posts: 14

Sorted it out

Changed to connectionFactory instead of ConnectionFactory and it worked.

Code:

mqsichangeproperties XXX.BRKR.XXXX -c JMSProviders -o ActiveMQ -n connectionFactoryName,initialContextFactory, jndiBindingsLocation,jndiEnvironmentParms -v connectionFactory,org.apache.activemq.jndi.ActiveMQInitialContextFactory,ssl://<IP>:<Port>,queue.jmsABCREGQ=aq;queue.jmsOUTQ=hq;
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JMSOutput Node - JNDI issue on connecting with ActiveMQ
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.