javax.naming.NameNotFoundException: jms/BPECF
 Technote (troubleshooting)
 
Problem(Abstract)
The SystemOut.log contains a "javax.naming.NameNotFoundException: jms/BPECF", although WebSphere's® Administrative Console shows that the connection factory BPECF is configured correctly under the WebSphere MQ JMS Provider. The exception stack for this exception contains a com.ibm.websphere.naming.CannotInstantiateObjectException.
 
Cause
Either external WebSphere MQ was installed with the default installation, which doesn't install MQ Java and JMS support, or the jar files for MQ's JMS implementation are missing from the classpath. These jar files are found in the java/lib subdirectory of the MQ installation directory.
 
Resolving the problem
Install WebSphere MQ using custom installation and make sure that MQ Java and JMS support are selected.

Make sure, that WebSphere finds the jar files for MQ's JMS implementation. Usually, the jar files are found, if the WebSphere variable MQJMS_LIB_ROOT points to the java/lib subdirectory of the MQ installation directory, and the variable MQ_INSTALL_ROOT points to the installation directory for MQ. You can find these variables in the WebSphere Administration Console under Environment ->Manage WebSphere Variables, usually in the node scope.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Enterprise Edition (EE)
Operating system(s): Windows
Software version: 5.1
Software edition:
Reference #: 1113718
IBM Group: Software Group
Modified date: Nov 27, 2004