|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Problems running JMSAdmin |
« View previous topic :: View next topic » |
Author |
Message
|
javierDiaz |
Posted: Fri Oct 25, 2002 5:19 am Post subject: Problems running JMSAdmin |
|
|
Novice
Joined: 04 Mar 2002 Posts: 13 Location: Ireland
|
Hi there,
I am getting the following when running JMSAdmin:
$ JMSAdmin
Exception in thread "main" java.lang.NoSuchMethodError: com.ibm.mq.MQEnvironment.runningInWS()Z
at com.ibm.mq.jms.services.ConfigEnvironment.<clinit>(ConfigEnvironment.java:173)
at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:184)
at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1818)
I am pretty sure that CLASSPATH includes all the jar files required. I am using MQSeries V5.1 on a Solaris box and downloaded the MA88 supportPac yesterday from the IBM web site.
I would really appreciate any help. I have searched this site but couldn't find a similar topic.
Thanks,
Javi |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Oct 25, 2002 7:26 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
I would guess that you have some kind of environment error since MQ 5.1 has been out of support for a while and the latest MA88 probably doesn't work with it.
I did do a search on an internal database. The only problem that I found indicated that there were problems with the level of MA88. However, since you downloaded it yesterday, I would guess your problems are with the MQ 5.1. |
|
Back to top |
|
 |
harwinderr |
Posted: Fri Nov 15, 2002 1:12 am Post subject: |
|
|
 Voyager
Joined: 29 Jan 2002 Posts: 90
|
The JMSAdmin tool has nothing to do with the MQSeries version whatsoever, as it is just a Java tool, which enables administrators to create and define the properties of eight types of MQSeries JMS object and to store them within a JNDI namespace.
The configuration error that you are getting is maybe because you have not properly configured the JMSAdmin.config file, which is the default configuration file for the MQSeries Classes for Java Message Service Administration Tool.
By default, it indicates an LDAP service provider. If a different service provider is used, then this line should be commented out and the appropriate one should be uncommented. Same thing goes for the URL provider also.
I generally configure to use it for file system context. So I just uncomment the following two lines and comment the others:
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory
(you need to manually create the directory)
Also make sure that you have the following jar files in the classpath:
com.ibm.mq.jar, com.ibm.mqjms.jar, fscontext.jar, jndi.jar, jms.jar,
connector.jar, and providerutil.jar.
Hope this will help
Later,
harwinder |
|
Back to top |
|
 |
kingdon |
Posted: Fri Nov 15, 2002 2:32 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002 Posts: 63 Location: UK
|
A couple of things to check:
You could get this error from using inconsistent versions of com.ibm.mqjms.jar and com.ibm.mq.jar, so make sure that you are not picking up an old version of com.ibm.mq.jar.
There have been some reports of problems using jdk 1.2.x with the latest MA88, so if you are using a 1.2 jdk, it might be worth trying a newer version.
Cheers,
James. |
|
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
|
|
|
|