| Author |
Message
|
| mqsiuser |
 Posted: Wed Aug 21, 2013 4:54 am Post subject: There is a configuration problem with the JNDI Administered |
 |
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Hello MQ Experts,
we have a problem setting up a JMS-Connection from MQ to WAS.
Anyone with experience on that is hightly welcome to leave a comment/hint on what we should do:
| Code: |
( myBroker.myExecutionGroup ) WMB JMSClient. ''Broker 'myBroker'; Execution Group 'myExecutionGroup'; Message Flow 'myMessageFlow'; Node 'JMS Output' '' There is a configuration problem with the JNDI Administered objects where: Initial Context Factory = ''JMS Output''. Location of the bindings = ''com.ibm.websphere.naming.WsnInitialContextFactory''. ConnectionFactory Name = ''iiop://myWASServer:9810''. JMS destination = ''QCF''. The exception text is : ''jms/eventqueue''.
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. |
We use Broker 7, MQ 7 and WAS 8.5 (I may provide more detailed version information if required) |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Wed Aug 21, 2013 6:09 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Your error is coming from WMB and not WAS.
Maybe the moderator can move this to the WMB section.
You do not need to repost this and somebody will come along in a bit with a better answer than what I'm giving.
Basically, your service is not correctly setup in WMB or does not contain what your flow is looking for... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Aug 21, 2013 6:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| That looks like the wrong value for the Initial Context factory. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 21, 2013 1:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
From the top output;
Context.INITIAL_CONTEXT_FACTORY content is in location of the bindings
Context.PROVIDER_URL content is in ConnectionFactoryName
ConnectionFactoryName is in InitialContextFactory....
So it looks like you have a completely messed up setup.
A word to the wise: better use the file based JNDI...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Mon Aug 26, 2013 2:13 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
The Configuration of the JMS-Output Node is:
Basic:
Destination queue: "jms/eventqueue"
JMS Connection:
JMS provider name: "Client for WebSphere Application Server"
Initial context factory: "com.ibm.websphere.naming.WsnInitialContextFactory"
Location JNDI bindings: "iiop://servername:9810
Connection factory name: "QCF"
Probably I should delete and redeploy the flow. |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Thu Aug 29, 2013 11:12 pm Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
We deleted and deployed the flow (again) and restarted the Application Server Cluster.
Works now  . Thank you for your help! |
|
| Back to top |
|
|
|
|
