APAR status |
Closed as fixed if next.
| Error description
ON PAGE 40 IN REDBOOK SG24-6153-00, ADMINISTRATIVE SERVERS CAN
PARTICIPATE IN WORKLOAD MANAGEMENT, HOWEVER I SPOKE WITH JOHN K.
IN ROCHESTER AND THAT FUNTIONALITY IS NOT THERE. I RECREATED BY
SETTING UP AN OSEREMOTE/MODEL AND CLONE ENVIRONMENT, AND SIMPLY
PULLED THE PLUG ON ONE OF THE SERVER TO SIMULATE A DOWN SYSTEM.,
THE APPLICATION DID NOT FAILOVER, THE ADMIN CONSOLE DID NOT SHOW
A FAILOVER AND THE ADMIN GUI HUNG. I WAITED FOR 30 MINUTES TO
SEE IF CONSOLE OR ADMIN SERVER WOULD RECOVER. HAD TO REBOOT
BOTH SYSTEMS. THIS DEFECT SHOULD SERVE AS A DOCS ISSUE AND ADMIN Local fixProblem summary
Automatic console failover was never a planned or implemented
feature. The client would need to know the alternate bootstrap
host/port etc. to even try to reconnect with the other
AdminServer making this a manual procedure. To implement this,
WebSphere would need to add the infrastucture to administer
such a feature (entering and storing alternate AdmSrv's to
connect to) plus the failover ability to dynamically connect
to an alternative server.
.
This APAR is being closed FIN. It will be fixed in the next
release of WAS, if any. Problem conclusionTemporary fixComments
APAR information | APAR number | PQ47777 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED FIN | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-04-10 | Closed date | 2001-06-19 | Last modified date | 2001-06-19 |
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 | R350 PSN | UP |
|