APAR status
Closed as program error.
Error description
EAR file is being deleted in V5.0.2.3 when application is
installed using the administrative console
Problem can be reproduced in a WebSphere Application Server
V5.0.1 environment, where
PQ76005 is applied. In a clustered
configuration:
1. Open administrative console
2. Select Enterprise Applications/Install
3. Select "Server Path".
4. Browse to one of the base server's installableApps folder
(on a remote server) and choose an EAR, such as
perfServlet.EAR.
5. Complete install.
6. Save the configuration.
7. TEST: Verify the config/temp folder on the dmgr system has a
perfServlet.EAR.
8. Install
PQ76005 on both servers.
9. RETEST:
In the case of 5.0.2 and 5.0.1 the EAR file in config\temp is
deleted after applying fix
pq76005.
Customer observed that EAR is not deleted when choosing
the server path in administrative console, even after
applying
PQ76006.
Note: Problem can also be reproduced using a JACL script that
invokes wsadmin commands.
Local fix
Manually delete it from config/temp
Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users *
* installing an application from the *
* administrative console by choosing *
* Server Path ->browse to Base server *
* installable apps(remote box)->install *
* application. *
****************************************************************
* PROBLEM DESCRIPTION: If you install an application from *
* administrative console by choosing *
* Server Path ->browse to Base server *
* installable apps (remote box)->install *
* application, you will find the EAR *
* file present in *
* DeploymentManager/Config/temp *
* directory *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The EAR file in DeploymentManager/Config/temp directory is not
getting deleted. If you install from the administrative
console by choosing Server Path -> browse to Base server
installable apps (remote box) -> install application, you will
find the EAR file present in DeploymentManager/Config/temp
directory.
The problem only occurs when choosing Server Path -> nodename
and not with local path.
Problem conclusion
Code has been changed so that the EAR file will not be present
in DeploymentManager/Config/temp directory.
Temporary fix
Fix is scheduled for delivery in next cumulative fix.
Comments
APAR information |
APAR number |
PQ90033 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-06-11 |
Closed date |
2004-07-19 |
Last modified date |
2005-03-16 |
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 |
|