APAR status
Closed as program error.
Error description
The list of required attributes for the Queue Connection
Factory is incorrect. We can see the list by doing:
wsadmin>$AdminConfig required WASQueueConnectionFactory
Attribute Type
name String
jndiName String
However, only including these attributes will result in an
incomplete Queue Connection Factory. There are other
required attributes such as "node", "ConnectionPool" and
perhaps others.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users who *
* attempt to configure a *
* QueueConnectionFactory using wsadmin *
****************************************************************
* PROBLEM DESCRIPTION: The list of required attributes shown *
* by wsadmin for creating a new *
* QueueConnectionFactory is *
* incorrect. *
* *
* Below is the command and the result *
* for list of required *
* attributes *
* for creating a *
* WASQueueConnectionFactory. *
* wsadmin>$AdminConfig required *
* WASQueueConnectionFactory *
* Attribute Type *
* name String *
* jndiName String *
* *
* But creating a WASQCF with only *
* these parameters *
* will result in an incomplete WAS *
* Queue Connection Factory. *
* Node will be one of another required *
* attributes. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Below is the command and the result for the list of required
attributes for creating a WASQueueConnectionFactory.
wsadmin>$AdminConfig required
WASQueueConnectionFactory
Attribute Type
name String
jndiName String
But creating a WASQCF with only these parameters will result
in an incomplete Application Server Queue Connection Factory.
Node will be one of the other required attributes.
The problem was happening because wsadmin was pulling the list
of required attributes from the validation.xml used by the
administrative console.
In the administrative console, the Node input was a selectbox
and so a value was always selected by default and it was not
required that this value be made a mandatory field.
So the validation.xml did not enforce the node as a required
parameter.
This affected the list of required attributes while creating a
WASQueueConnectionFactory using wsadmin.
Problem conclusion
Code changes have been made to resolve the problem.
The APAR has been integrated to cumulative fixes 5.0.2.17 and
5.1.1.11.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK20200 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-02-22 |
Closed date |
2006-03-28 |
Last modified date |
2006-03-28 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
Applicable component levels |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|