APAR status |
Closed as duplicate of another apar.
| Error description
EJB jar deployment from GUI fails even if the node or appserver
has jar in classpath needed by EJB being deployed.
.
Note from developer:
We have traced down the client and server codes and found it was
not the Admin console (GUI) problem. The problem might be in
server ActiveFileBrowserService or some ejs utility files.
There were some code changes in those files between 3.5.3 and
3.5.5 Note from developer:We have traced down the client and server codes and found it wasnot the Admin console (GUI) problem. The problem might be inserver ActiveFileBrowserService or some ejs utility files.There were some code changes in those files between 3.5.3 and3.5.5 Local fix
n/a Problem summaryProblem conclusionTemporary fixComments
APAR information | APAR number | PQ52237 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DUB | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-09-07 | Closed date | 2001-09-14 | Last modified date | 2001-09-14 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General Software version: 350 Reference #: PQ52237 IBM Group: Software Group Modified date: 2001-09-14
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|