|
Problem(Abstract) |
When a queue connection factory (QCF) is configured in
WebSphere® Application Server V5.0, V5.0.1, or V5.0.2 to connect to a
WebSphere MQ queue manager, the following error can occur when the QCF is
bound to the namespace during application server startup:
WSVR0017E: Error encountered binding the J2EE resource,
QueueConnectionFactory, as
jms/QueueConnectionFactory from
file:
///usr/websphere/appserver/config/cells/cellname/nodes/nodename/resources.xml
com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid
configuration passed to resource binding logic. REASON: Failed to create
connection factory at
com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>(JMSConnectionFactoryReferenceable.java:132) |
|
|
|
Cause |
The problem occurs if the Transport Type for the QCF is
set to BINDINGS and any of the following QCF properties are also
set:
The properties listed above are meant to be used only if the Transport
Type is CLIENT. |
|
|
Resolving the
problem |
There are three ways to resolve the problem:
- Use the CLIENT Transport Type instead of
BINDINGS in the QCF definition.
- Use the BINDINGS Transport Type, but leave the
Host, Port, Channel, and CCSID properties blank in the QCF.
- Install Cumulative Fix 1 (5.0.2.1) or higher for V5.0.2.
If V5.0 or V5.0.1 are being used, you must install Fix Pack 2 (5.0.2)
first. Cumulative Fix 1 contains a fix (PQ76051) that changes the behavior
of WebSphere Application Server so that it ignores the Host, Port,
Channel, and CCSID properties when binding the QCF if the Transport Type
is set to BINDINGS. As a result, the WSVR0017E does not occur
during the application server startup and the QCF is bound to the
namespace successfully.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|