APAR status
Closed as program error.
Error description
PROBLEM:
Files in /wstemp directory do not get deleted and the directory
continues to grow and grow in size. The files are never purged
after being created.
The admin console creates a directory upon startup, but when the
admin console is closed it doesn't cleanup the /wstemp
directory.
.
This problem could also negatively impact workload management
(WLM). The deployment manager's routing tables may become
corrupted or not filled in. The following exception would be
thrown in the deployment manager:
.
WKSP0011E: Unable to create existing session id file
/opt/WebSphere/5.0/DeploymentManager/wstemp/com.ibm.ws.wlm111151
3073102/workspace/.workspace_
--java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native
Method)
at java.io.File.createNewFile(File.java:688)
...
As a result, EJB lookups will fail. The following exception
would be seen on the EJB client JVM:
.
org.omg.CORBA.NO_IMPLEMENT: No Useable Targets minor code:
1229066304 completed: No
at
com.ibm.ws.wlm.client.selection.WLMLSDRouter.getNextTarget(WLMLS
DRouter.java:214)
at
com.ibm.ws.wlm.client.WLMClientLegacyImpl.getNextTarget(WLMClien
tLegacyImpl.java:318)
at
com.ibm.ws.wlm.client.WLMClient.getNextTarget(WLMClient.java:195
)
at
com.ibm.ws.orbimpl.services.lsd.LocationServiceDaemon.getDirectI
OR(Unknown Source)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2139)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:63)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Local fix
Workaround:
To delete the files, a kron job can be run every night to delete
files that are 2 days old. This is a limited workaround as some
files that are a day or less old can be 33MB per file.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server customers *
* using Administration Console. *
****************************************************************
* PROBLEM DESCRIPTION: After the user logs out from the *
* WebSphere Administration Console, the *
* workspace under the wstemp directory *
* is not cleaned up. Therefore, it takes *
* a lot of disk spaces. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A new interface is introduced in the Work Space component
to clean up the temporary workspace under wstemp directory.
The Web UI component calls this new interface to do the clean
up when user logs out.
Problem conclusion
A new interface is called to clean up the temporary workspace
under wstemp directory when users log out from Administration
Console.
The fix here attempts to handle the wstemp cleanup issue as
reported by the customer. What the fix does achieve is the
following. When a user logs on to the adminconsole and makes
some changes in the adminconsole and either saves or discards
the changes, now on logout the wstemp/xxxxxx/workspace directory
should disappear. Another scenario is when a user Logs on then
changes preferences and logs out. The wstemp/xxxxx/workspace
should be gone but the wstemp/xxxxxx/preferences.xml should
remain.
Temporary fix Comments
APAR information |
APAR number |
PQ78824 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-09-24 |
Closed date |
2004-01-27 |
Last modified date |
2005-03-31 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|