APAR status |
Closed as program error.
| Error description
Clients continue to tie themselves to shutdown appservers even
when trying to get new initial contexts (caching set to cleared)
It appears that WAS client IIOP code is caching some, but not
all, info about initial context request for the life of the JVM,
such as any subsequent initial context requests specifying the
same IIOP address will always be directed to the same appserver. Local fixProblem summary
Clients continue to tie themselves to shutdown appservers even
when trying to get new initial contexts (caching set to cleared)
It appears that WAS client IIOP code is caching some, but not
all, info about initial context request for the life of the JVM,
such as any subsequent initial context requests specifying the
same IIOP address will always be directed to the same appserver. Problem conclusionTemporary fixComments
APAR information | APAR number | PQ51608 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-08-17 | Closed date | 2001-08-22 | Last modified date | 2001-08-22 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|