PK05893: TEST CONNECTION FAILS WHEN JDBC XA DATASOURCE VARIABLE IS ADDED TO CUSTOM PROPERTIES AT NODE LEVEL FOR SERVERNAME ${DB2HOST} | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer is attempting to use the TestConnection feature of the Admin console. This works fine, however it fails when an env var is defined for the db2 classpath. The datasource works fine from the application with this variable coded, but fails in the the TestConnection path. WebSphere w510205 Using a WebSphere variable in a JDBC XA DataSource definition (the host name, to be specific), our customer could not get it pick up the variable. He is running in a network deployment, with two servers clustered. He defined a variable at the node level called DB2HOST with the value is wwwtest.xxx.state.xx.us. Then synced the system. He then created a DB2 Universal XA DataSource (for the same node), and in the custom properties tried to set the serverName variable equal to ${DB2HOST), but when he did a test the connection, it said it could not find ${DB2HOST}.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: A DataSource Test Connection operation * * will fail when a serverName DataSource * * custom property contains a variable * * reference. Also, Test Connection * * warning and error messages contain * * unusable links to server logs. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using the WebSphere Administrative Console to test a DataSource connection (Resources > JDBC Providers > provider > Data Sources > Test Connection), the operation will fail if the DataSource's serverName custom property value contains a variable reference, for example, ${DB2HOST}, with the variable reference not being resolved. Furthermore, warning and error messages reporting such a failure contain links to server logs which are not accessible in WebSphere for z/OS configurations. The following error message is an example of how this problem is reported to the Administrative Console user: "Test Connection failed for datasource MyDataSource on server dmgr at node PLEX1Manager with the following exception: java.lang.Exception: com.ibm.db2.jcc.b.SqlException: Unknown server ${DB2HOST}. <View server logs for further details.>"Problem conclusion Variable references in the serverName DataSource custom property value are now properly resolved. (Note: Variables must be defined on the WebSphere Variables page of the Administrative Console, accessed by clicking Environment > Manage WebSphere Variables.) Also, the unusable links to server logs have been removed. APAR PK05893 is associated with SERVICE LEVEL W502030 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PK03874 APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK05893.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK05893
IBM Group: Software Group
Modified date: Jun 2, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.