Thanks Tony, I appreciate your quick response.

I had actually "stumbled" onto this late yesterday afternoon. In my 
specific case, the JVM was loading a MQEnvironment class from 
com.ibm.mqbind.jar (which didn't have an addConnectionPoolToken method). I 
changed the classpath so that com.ibm.mq.jar was ahead of the mqbind.jar 
and the JVM then loaded the MQEnvironment class (the "correct" one) from 
there.

I'm not aware of anything like this, but wouldn't it be nice if there was 
a "utility" to scan the classpath and point out all of the multiple 
occurances (duplicates) of classes (and somehow indicate which is highest 
in the list and will be loaded by the JVM)? I know I sure could make use 
of something like this.

Thanks again,

Bill




> Bill
> 
> make sure you have a clean classpath as IBM tends to add reference to 
other 
> JAR files without you knowing.
> 
> what i would recommend doing is copying and saving  your current 
classpath 
> into a file called say "classpath.old.txt" and create a new classpath 
and 
> just add the references to the jdk and mq jar files as outlined in the 
ibm 
> installation document. I found this sorted everything out..
> 
> CLASSPATH=C:jdk_dir\lib\tools.jar;
> install_dir\lib\com.ibm.mq.jar;
> install_dir\lib\com.ibm.mq.iiop.jar;
> install_dir\lib\connector.jar;
> install_dir\lib\;
> install_dir\samples\base\;
> 
> email me if you have any further problems
> 
> Tony
>