PK01396; 5.0.2, 5.1.1: WSADMIN throws
configserviceexception after PQ92961
Downloadable files
Abstract
wsadmin $ADMINCONFIG modify $QQUEUECONNECTIONFACTORY
$ATTRIBUTESCOMMAND throws CONFIGSERVICEEXCEPTION after PQ92961
Download Description
PK01396 resolves the following problem:
ERROR DESCRIPTION:
If the jndiName exists then AdminConfig modify command throws following
exception:
$AdminConfig modify $QQueueConnectionFactory $attributes
Throws the following exception:
WASX7015E: Exception running command:
"$AdminConfig modify $qcf $attributes"; exception information:
com.ibm.websphere.management.exception.ConfigServiceException:
ADMG0037E: New instance of MQQueueConnectionFactory object can not be
created since the "jndiName" attribute of an existing
MQQueueConnectionFactory object has same value "jms/DefaultQCF".
Above action works at IBM® WebSphere® Application Server V5.0.2.3 but
fails at WebSphere Application Server V5.0.2.9 level. Also WebSphere
Application Server administrative console does not prevent duplicate
jndiName creation.
PROBLEM SUMMARY:
USERS AFFECTED:
WebSphere Application Server Users of all versions of 5.0.2 and 5.1.1.
PROBLEM DESCRIPTION:
$AdminConfig modify $ds {{description "test description}}
During the invocation of the above command from wsadmin, the jndiName
attribute is validated for a duplicate name which is incorrect. This APAR
is a replacement for the ZEd APAR PQ92961.
RECOMMENDATION:
jndiName attribute is validated during the modify operation. But, ideally
the check for a duplicate jndiName should be validated for resources (like
URL's, DataSource) during the create operation.
PROBLEM CONCLUSION:
Code has been corrected to check the validity of the jndiName attribute
during create operation.
This APAR is targeted for 5.1.1.4 and 5.0.2.11.
Please refer to the recommended updates page for delivery information: General/swg27004980.html)
Prerequisites
WAS 5.0.2.9 Service pack should be installed on the target
machine.