APAR status |
Closed as program error.
| Error description
(repository)
The WrapperManager cache in the EJB container inside the adminse
rver, can invalidate a reference to the home for a SM EJB
while this home is still being cached and used in a homeCache
inside RepositoryObjectImpl. This happens in very large
topologies (1000 URIs, 800 servlets, etc.
where the WrapperManager cache may overflow during normal admin
operations. Action item: please review defect 91141
defect is 91742 Local fix
Development is looking into this. The Cache size is hard coded Problem summary
cache size parameters associated with the EJB container, for
any container that is inside an application server. But there
does not appear to be a way to tune these same parameters for
the EJB container that is used internally within the
adminserver. This container is always created with the
default values 2047/2000/2047/1000 respectively for the
cacheSize, cacheSoftLimit, cacheHardLimit and
cacheSweepInterval parameters. (This happens in
AdminServer.java, with defaults coming from
ActiveEJBContainerConfig.java). Problem conclusion
correct this problem:
com/ibm/ejs/sm/server/AdminServer.java
com/ibm/ejs/sm/server/AdminServerConfigConstants.java correct this problem:com/ibm/ejs/sm/server/AdminServer.javacom/ibm/ejs/sm/server/AdminServerConfigConstants.java Temporary fixComments
APAR information | APAR number | PQ45602 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-01-29 | Closed date | 2001-03-12 | 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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R300 PSY | UP | R350 PSY | UP |
|