IC89342: SCP LOG TARGET MAY CAUSE SYSTEM HANG IF SCP SERVER IS UNRESPONSIVE
Fixes are available
Closed as fixed if next.
SCP log target may cause system hang if the SCP server is unresponsive during time of file upload. The appliance may remain in a hung/wait state for up to 130 seconds before it recovers and resumes processing. The log may show successive inactivity errors during the time of the hang: system,error,,,0,,0x80400025,,,"Watchdog system detects no activity for at least 49 seconds" system,critic,,,0,,0x80400025,,,"Watchdog system detects no activity for at least 50 seconds" Also, once the appliance recovers, the following log target errors may be seen at the end of the inactivity errors: [system][error] logging target(scp-log): tid(415730367): File not found. [system][error] logging target(scp-log): tid(415730367): Log upload of target scp-log failed.
Use Syslog log target instead.
Affected are users of all firmware releases up to and including version 5.0.0.x using log targets with SCP or SFTP upload method. SCP/SFTP log target may cause system halt if the the target SCP/SFTP server is unresponsive during time of file upload. The appliance may remain in a wait state for up to 130 seconds before it recovers and resumes processing. Fix will be provided in a next major release. No formal fix is planned for the current releases.
The safest workaround for the problem is to use upload method other than SCP or SFTP.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels
More support for:
WebSphere DataPower Integration Blade XI50B
Software version: 3.8.2
Reference #: IC89342
Modified date: 19 February 2013
Translate this page: