| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMSAdmin Error.. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Manikrish |
 Posted: Thu Mar 27, 2003 2:19 am Post subject: JMSAdmin Error.. |
 |
|
Apprentice
Joined: 19 Jun 2002
Posts: 35
|
Hi.,
We are using WSAD 5.0 and Websphere MQ as a JMS Provider. While running JMSAdmin, I'm getting the following error..
"JNDI initialisation failed, please check your JNDI settings and service" ..
I'm posting the file contents
setup.p2p file:
def ctx(MyJNDIContextFactory)
chg ctx(MyJNDIContextFactory)
def qcf(MyJNDIContextFactory) qmgr(MDBQMgr)
def q(MyMDBQueue) qmgr(MDBQMgr) queue(MyQueue)
end
setenv.bat
@echo off
set WAS_HOME=C:\Program Files\IBM\WebSphere Studio\wstools\eclipse\plugins\com.ibm.etools.websphere.runtime.locator_5.0.1
set MQ_JAVA_INSTALL_PATH=C:\Program Files\IBM\WebSphere MQ\Java
@rem Java runtime
set JAVA_HOME=C:\Program Files\IBM\WebSphere Studio\eclipse\jre\bin
@rem MQ JMS
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\com.ibm.mq.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\com.ibm.mq.jms.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\jms.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\connector.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\fscontext.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\providerutil.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\jndi.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\ldap.jar
set MQ=%MQ%;%MQ_JAVA_INSTALL_PATH%\lib\jta.jar
@rem needed to use WebSphere name service for JNDI
set WebSphereCP=%WAS_HOME%\lib\websphere.jar
set CLASSPATH=%MQ%;%WebSphereCP%;%CLASSPATH%
set PATH=%JAVA_HOME%;%MQ_JAVA_INSTALL_PATH%\lib;%PATH%;
JMSAdmin.config file:
INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
PROVIDER_URL=iiop://localhost:900/
on running " JMSAdmin<setup.p2p -cfg JMSAdmin.config " in command prompt, I'm getting the JNDI Initialization failed error message..
Any help is appreciated.......
-Manikrish |
|
| Back to top |
|
 |
| meekings |
| Posted: Thu Mar 27, 2003 6:20 am Post subject: |
|
|
Voyager
Joined: 28 Jun 2001
Posts: 86
Location: UK, South West
|
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Mar 27, 2003 8:00 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The CNInitialContextFactory is the WAS 3.5 icf. The WsnInitialContextFactory is definitely correct for WAS 4. I haven't messed with WAS 5 and JMSAdmin to know if anything has changed in this area. I'd suggest running JMSAdmin with the -t and -v parameters to get a trace and verbose mode. It might shed more light. |
|
| Back to top |
|
|
| meekings |
| Posted: Thu Mar 27, 2003 9:08 am Post subject: |
|
|
Voyager
Joined: 28 Jun 2001
Posts: 86
Location: UK, South West
|
From the link above:
"Technically, the context factory com.ibm.ejs.ns.jndi.CNInitialContextFactory is deprecated in WebSphere Application Server 4.0; however, the new context factory com.ibm.websphere.naming.WsnInitialContextFactory doesn't work as it should with the JMSAdmin application. "
Don't know if this still applies in 5.0, but may be worth a try. |
|
| 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
|
|
|
|
