PK37706: ENABLE INSTALLATION CONFIGURABLE MESSAGE LENGTH LIMITS FOR 64BIT SERVERS FOR LOCAL COMMUMICATIONS, IIOP, AND HTTP MESSAGES.

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere application server for zOS version 6.1.0.4 removes
the 100MB message length limit for servers running in 64bit
mode. To enable a customizable limit on unchuncked message
sizes, create installation configurable limits for local
communictions, IIOP, and HTTP messages.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V6.1 for z/OS running in 64-bit mode.        *
****************************************************************
* PROBLEM DESCRIPTION: 64-bit support for WebSphere            *
*                      Application Server V6.1 for zOS removed *
*                      checking for message request length     *
*                      when the server is running in 64-bit    *
*                      mode. Customer feedback indicated that  *
*                      they require a means of specifying some *
*                      sort of limit. 31-bit mode servers      *
*                      still limit request messages to 10MB.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Code checks had been removed from native and java code paths
for request message length when in 64bit mode. 31bit
code maintains the usual 10MB size checks but when in 64bit
mode, the server became vulnerable to congestion and impaired
performance if extraordinarily large request messages come in.

Problem conclusion

The following three new z/OS application server custom
properties have been created and are used in vative and
Java code for enforcing request message size limits when the
server is running in 64bit mode:

1) iiop_max_msg_megsize
  Specifies, in megabytes, the maximum size for IIOP requests.
  For example, if a customer sets the property to 35, any
  requests over 35 megabytes are rejected. The minimum value
  for this property is 10 and the maximum value is 2048.
  Customers omit this property if they do not want to limit the

  size of IIOP requests.

  This custom property only applies for systems that are
  running in 64-bit mode. The maximum size for IIOP requests on
  systems that are running in 31-bit mode is still 10 megabytes.


  Set this custom property for an application server in the
  administrative console: click Application servers > server >
  Server infrastructure > Administration > Custom Properties.

2) local_comm_max_msg_megsize
  Specifies, in megabytes, the maximum size of locally
  connected communications requests. For example, if a customer
  sets the property to 35, any requests over 35 megabytes are
  rejected. The minimum value for this property is 10 and the
  maximum value is 2048. When the customer omits this property
  the size of locally connected communications requests are not
  limited.

  This custom property only applies for systems
  that are running in 64-bit mode. The maximum size for IIOP
  requests on systems that are running in 31-bit mode is 10
  megabytes.
  Set this custom property for an application server in the
  administrative console: click Application servers > server >
  Server infrastructure > Administration > Custom Properties.

3) protocol_http_large_data_inbound_buffer_64bit
  This specifies, in megabytes, the size limit for incoming
  HTTP requests when inbound HTTP chunking is disabled. Setting
  the property to 35 megabytes rcauses any HTTP request over
  35 megabytes to be rejected. If a customer specifyies 0 (zero)

  for this property the unchunked HTTP requests will have no
  size limit.

  Important: This custom property should only be used if the
  server is running in 64-bit mode. If the customer's system is
  running in 31-bit mode, they should use the
  protocol_http_large_data_inbound_buffer custom property to
  set a limit for this inbound buffer.

APAR PK37706 requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

http://www.ibm.com/software/webservers/appserv/library
 The following changes to the z/OS version of the WebSphere
Application Server Version 6.1.x Information Center will be
made available in June, 2007.
. The following descriptions of the three new z/OS
application server custom properties will be added to the
"Application server z/OS custom properties" topic:
.   iiop_max_msg_megsize
.   Specifies, in megabytes, the maximum size for IIOP requests.

  For example, if you set the property to 35, any requests
  over 35 megabytes are rejected. The minimum value for this
  property is 10 and the maximum value is 2048. Omit this
  property if you do not want to limit the size of IIOP
  requests.

  Important: This custom property only applies for systems
  that are running in 64-bit mode. The maximum size for IIOP
  requests on systems that are running in 31-bit mode is 10
  megabytes.
.   Data Type          Integer
  Default          0
  Used by Daemon  No
.   To specify a value for this custom property for an
  application server, in the administrative console, click
  Application servers > server > Server infrastructure >
  Administration > Custom Properties.
.   local_comm_max_msg_megsize
.   Specifies, in megabytes, the maximum size of locally
  connected communications requests. For example, if you set
  the property to 35, any requests over 35 megabytes are
  rejected. The minimum value for this property is 10 and the
  maximum value is 2048. Omit this property if you do not want
  to limit the size of locally connected communications
  requests.
.   Important: This custom property only applies for systems
  that are running in 64-bit mode. The maximum size for IIOP
  requests on systems that are running in 31-bit mode is 10
  megabytes.
.   Data Type          Integer
  Default          0
  Used by Daemon  No
.   To specify a value for this custom property for an
  application server, in the administrative console, click
  Application servers > server > Server infrastructure >
  Administration > Custom Properties.
.   protocol_http_large_data_inbound_buffer_64bit
.   Specifies, in megabytes, the size limit for incoming HTTP
  requests when inbound HTTP chunking is disabled. For example,
  if you set the property to 35 megabytes, any HTTP requests
  over 35 megabytes are rejected. Specify 0 (zero) for this
  property if you do not want to limit the size of unchunked
  HTTP requests.
.   Important: This custom property should only be used if your
  system is running in 64-bit mode. If your system is running
  in 31-bit mode, you should use the
  protocol_http_large_data_inbound_buffer custom property to
  set a limit for this inbound buffer.
.   Data Type          Integer
  Default          0
  Used by Daemon  No
.   To specify a value for this custom property for an
  application server, in the administrative console, click
  Application servers > server > Server infrastructure >
  Administration > Custom Properties.
. Also, the following note will be added to the description of
the protocol_http_large_data_inbound_buffer custom property
that is contained in this same topic:

  Important: This custom property should only be used if your
  system is running in 31-bit mode. If your system is running
  in 64-bit mode, use the
  protocol_http_large_data_inbound_buffer_64bit custom
  property to set a limit for this inbound buffer.

APAR PK37706 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.8 of WebSphere Application Server V6.1
for z/OS.

Temporary fix

Comments

APAR Information

APAR number
PK37706
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-01-18
Closed date
2007-04-10
Last modified date
2007-06-05

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

Modules/Macros

BBOCFDMN BBOCLCON BBOCSESS BBOMWENV BBOOBOAI BBOOBOAT BBOOJORB
BBOOORBR BBOOREQ  BBOOZJNI

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R500 PSN
UP
R601 PSN
UP
R610 PSY UK24627
UP07/05/11 P F705

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.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK37706: ENABLE INSTALLATION CONFIGURABLE MESSAGE LENGTH LIMITS FOR 64BIT SERVERS FOR LOCAL COMMUMICATIONS, IIOP, AND HTTP MESSAGES.

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:

Modules/Macros

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R500 PSN

R601 PSN

R610 PSY UK24627

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?