APAR status
Closed as program error.
Error description
During concurrent starts of containers that are hosted on WebSphere Application Servers, a workspace conflict causes the container to not start. The following workspace conflict is displayed in the logs: [12/11/12 12:20:05:412 GMT] 00000000 WorkSpaceMast E WKSP0011E: Unable to create existing session id file D:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\ObjectGridCa talogComponentImpl_684_1352722805366\workspace\.workspace_ --java.io.IOException: Access is denied. A trace shows that this conflict causes the deletion of the catalogservice.xml file: [12/11/12 12:20:05:802 GMT] 00000000 RepositoryCon < getPath Exit D:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\ObjectGridCa talogComponentImpl_684_1352722805366\workspace\cells\ObjectGridC ell01 [12/11/12 12:20:05:802 GMT] 00000000 WorkSpaceMast 3 release: D:\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\ObjectGridCa talogComponentImpl_684_1352722805366\workspace\cells\ObjectGridC ell01\catalogservice.xml [12/11/12 12:20:05:802 GMT] 00000000 FileAccessorU 3 delete cells/ObjectGridCell01/catalogservice.xml [12/11/12 12:20:05:802 GMT] 00000000 FileAccessorU 3 delete cells/ObjectGridCell01/catalogservice.xml.workspace_save [12/11/12 12:20:05:802 GMT] 00000000 FileAccessorU 3 exist [0] "cells/ObjectGridCell01/catalogservice.xml.copy" [12/11/12 12:20:05:802 GMT] 00000000 FileAccessorU 3 exist [0] "cells/ObjectGridCell01/catalogservice.xml.current" [12/11/12 12:20:05:802 GMT] 00000000 FileAccessorU 3 delete cells/ObjectGridCell01/catalogservice.xml.current.workspace_save When the catalogservice.xml file is not found, the container defaults to using catalog.services.cluster property. If this property is not found, the container default to looking for the catalog server on the deployment manager (DMGR). If the DMGR is not hosting the catalog service, the request will timeout, with the following message: [12/11/12 12:21:05:582 GMT] 00000042 ServerImpl W CWOBJ7300W: This server failed to bootstrap to a catalog server at the following address(es): dmgr.ibm.com:9809. Will retry in 5000 ms. This causes the container to not start.
Local fix
Workaround: On 7.1.1, the catalog.services.cluster is deprecated but still used as a backup. Defining the catalog servers with this property will allow the containers to start. More info about defining that property can be found here: http://publib.boulder.ibm.com/infocenter/wxsinfo/v7r0/topic/com. ibm.websphere.extremescale.admin.doc/txscatalogstartwas.html
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere eXtreme Scale * * embedded in WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: Concurrent starts of containers on * * the same host cause a workspace * * conflict. * **************************************************************** * RECOMMENDATION: * **************************************************************** Each container needs a session identification to access configuration information. Containers starting on the same host were using the same identification and conflicting with each other.
Problem conclusion
Each container now starts with a unique session identification based on its name and a time stamp.
Temporary fix
Comments
APAR Information
APAR number
PM77266
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-16
Closed date
2012-11-29
Last modified date
2012-11-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R711 PSY
UP
R850 PSY
UP
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"711","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 November 2012