PK94508: THE ADMIN CONSOLE DISPLAYS THE DEFAULT MAXIMUM TRANSACTION TIMEOUT VALUE AS 0. THE LOG SHOWS THE CORRECT VALUE (300).

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The default value for Maximum transaction timeout is 300, which
  is reflected in the log correctly. However, the admin console
  under
  Servers -> Application servers -> (server name) -> Container
  services -> Transaction service
    displays this with a value of 0.
  .
  This is only a problem for the default value. Any changes made
  to the Maximum Transaction Timeout are correctly reflected in
  the admin console.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM WebSphere Application       *
  *                 Server                                       *
  *                                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Administrative Console displayed    *
  *                      the default Maximum Transaction         *
  *                      Timeout value as 0.                     *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The Administrative Console displayed the Default Maximum
  Transaction Timeout value as 0 when the Transaction Service
  panel was displayed - the default value is 300.
  On version 6.0 servers the default value was shown as 0, even
  when a Version 6.1 or Version 7.0 Deployment Manager was being
  used to administer the version 6.0 server.
  
  The root cause of this problem was that the Transaction
  Service Controller responsible for building the Transaction
  Service Properties panel did not take into account that the
  property propogatedOrBMTTranLifetimeTimeout (used to control
  Maximum Transaction Timeout) might not be present in the
  server configuration file. If the property was not present,
  which is true for the default value, the Transaction Service
  Controller calculated the value as 0.
  

Problem conclusion

• The Transaction Service Controller will be changed to test for
  the presence of propogatedOrBMTTranLifetimeTimeout in the
  server configuration file before displaying the Maximum
  Transaction Timeout value. If the property is present the
  panel will display the value defined. If the property is not
  present the panel will display the Maximum Transaction Timeout
  value as 300.
  
  APAR PK94508 is currently targeted for inclusion in Service
  Level (Fix Pack) 6.1.0.27 of WebSphere Application Server
  V6.1.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PK86696

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

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R610 PSY UK49671

     UP09/09/21 P F909

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.