APAR status |
Closed as program error.
| Error description
The original efix introduced the problem of NOT wlmizing the
jar files while deploying a bean even though the operation
itself would be successful. The user would be able to use the
beans but they would not participate in WLM even though the
user did all the necessary things for WLM.
.
The original efix was for 3.5.3. The updated efix should work
with 3.5.3 and 3.5.4 as well. Local fix
pq52367.jar Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users of *
* WLM with PQ47464 applied. *
****************************************************************
* PROBLEM DESCRIPTION: After PQ47464, jars that should have *
* participated in WLM no longer did. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
As a result of the change made for PQ47464, the jar file that
was supposed to be wlmized (_wlm_Deployedwlmtest.jar) was NOT
wlmized. In other words, _wlm_Deployedwlmtest.jar did not
contain the xxxx_BaseStub.x files (for example,
Entity1Home_BaseStub.class and Entity1Home_BaseStub.java).
Since the _wlm_Deployedwlmtest.jar file was not wlmized, WLM
was not involved in routing the requests.
.
The change for defect PQ47464 changed the JarUtil's constructor
from using the EJBJar constructor without the classloader
parameter to using the EJBJar constructor with the classloader
parameter. Thus, the loadDeploymentDescriptors() method was not
called and the interfaces were not set up. Problem conclusion
The two EJBJar constructors were made equivalent.
Code was changed in:
com/ibm/ejs/util/jar/EJBJar.java Code was changed in:com/ibm/ejs/util/jar/EJBJar.java Temporary fixComments
APAR information | APAR number | PQ52367 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-09-12 | Closed date | 2001-09-14 | Last modified date | 2001-12-17 |
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
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 | APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels | R350 PSY | UP |
|