PK12324: SHIP INTERNAL DEFECTS FOR W502034

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Ship internal defects for W502034
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PK12324 addresses the following    *
*                      defects in WebSphere Application Server *
*                      V5.0 for z/OS:                          *
*                                                              *
*                      (MD20798) Users will get error message, *
*                      "Host is required" when defining a      *
*                      MQ TopicConnectionFactory in the        *
*                      Administrative Console.  However a host *
*                      is not actually needed for defining a   *
*                      BINDINGS-mode ConnectionFactory.        *
*                                                              *
*                      (MD20863) If the Administrative Console *
*                      is configured for session persistence,  *
*                      a java.io.NotSerializableException will *
*                      be thrown when its session information  *
*                      is saved.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PK12324 addresses the following defects in WebSphere
Application Server V5.0 for z/OS:

(MD20798)   After defining a MQ TopicConnectionFactory under
Administrative Console panel:
Resources -> WebSphere MQ JMS Provider ->
WebSphere MQ Topic Connection Factories, and clicking "OK" or
"Apply", users will get an error message: "Host is required"
when a value is not specified for the "Host" field.  This field
is not  required when defining a ConnectionFactory in
BINDINGS-mode (i.e. TransportType="BINDINGS"), and so it is
incorrect to require this field before saving the
TopicConnectionFactory resource definition.

(MD20863) Session persistence for the Adminstrative Console may
be either be set at the application level
(Applications -> Enterprise Applications -> adminconsole ->
Session Management -> Distributed Environment Settings ->
Database or Memory to Memory Replication)
or the server level
(Servers -> Application Servers -> server_name ->
Web Container > Session Management ->
Distributed Environment Settings ->
Database or Memory to Memory Replication).

By definition, all session data must be serializable if it is
to be persisted.  This problem is caused by the presence of a
non-serializable object in the Administrative Console's session
data.

The result of this problem is that Administrative Console
session information will not be persisted to a database or
memory and  thus will not be available in failover situations.
The only other evidence of the problem are trace records
similar to the following in the server's servant joblog:

 Trace: 2005/08/22 20:41:32.446 01 t=8E1CF0 c=UNK key=P8
   Description: Log Boss/390 Error
   from filename: ./bborjtr.cpp
   at line: 850
   error message: BBOO0220E SESN0040E: BackedHashtable:
     commonSetup - problem streaming object. Exception caught
     while trying to serialize session data for subsequent
     database write. . . .
 Trace: 2005/08/22 20:41:32.450 01 t=8E1CF0 c=UNK key=P8
   FunctionName: com.ibm.ws.webcontainer.httpsession.
     SessionContext
   SourceId: com.ibm.ws.webcontainer.httpsession.SessionContext
   Category: ERROR
   ExtendedMessage: Exception: java.io.NotSerializableException:
     com.ibm.ws.console.core.bean.StatusBean$Tile
Problem conclusion
APAR PK12324 fixs the following defects in WebSphere
Application Server V5.0 for z/OS:

(MD20798) The Administrative Console was changed so the "Host"
field is not required after defining a MQ
TopicConnectionFactory.

(MD20863) The non-serializable session object was made
serializable.  Now the Administrative Console session data
can be successfully saved to a database or memory.

APAR PK12324 is asociated with SERVICE LEVEL W502034 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK12324
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-09-22
Closed date 2005-09-28
Last modified date 2005-10-04

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UK07674

Modules/Macros
BBOSSESS BBOUBINF BBOZ1474 BBOZ1475 BBOZ1479 BBOZ1480
BBOZ1483 BBOZ1506 BBOZ1508 BBOZ1514 BBOZ1524 BBOZ15
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced

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

Applicable component levels
R500 PSY UK07674    UP05/10/01 P F509

  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: swg1PK12324.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 #: PK12324
IBM Group: Software Group
Modified date: Oct 4, 2005