APAR status
Closed as program error.
Error description
Log message 0x08040008d ?Binary Data: Maximum message size exceeded? is logged only in the system log of the default domain. It should be logged in the application domain where the corresponding maximum message size was configured for a specific service object.
Local fix
Review the system log from the default domain when searching for this log message.
Problem summary
When using max-message-size service parameter to limit the maximum accepted binary message size, the accompanying log message indicating the message has been rejected due to exeeding this limit is not logged in the application domain's log, showing in the default domain's log instead. Additionally, the message logged is identical to the case when a message has been rejected due to insufficient memory. No information about the service and transaction ID is provided.
Problem conclusion
The fix is available in 3.8.1.18, 3.8.2.9, 4.0.1.6 and 4.0.2.2.
Temporary fix
Check also the default domain's log when looking for cases of rejected oversize binary messages.
Comments
APAR Information
APAR number
IC78400
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
380
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-30
Closed date
2011-11-30
Last modified date
2011-12-15
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
DATAPOWER
Fixed component ID
DP1234567
Applicable component levels
R381 PSN
UP
R382 PSN
UP
R401 PSN
UP
R402 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.8","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022