IBM Support

IT13711: BIP3383E FROM FILEINPUTNODE WITH SFTP TRANSPORT IF THE FLOW IS DEPLOYED TO MULTIPLE INTEGRATION SERVERS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a message flow with FileInput node is configured with SFTP
    transport and the same flow is deployed to multiple integration
    servers then BIP3383E errors can get logged into the broker
    syslog file.
    
    BIP3383E: File node 'MyFileInputNode' in message flow
    'MyMessageFlow' failed with reason 'Error while transfering file
    from server: inputFile.txt Reason: No such file' when
    transferring 'java.io.FileOutputStream@eae84540' to or from a
    remote 'SFTP' server.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 and V10.0 using the
    FileInput node with sftp transport protocol.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a message flow with FileInput node is configured with SFTP
    transport and the same flow is deployed to multiple integration
    servers then BIP3383E errors can get logged into the broker
    syslog file.
    
    BIP3383E: File node 'MyFileInputNode' in message flow
    'MyMessageFlow' failed with reason 'Error while transferring
    file from server: inputFile.txt Reason: No such file' when
    transferring 'java.io.FileOutputStream@eae84540' to or from a
    remote 'SFTP' server.
    
    The above error is logged against each remote input file that
    the flow failed to transfer as the same remote file has already
    been processed and deleted by message flows running on other
    integration servers.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product no longer logs BIP3383E against a remote input file
    which has been processed and deleted by other integration server
    message flows.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.5
    v9.0       9.0.0.7
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13711

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-10

  • Closed date

    2016-08-22

  • Last modified date

    2016-08-22

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020