PQ78166: Portal server will not start after install on V5.02 of Websphere | |||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The apar should be routed to the runtime component of webpshere. They are aware of the problem via emails and have provided a fix. The apar is opened to process the fix an a official manner. Installing portal server (current build 20030818 11:20) on Wbsphere V5.02 base. After installation the portal does not initialize due to a configuration problem of the database resource. This works fine in V5.01 of Websphere. Possible causes: a) WAS 5.0.2 was changed to expect an additional parameter / step that Portal don't know of b) There is a bug in WAS 5.0.2 that prevents it to accept our configuration of the db resource. This is the workaround applied to bypass the problem: - open the WAS Administrative Console - In the navigation panel, select Resources->JDBC Provider - In the main panel, click "wps50JDBC" - Click "Data Sources" - click wps50DS - Click "Custom Properties" - Insert some text in the "Description" field - Click "Apply" - Save the modifications - start the WebSphere_Portal server (It should now complete without eceptions in the log file). One interesting thing that I observed are the changes in the file resources.xml. The differences are in the following lines: ===============Difference # 1=================================== The changed file (resources(good).xml) has the following: <factories xmi:type="resources.jdbc:DataSource" xmi:id="DataSource_1060776926692" name="wps50DS" jndiName="jdbc/wps50DS" description="JDBC DataSource for C:/work/drivers/WPS50_~4/bin/cloudscape/wps50" authMechanismPreference="BASIC_PASSWORD" authDataAlias="wpsDBAuth" statementCacheSize="10" datasourceHelperClassname="com.ibm.websphere.rsadapter.Cloudscap eDataSto reHelper" relationalResourceAdapter="builtin_rra"> The original resource.xml file has the following: <factories xmi:type="resources.jdbc:DataSource" xmi:id="DataSource_1060776926692" name="wps50DS" jndiName="jdbc/wps50DS" description="JDBC DataSource for C:/work/drivers/WPS50_~4/bin/cloudscape/wps50" authMechanismPreference="BASIC_PASSWORD" authDataAlias="wpsDBAuth" statementCacheSize="10" datasourceHelperClassname="com.ibm.websphere.rsadapter.Cloudscap eDataSto reHelper"> Note the difference is the good file has the following at the end: relationalResourceAdapter="builtin_rra"> ===============Difference # 2=================================== The changed file (resources(good).xml) has the following: <resourceProperties xmi:id="J2EEResourceProperty_1060776928144" name="description" type="java.lang.String" value="dummy" description="Description of the Data Source. Not used by the Data Source object. Used for informational purpose only." required="false"/> The original resource.xml file has the following: <resourceProperties xmi:id="J2EEResourceProperty_1060776928144" name="description" type="java.lang.String" value="" description="Description of the Data Source. Not used by the Data Source object. Used for informational purpose only." required="false"/> Note the difference is in the value field. ===============Difference # 3================================== The original file has the following: <relationalResourceAdapter href="resources.xml#builtin_rra"/> the changed file did not have that line. =============================================================== The exception in the log file when trying to start portal without using the work around is as follows: 2003.08.20 13:29:34.778 I com.ibm.wps.logging.LogManager init Trace specification: *=all=disabled 2003.08.20 13:29:35.309 E com.ibm.wps.services.naming.NamingServiceImpl lookup SERV0006E: Cannot find object * in JNDI context *. - StackTrace follows... 2003.08.20 13:29:35.309 E com.ibm.wps.services.naming.NamingServiceImpl lookup javax.naming.NameNotFoundException: jdbc/wps50DS. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFoun d(WsnOpt imizedNamingImpl.java:1999) at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimiz edNaming Context(WsnOptimizedNamingImpl.java:1316) at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetCo ntext(Ws nOptimizedNamingImplBase.java:2409) 2003.08.20 13:29:35.319 E com.ibm.wps.engine.Servlet init SERV0016E: Initialization of service failed. - StackTrace follows... 2003.08.20 13:29:35.319 E com.ibm.wps.engine.Servlet init com.ibm.wps.services.ServiceUnavailableException: DSTO0061E: The DataSource jdbc/wps50DS cannot be found. at com.ibm.wps.services.datastore.DataStoreServiceImpl.init(DataSto reServic eImpl.java:117) at com.ibm.wps.services.Service.init(Service.java:108) at com.ibm.wps.services.Service.init(Service.java:84) at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:268 ) Full stack traces are on wasdoc1. The installation logs for portal show that the datasources are created a nd does not seem to detect any errors.Local fix This is the workaround applied to bypass the problem: - open the WAS Administrative Console - In the navigation panel, select Resources->JDBC Provider - In the main panel, click "wps50JDBC" - Click "Data Sources" - click wps50DS - Click "Custom Properties" - Insert some text in the "Description" field - Click "Apply" - Save the modifications - start the WebSphere_Portal server (It should now complete without eceptions in the log file).Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server 5.0 users. * **************************************************************** * PROBLEM DESCRIPTION: Unable to resolve cross document * * references in the configuration XML * * files. * **************************************************************** * RECOMMENDATION: * **************************************************************** Href references in the configuration XML files that refer to other configuration XML files cannot be resolved. Typically an exception is logged during the server startup that either indicates some failure to retrieve the Eclipse Modeling Framework ( EMF ) configuration data or a NameNotFoundException if the configuratin data was being read by the runtime to populate the JNDI namespace.Problem conclusion The operational behavior of the URIConverter was modified such that it can now search heirarchically up the directory structure for the file referred to in the href tag.Temporary fix Temporary fix delivery and has been tested working, working on to create official fix.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ78166
IBM Group: Software Group
Modified date: Sep 16, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.