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

Fixes are available

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 PK86696 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.37 of WebSphere Application Server
V6.0.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 number
PK86696
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-15
Closed date
2009-06-16
Last modified date
2009-10-05

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

PK94508 PK97886

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK49499
UP09/08/29 P F908

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R601 PSY UK49499

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

Share your feedback

Need support?