APAR status
Closed as program error.
Error description
If a JMS backend call fails (for example, if a JMS Messaging bus doesn't exist in an environment), hundreds of Network Error on Back interface entries flood the logs. It appears that the JMS continues to retry until the Error rule completes, despite the fact that retry is disabled for the JMS object. Given the configuration, the expected behavior is for only one error to appear in the logs.
Local fix
The issue occurs when remote DNS server cannot resolve the domain name provided by WebSphere JMS Endpoint So there is a workaround that can avoid this issue: Set "Host Alias" in default domain that can convert the domain name to assigned ip address.
Problem summary
WHO is likely to see this problem? DataPower customers using JMS as backend and the JMS object is unreachable. WHAT is the problem? The log will keep generating "Network Error on Back interface" WHY did the problem happen? Handle incorrectly when the JMS object is not up due to connection problem
Problem conclusion
3.7.3.18, 3.8.0.12, 3.8.1.11, 3.8.2.3
Temporary fix
Comments
APAR Information
APAR number
IC75221
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
373
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-23
Closed date
2011-04-18
Last modified date
2011-04-18
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
R373 PSY
UP
R380 PSY
UP
R381 PSY
UP
R382 PSY
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.7.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022