Fixes are available
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When the wsadmin utility is launched in connected mode, it accesses the local repository of the profile where launched: profile_root/config/temp/download/ when it should be accessing the repository of the server to which wsadmin is connected which results in permission related Workspace WKSP0012E errors in the Dmgr's SystemOut.log file, for example: . 08/30/12 15:21:50:250 EDT] 0000002f WorkSpaceMast E WKSP0012E: Exception while extracting cells/was7Cell/nodes/wastest/ node.xml from ConfigRepository - com.ibm.websphere.management.exception.DocumentIOException: Unable to create temp file for document: cells/was7Cell/nodes/wastest/node.xml . This occurs when the customer invokes wsadmin.sh as root user, and the Dmgr is started as another user, wasuser. . As a temporary workaround, client changes the ownership back to wasuser to avoid the above permission workspace related error in the SystemOut.log files on the Deployment Manager . The content under the profile_root/config/temp/download directory written by wsadmin is due to the fact that when the wsadmin tool is running in connected mode, it mistakenly accesses the local repository of the profile where wsadmin is launched. However, it should be accessing the repository ( profile_root/config/temp/download/ sub-directory) of the server to which wsadmin is connected. For example, if the dmgr is started as wasuser, and wsadmin is started by a different userid, for example, root user, the contents under profile_root/config/temp/download will be assigned as the userid that invokes wsadmin; this behavior caused permission issues. Environment: WebSphere Application Server ND - Distributed 7.0.0.23 Fixpack
Local fix
As a temporary workaround, client can change the ownership back to wasuser to avoid the above permission workspace related error in the SystemOut.log files on the Dmgr.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: When starting wsadmin with a different * * user (different from server's login), * * a WorkSpace exception: unable to * * create temp file for document * * was thrown. * **************************************************************** * RECOMMENDATION: * **************************************************************** When starting wsadmin and server with different user ids, a WorkSpace DocumentIOException will be thrown. The error occurred because the wsadmin had mistakenly accessed the local repository document with the wsadmin user when connecting to the server.
Problem conclusion
It is a bug in the wsadmin code that mistakenly accessed the local repository document when it is connecting to the server. This has been corrected. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.27, 8.0.0.6, and 8.5.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM73437
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-09-21
Closed date
2012-10-24
Last modified date
2012-10-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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021