PQ84961: ZOS WEBSPHERE WITH THE HTTP PLUGIN RESULTS IN THE ZOS WEBSERVER ENDING WITH ABEND0C9 AT ASSUREWEIGHTSVALID+138

APAR status
Closed as fixed if next.

Error description
Customer was running zOS WebSphere V5 at W501001 and using
the zOS HTTP Plugin. The WebServer is ABENDING with an
Abend0C9 in assureWeightsValid() . The customer has coded a
<Server> tag in his plugin-cfg.xml that looks like:
        <Server
            CloneID="BA911C4E7D14BF80000002F0000000052B1C351F"
            LoadBalanceWeight="0" Name="ServerName">
            <Transport Hostname="host1.com" Port="9082"
                  Protocol="http"/>
</Server>
The LoadBalanceWeight="0" exposes a problem in WebSphere code.
    The LE TRACEBACK looks like:
Entry         E Addr    E  Offset   Statement  Load Mod  Service
__cdump       06D6E228  +0000017A              CEEEV003  DRIVER9
EDCOWRP1      06CA2748  +000006F0              CEEEV003
sig_prgchk    0DB8EFE8  +00000662              *PATHNAM
CEEPGTFN      06F07B58  +0000005A              CEEPLPKA
__zerros      06D70808  +000007EC              CEEEV003  DRIVER9
CEEHDSP       06E6B628  +00000C0C              CEEPLPKA
assureWeightsValid
              0E5BFA60  +00000138        1440  *PATHNAM  W501000

serverGroupNextRoundRobinServer
              0E5BE560  +00000120        1151  *PATHNAM  W501000
serverGroupSelectServer
              0E5C0100  +00000086         534  *PATHNAM  W501000
websphereFindServer
              0E59DC70  +00000180        2335  *PATHNAM  W501000
websphereWriteRequestReadResponse
              0E59D7B8  +00000230        2530  *PATHNAM  W501000
esiResponseCreate
              0E5E43E8  +00000538         576  *PATHNAM  W501000
esiResponseGet
              0E5E8108  +000000E0        1191  *PATHNAM  W501000
esiHandleRequest
              0E60B988  +00000104         155  *PATHNAM  W501000
websphereHandleRequest
              0E5A5398  +0000057E        2769  *PATHNAM  W501000
service_exit  0E5F9D18  +000007BC         599  *PATHNAM  W501000
AND SO ON......
Condition Information for Active Routines
  Condition Information for  (DSA address 0EEEEB28)
    CIB Address: 0EEEFE68
    Current Condition:
      CEE3209S The system detected a fixed-point divide
exception (System Completion Code=0C9)

    Location:
      Program Unit:  Entry: assureWeightsValid
     Statement:    1440 Offset: +00000138
   Machine State:
ILC..... 0002    Interruption Code..... 0009
PSW..... 078D0400 8E5BFB9A
GPR0..... 00000000  GPR1..... 00000001  GPR2..... 0E68FAF8
GPR3..... 0E5BFA9A
GPR4..... 0E630FD0  GPR5..... 0E634A68  GPR6..... 00000001
GPR7..... 0EEEEBDC
GPR8..... 0E634DC0  GPR9..... 0E622EC8  GPR10.... 00013D40
GPR11.... 00000002
Local fix
Do not code LoadBalanceWeight="0". This effectively prevents the
server from receiving any requests, same as removing the
<Server> tag from the <ServerCluster> tag all together.
Customer was using LoadBalanceWeight="0" as a convience to
remove the server from the environment.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: When running WebSphere Application      *
*                      Server V5.0 for z/OS using the          *
*                      zOS HTTP Plugin and specifying          *
*                      LoadBalanceWeight=0 in a <Server> tag   *
*                      in the plugin-cfg.xml file,             *
*                      the WebServer abends with Abend0C9 in   *
*                      assureWeightsValid().                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
LoadBalanceWeight=0 was preventing the server from receiving
any requests.

In the module "ws_server_group.c", the function
"weights_need_reset" should be called only once in the function
"assureValidWeights".  There is no need to loop until a server
with valid weights is found.  Also, current weight should be
bumped only if the server is marked up.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
release within the next 18 months.
APAR information
APAR number PQ84961
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-02-19
Closed date 2004-06-21
Last modified date 2004-06-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information

Applicable component levels
R500 PSN    UP


Document Information


Current web document: swg1PQ84961.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ84961
IBM Group: Software Group
Modified date: Jun 21, 2004