PQ86451: Unable to start Deployment Manager or other Servers after upgrade from W502002 to W502003. 04/03/29 PTF PECHANGE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
After upgrading from W502002 to W502003, you can find the
following errors when starting up Deployment Manager and
other Servers:

BBOT0010I TRANSACTION SERVICE RESTART AND RECOVERY ON SERVER
serverX IS COMPLETE
BBOO0036E FUNCTION gsk_environment_init FAILED WITH RC=202.
BBOO0036E FUNCTION gsk_environment_init FAILED WITH RC=202.
BBOS0052E SSL security was specified but could not be
initialized.
BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C2127D.
BBOO0006E WEBSPHERE FOR Z/OS PROCESS serverX ENDED ABNORMALLY,
564 REASON=C9C21236.

BBOO0056E CONTEXT SERVICE 'CTXBEGC' FAILED WITH RETURN
CODE=301.
BPXP018I THREAD 32369F7000000036, IN PROCESS 67372428, ENDED 566
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04EC3000,

The CR tries to initialize the https port which fails with since
no keyring is defined.  You may not want to use SSL and global
security is disabled.  This same configuration does run with
W502002.


The last messages before the Deployment Manager ends are:

Trace: 2004/03/12 07:06:28.140 01 t=665088 c=UNK key=S2
(0E01100D)
  Description: Supported Securities failed to pick a Security
Mechanism
Trace: 2004/03/12 07:06:28.342 01 t=6A7088 c=UNK key=S2
(0E01100D)
  Description: Supported Securities failed to pick a Security
Mechanism
Trace: 2004/03/12 07:07:47.009 01 t=6B1088 c=UNK key=S2
(0301300A)
  Description: SessionManagerProtocolHTTPSSL::startListening()
 SSL not active -
Trace: 2004/03/12 07:07:47.009 01 t=6B1088 c=UNK key=S2
(0000000A)
  Description: Log Boss/390 Error
  error message: BBOO0021E Assertion failed: '0', file
./bboobsa.cpp, line 197.
Trace: 2004/03/12 07:07:47.013 01 t=6B1088 c=UNK key=S2
(0000001E)
  Description: Log Boss/390 Activity
  activity message: BBOO0035W TERMINATING THE CURRENT PROCESS,
REASON=C9C2127D.
...
Trace: 2004/03/12 07:07:47.421 01 t=6A9348 c=UNK key=S2
(0000000A)
  Description: Log Boss/390 Error
  from filename: ./bbo3ctxm.cpp
  at line: 550
  error message: BBOO0056E CONTEXT SERVICE 'CTXBEGC' FAILED WITH
RETURN CODE=301.

The following environment variables are picked up as seen in the
joblogs:
protocol_https_port: 9443.
com_ibm_Server_Security_Enabled: 0.


There seems to be problem after W502003, where WebSphere tries
to load System SSL even if Global Security is NOT enabled, and
at the same time it tries to initialize/use the https_port.  In
order to use that port, SSL has to be enabled.
                                                               .
================================================================
ADDITION INFORMATION:
This problem may also be seen at the W502000 level.
================================================================
Local fix
You should not see this problem if you enable Global Security.

If you do not want to use Global Security, that is Global
Security is DISABLED, then you should use on of the following
workarounds until the PTF for apar PQ86451 is applied.

Workaround choices:

1) Call into IBM WebSphere L2 to request for server.xsl temp
fix.

2) Delete the https_port until the you decide to enable
Global Security.
In order to do that, you will first have to set the https_port
to 0 (zero) in the was.env.
i.e.:
/WebSphere/V5R0M0/DeploymentManager/config/cells/PLEX1Network/
nodes/PLEX1Manager/servers/dmgr/was.env
so that the you can bring up the Deployment Manager.

The problem is that as soon as you save any changes in the
AdminConsole, the zero gets overwritten by the original port #
9443 (which resides in the server.xml)
/WebSphere/V5R0M0/DeploymentManager/config/cells/PLEX1Network/
nodes/PLEX1Manager/servers/dmgr/server.xml

Here are the steps to this workaround:
1)  Change the https_port to 0 in the DeplMgr's was.env
2)  Bring up the DeplMgr
3)  Bring up the NodeAgent
4)  Log into the AdminConsole
5)  Click on 'System Administrator'
6)  Click in 'Deployment Manager'
7)  Click in 'HTTP Transport'
8)  You should see 2 or more ports defined. The one that we're
    interested in is the one that has SSL Enabled, in this case
    9443
9)  Select that port and then click the Delete button
10) Click Save
11) In the save page, before clicking the Save button, make sure
    the 'Synchronize changes with Node' option is checked.
12) Restart the DeploymentManager and NodeAgent.
13) REMINDER: When you decide to enable Global Security you will
    need to add this HTTPS port back

A similar process needs to be followed in order to delete the
HTTPS port from the AppServers (repeat for all AppServers):
a) In the Admin Console click
     Servers->ApplicationServers->
b) Click on the server that you are planning to remove the HTTPS
   port
     serverX -> Web Container -> HTTP transports -> select the
     HTTPS port and click the Delete button.
c) Click Save and in the save page, making sure that the
   "Synchronize changes with Nodes" box is selected before
   clicking the SAVE button
d) Repeat this process for any other server that you may have
   created.
e) Start the servers.

If you would like to a more illustrative approach to this
workaround, you will need to contact IBM L2 for further
assistance.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: A failure occurs trying to start the    *
*                      Deployment Manager running              *
*                      Application Server V5.0 for z/OS        *
*                      (W502003 and above).                    *
*                      The server terminates with the          *
*                      following message:                      *
*                      BBOO0006E WEBSPHERE FOR Z/OS PROCESS    *
*                      serverX ENDED ABNORMALLY, 564           *
*                      REASON=C9C21236.                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After upgrading from W502002 to W502003, the following errors
are displayed when starting up Deployment Manager and other
Servers:

BBOO0036E FUNCTION gsk_environment_init FAILED WITH RC=202.
BBOO0036E FUNCTION gsk_environment_init FAILED WITH RC=202.
BBOS0052E SSL security was specified but could not be
          initialized.
BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C2127D.
BBOO0006E WEBSPHERE FOR Z/OS PROCESS serverX ENDED ABNORMALLY,
          REASON=C9C21236.
BBOO0056E CONTEXT SERVICE 'CTXBEGC' FAILED WITH RETURN
          CODE=301.
BPXP018I THREAD 32369F7000000036, IN PROCESS 67372428, ENDED
         WITHOUT BEING UNDUBBED WITH COMPLETION CODE 04EC3000,

The following traces can be seen in the SYSPRINT if traces for
the COMM component are enabled:
Trace: 2004/03/12 07:07:47.009 01 t=6B1088 c=UNK key=S2
Description: SessionManagerProtocolHTTPSSL::startListening()
             SSL not active -
Trace: 2004/03/12 07:07:47.009 01 t=6B1088 c=UNK key=S2
Description: Log Boss/390 Error
             error message: BBOO0021E Assertion failed: '0',
             file bboobsa.cpp, line 197.
Trace: 2004/03/12 07:07:47.013 01 t=6B1088 c=UNK key=S2
Description: Log Boss/390 Activity
activity message: BBOO0035W TERMINATING THE CURRENT PROCESS,
                  REASON=C9C2127D.

The problem is that the Controller tries to initialize the https
port and it fails because either SSL is not available or is not
set up correctly.
Problem conclusion
Changes were made to ensure that the https port is not
initialized, when SSL is not available.

APAR PQ86451 is associated with SERVICE LEVEL W502006 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ86451
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE YesPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-03-22
Closed date 2004-04-08
Last modified date 2004-05-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ87201    UP04/04/19 P F404

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ86451.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 #: PQ86451
IBM Group: Software Group
Modified date: May 5, 2004