This is almost always due to a combination of an incomplete client installation and / or a CLASSPATH problem. Many people capture jar files rather than performing a full installation and not necessarily getting all of them. Sometimes they just search for jar files and grab them, regardless of different versions. IBM has extensively refactored Java / JMS classes with V7.0 and has made some updates since then. Starting with version V7.0.1, WMQ can be installed on arbitrary directory paths and several installations on the server. This meant that now there could be several JRE / s, several client installations, etc. This did not affect CLASSPATH so much, but it changed the dependencies such as NLS support, tracking, and other things that the Java classes depend on ./p>
The recommendation is to install the full WMQ client and specify CLASSPATH in the installation directory. If this is not possible, then somewhere install the full client and take a set of standard cans from a well-known installation. Then at least you know that you have all the same versions, etc.
If you decide to install the full client from the IBM distribution, you will get several additional features, such as diagnostics and low-level tracing. It also ensures that service can be applied. For example, if you have a problem fixed in a fix pack, you simply install the fix pack on top of an existing client installation. Fix Pack will not be installed if all you have are jar files.
WMQ clients are available as SupportPacs . You can download one of the following values:
Be sure to use Infocenter for the version of the client you are using!
source share