|
Home > Archive > WebSphere Application Server > September 2005 > JNDI naming mystery
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
JNDI naming mystery
|
|
|
| Hi,
I am using WAS 5.1 as a JNDI name server for a client app. The client communicates with other system components through Websphere MQ, and it retrieves the administerd components through the WAS 5.1 JNDI name server.
To make that possible, I registered the connection factory and several queues in the Websphere MQ JMS provider panel, during which I also specified the JNDI name. However, when the client does a lookup of these components, they can not be found. The excep
tion that is thrown states that the first component of the jndi name is not found.
I also bound several strings in the environment > Naming > Name space bindings panel, and these bindings *can* be found. So I assume the name server is properly set up.
All bindings are in the server context. I used dumpnamespace, and found that strings can be found, but the MQ objects do not appear in the dump.
I did a similar set up in WAS 5.0, not so long ago, and this worked fine from the start.
I would appreciate any information and tips to help me get on with this.
Thanks in advance,
Huub
| |
|
| Hi,
I solved the problem: the configuration of my WAS installation was not correct. The WebSphere variable MQ_INSTALL_ROOT should point to the installation directory of MQ. When it does not (and in my installation it indeed did not), no MQ administered object
s can be created, and hence no name bindings can be added to the naming provider.
Unfortunately, WAS is not very specific about this, and attempts to create managed objects without a known MQ are not clearly indicated. This took me hours...
Huub
|
|
|
|
|