PK73931: THE DEFAULT DELAY FOR THE CORE GROUP BRIDGE TUNNEL IS TOO HIGH AND CAUSES THE WEBSPHERE SECURE DMZ PROXY TO GENARATE HTTP 503

Fixes are available

APAR status

Closed as program error.

Error description

The core group bridge tunnel delays sending data from the
backend cell if no data is immediately available.  However, the
default delay value is too high and can cause the WebSphere
Application Server Secure DMZ Proxy to generate 503 errors
when an application is initially started in the backend cell.

Local fix

The following steps can be taken to avoid the problem:
To set the custom property do the following:

1) Go to Servers -> Core Groups -> Core group bridge settings
2) Go to Tunnel access point groups
3) Click the tunnel access point group used in your test
4) Go to Core group access points
5) For each core group access point do the following:
 a.  Select the core group access point and click "Show Detail"
 b.  Go to Custom properties and create the custom property
cgb.tunnel.sendDelay with a value of 400

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0 Secure DMZ Proxy                       *
****************************************************************
* PROBLEM DESCRIPTION: The default core group bridge send      *
*                      delay is too high.                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The high default core group bridge send delay caused the
DMZ proxy to take too long to receive end point data from
the back-end WebSphere Application Server cell.  This
can cause the proxy to respond with 503s for about 30
seconds when a back-end application is first started.

Problem conclusion

The default core group bridge send delay (amount of time to
queue data when none is immediately available) was changed to
400 milliseconds from 17 seconds.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK73931
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-16
Closed date
2008-11-04
Last modified date
2008-11-04

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022

Tips

PK73931: THE DEFAULT DELAY FOR THE CORE GROUP BRIDGE TUNNEL IS TOO HIGH AND CAUSES THE WEBSPHERE SECURE DMZ PROXY TO GENARATE HTTP 503

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

R700 PSY

Document Information

Share your feedback

Need support?