PQ91384: CONM6009E UNABLE TO CONNECT TO CLOUDSCAPE DUE TO OPENING FILES IN READ ONLY MODE WEBSPHERE APPLICATION SERVER V5 | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description UDDI console can't connect to Cloudscape Database. CONM6009E: Unable to get connection to the database from datasource (UDDI.Datasource.NA1B.WSBS2B). **** ExtendedMessage: createConnection; SQL Exception: Failed to start database '/TESTAPPS/WebSphere390/V500/AppServ52/bin/UDDI20', see the next exception for details. **** ERROR 40XD1: Container was opened in read only mode . *************************************************** Documentation concern: URL >>> http://publib.boulder.ibm.com/infocenter/wasinfo/ index.jsp?topic=/com.ibm.websphere.zseries.doc/i nfo/zseries/ae/twsu_install_dmc.html Topic >>> Installing the UDDI Registry into a deployment manager cell heading >>> Steps for this task ----------- Step number 11 states "run the db2profile script" which does not need to be invoked.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: This Apar resolves three issues- * * * * 1. With UDDI configured along with a * * Cloudscape Database installed within * * the WebSphere z/OS Application * * Server, the following error, which is * * displayed within the Sysprint process * * logs, can occur during Server * * startup- * * * * CONM6009E: Unable to get connection * * to the database from datasource * * * * 2. Incorrect * * DB2ConnectionPoolDataSource class * * referenced in setupuddi.jacl script. * * The exception- * * * * CONM6009E: Unable to get connection * * to the database from datasource * * * * is displayed within the Sysprint * * process logs and can occur during * * Server startup. * * * * 3. When creating a DB2 datasource for * * use with UDDI, the userid and * * password fields are required * * attributes, which does not * * correspond with the documentation. * **************************************************************** * RECOMMENDATION: * **************************************************************** For issue 1: With Cloudscape configured as the Database for the UDDI Registry, the application fails to start during server startup. The following message appears in the Servant process logs- CONM6009E: Unable to get connection to the database from datasource In addition, the "Test Connection" action, available through the Administrative console as well as the adminstrative scripting tool, fails with the same exception. The Server does not have the authority to write to the UDDI-Cloudscape files located within the <$WAS_HOME>/bin/UDDI20/ directory and therefore fails. The Cloudscape driver for UDDI persists data to these files and the server must be able to read and write to them. For issue 2: setupuddi.jacl creates a V4 datasource which references the COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource class as its implementation class. The package name for z/OS is com.ibm.db2.jcc.DB2ConnectionPoolDataSource. By using the wrong implementation class, the datasource fails to connect to the DB2-based UDDI database. For issue 3: The documentation is correct to not list the userid and password as required attributes for creating the UDDI datasource, instead both jacl scripts- appserversetupuddi.jacl and setupuddi.jacl incorrectly require the userid and password to be set.Problem conclusion For issue 1: A postinstall action has been shipped which replaces the links under the <$WAS_HOME>/bin/UDDI20 directory with the actual files. For issue 2: setupuddi.jacl now creates a V4 datasource that references the proper implementation class- com.ibm.db2.jcc.DB2ConnectionPoolDataSource For issue 3: both setupuddi.jacl and appserversetupuddi.jacl no longer require the userid and password attirbutes for creating the UDDI datasource. APAR PQ91384 is associated with SERVICE LEVEL W502017 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PQ91398 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ91384.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 #: PQ91384
IBM Group: Software Group
Modified date: Dec 2, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.