| Author |
Message
|
| pmehta |
 Posted: Wed Jan 18, 2006 3:34 am Post subject: jmsadmin utility |
 |
|
Novice
Joined: 29 Jul 2003
Posts: 13
|
When I try to run jmsadmin utility an error comes saying,
"JNDI initialisation failed, please check your JNDI settings and service"
I have set the classpath for com.ibm.mq.jar and com.ibm.mqjms.jar
Please help in resolving the error. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 18, 2006 4:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why are you even bothering with JMSAdmin?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Jan 18, 2006 9:03 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| jefflowrey wrote: |
| Why are you even bothering with JMSAdmin? |
Not sure about him, but I use it all the time. It works great with stand-alone programs and a file system context. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 18, 2006 9:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bower5932 wrote: |
| Not sure about him, but I use it all the time. It works great with stand-alone programs and a file system context. |
That, in fact, is the only thing it is good for these days.
And I have a suspicion that pmehta is not trying to use it for that.
Also, I'm still not sold on the idea of using JMS or any other J2EE spec outside a J2EE container.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fengxiwei |
| Posted: Sat Feb 18, 2006 11:17 pm Post subject: problem on jmsadmin |
|
|
Newbie
Joined: 18 Feb 2006
Posts: 1
|
hi,
I using the jmsadmin and WebSphere MQ Initial Context useing mqcontent.jar(me01) program stand-alone programs.
the result is :
JNDI initialization failed, please check your JNDI settings and service.
The JMSAdmin.config file:
INITIAL_CONTEXT_FACTORY=com.ibm.mq.jms.context.WMQInitialContextFactory
PROVIDER_URL=localhost:1414/SYSTEM.DEF.SVRCONN
Please help in resolving the error.
thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 19, 2006 4:05 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Make sure all the jars in <MQ Install>/java/lib are on the classpath.
Can you be more specific about the error? (stack trace etc...)
Thanks 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kibbeyb |
| Posted: Thu Feb 23, 2006 10:20 am Post subject: Same problem here |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 1
|
I'm trying to get JMSAdmin running & have the same error: JNDI initialisation failed.
Initialising JNDI Context...
INITIAL_CONTEXT_FACTORY: com.ibm.mq.jms.context.WMQInitialContextFactory
PROVIDER_URL: localhost:1414/SYSTEM.DEF.SVRCONN
JNDI initialisation failed, please check your JNDI settings and service
I do have mq in my classpath and in my JMSAdmin.bat file. I'm following instructions here:
http://www-128.ibm.com/developerworks/websphere/techjournal/0502_woolf/0502_woolf.html
Any other suggestions? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 23, 2006 3:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| INITIAL_CONTEXT_FACTORY: com.ibm.mq.jms.context.WMQInitialContextFactory |
Yeah... only really works if in a WAS environment and then it should be below WAS 5.x and then your ProviderURL is all wrong...
Really start with the file context . Much easier.
The Was Context needs half of the WAS jars on the classpath -- Quite heavyweight...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rossired |
| Posted: Mon Feb 27, 2006 7:33 am Post subject: |
|
|
Novice
Joined: 22 Feb 2006
Posts: 22
|
| fjb_saper wrote: |
| Quote: |
| INITIAL_CONTEXT_FACTORY: com.ibm.mq.jms.context.WMQInitialContextFactory |
Yeah... only really works if in a WAS environment and then it should be below WAS 5.x and then your ProviderURL is all wrong...
Really start with the file context . Much easier.
The Was Context needs half of the WAS jars on the classpath -- Quite heavyweight...
Enjoy |
Ok, I can't get this to work either. I have no JMS experience etc. I've been following this thread and have added all the jars to the classpath, including the ones from the ME01 pac.
Before, it couldnt find the class for the InitialContext, but now, when I start the utility, it actually says its starting, but nothing actually happens.
The reason I am even trying to run this utility ? I am trying a simple msgflow with JMS output nodes, and have to fill in the initialcontextfactory, location of jndi bindings, and connection factory name. So searching through the documentation has led me to trying to use this tool to get these values..
Thanks
Vale |
|
| Back to top |
|
|
| rossired |
| Posted: Mon Feb 27, 2006 7:53 am Post subject: |
|
|
Novice
Joined: 22 Feb 2006
Posts: 22
|
| rossired wrote: |
| fjb_saper wrote: |
| Quote: |
| INITIAL_CONTEXT_FACTORY: com.ibm.mq.jms.context.WMQInitialContextFactory |
Yeah... only really works if in a WAS environment and then it should be below WAS 5.x and then your ProviderURL is all wrong...
Really start with the file context . Much easier.
The Was Context needs half of the WAS jars on the classpath -- Quite heavyweight...
Enjoy |
Ok, I can't get this to work either. I have no JMS experience etc. I've been following this thread and have added all the jars to the classpath, including the ones from the ME01 pac.
Before, it couldnt find the class for the InitialContext, but now, when I start the utility, it actually says its starting, but nothing actually happens.
The reason I am even trying to run this utility ? I am trying a simple msgflow with JMS output nodes, and have to fill in the initialcontextfactory, location of jndi bindings, and connection factory name. So searching through the documentation has led me to trying to use this tool to get these values..
Thanks
Vale |
Nevermind,, I got it to come up.. I was using a file URL, with the wrong contextfactory etc.... problem one solved.
Thanks
Vale |
|
| Back to top |
|
|
| vgawli |
| Posted: Mon Jun 18, 2007 10:13 pm Post subject: JMSADMIN: JNDI initialisation failed |
|
|
Newbie
Joined: 18 Jun 2007
Posts: 6
|
Hi,
I'm quite new to JMS and MQ, I just installed WebSphereMQ5.3.0.2 on a windows XP machine.
While installing MQ, I installed JMS messaging service option and want to create topics and stuff using JMS.
I found out that to do that, I need to use JMSADMIN tool for this, but when I try to run that tool, I'm getting this message:
JNDI initialisation failed, please check your JNDI settings and service
The INITIAL_CONTEXT and PROVIDER_URL in the JMSADMIN.config file has the following values:
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
and
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
#PROVIDER_URL=file:/C:/JNDI-Directory
#PROVIDER_URL=iiop://localhost/
which one of them should I enable to get the JMSADMIN tool working?
Thanks
Vinay Gawli |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 19, 2007 2:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Please don't double post. See my answer in the other thread. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Jun 19, 2007 11:54 am Post subject: JMS and Stanalone apps --- Why Not!! |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
To address the inference as to why one woud use JMS outside an App Server enviroment one may want to read the article on IBM Developerworks as to Why and How to use JMS with Standalone apps.
Here is a quick except: Why a standalone JMS application?
Why, one might wonder, would you want to write a JMS messaging program to operate outside of a J2EE environment? True, J2EE has received much of the messaging spotlight, but messaging was around before J2EE and we still need to do many of the same tasks we used messaging for then -- tasks for which the J2EE environment may be overqualified, or just simply inappropriate. These include batch jobs, bridges, conversions, utilities, administration, instrumentation, monitoring, and notification of real-world events, among other things. Coding outside of the J2EE environment, however, does not preclude the use of JMS. Given Java as the programming language of choice, and JMS the standard messaging API for Java, the question really is: Why wouldn't you want to use JMS to meet these messaging requirements?
-------------- and here is the url for the whole article:
http://www.ibm.com/developerworks/websphere/techjournal/0610_woolf/0610_woolf.html
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 19, 2007 12:00 pm Post subject: Re: JMS and Stanalone apps --- Why Not!! |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| George Carey wrote: |
| Given Java as the programming language of choice, and JMS the standard messaging API for Java, |
JMS is not the standard messaging API for Java.
It's the standard messaging API for Java Enterprise Edition. There is no standard messaging API for Java Standard Edition.
Which means that it's a standard that is designed to be executed within and supported by an Application Server environment....
The same argument you have just quoted here could be used to show that one should always use EJBs to access databases.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Jun 19, 2007 2:32 pm Post subject: |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
| Quote: |
| The same argument you have just quoted here could be used to show that one should always use EJBs to access databases. |
1.) I have a philosophy minor and major in Mathematics in college, so my skils in logic are good but still I miss the thread in your quoted analogy, sorry.
2.) As you mention it is a quote (verbatim at that) from the article, so it is not my 'argument', perhaps you should contest it with the authors rather than me. I am offering it as a worth while observation with which I concur.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
|
|
