IC69077: FILENODES SHOULD NOT EMIT ERROR WHEN LOCKFILE ALREADY EXISTS

WebSphere Message Broker V7.0 - Fix Pack 7.0.0.1
WebSphere Message Broker V7.0 - Fix Pack 7.0.0.2
WebSphere Message Broker V6.1 - Fix Pack 6.1.0.9
WebSphere Message Broker V7.0 - Fix Pack 7.0.0.3
WebSphere Message Broker V6.1 - Fix Pack 6.1.0.10

APAR status

• Closed as program error.

Error description

• When using multiple WebSphere Message Broker File Input nodes,
  (any version, but reported in version 6.1) and the nodes are all
  reading from the same input directory, a spurious BIP3315 error
  can be thrown to the syslog:
  
  
  BIP3315E: File node '<node name>' in message flow 'flow name'
  cannot move file '<file name>' from directory '<dir name>' to
  subdirectory '<dir name>/mqsitransitin/locks'. The file node
  attempted to move a file to a subdirectory but could not. Either
  there is a file of that name already in the subdirectory, or the
  file system prevents the action...
  
  
  
  The node intends to move the input file to the
  mqsitransitin directory. Before this can happen the node will
  create
  an empty file in the locks directory with the same name as the
  input file, then, and only then, copy the input file to the
  mqsitransit directory for processing. An execution group will
  scan the input
  directory for a file that is not locked to begin processing.
  
  In a case where there are few files in the directory, a second
  execution group will note that all files have been locked, and
  throw an exception that the first file it looked at is locked.
  There is nothing wrong with an execution group not getting a
  file to lock on since the file will be processed successfully by
  another execution group.
  

Local fix

• Have multiple File Input nodes read from separate input
  directories
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker version 6.1 fixpack 6 or
  higher using FileInput nodes in multiple Execution Groups or
  multiple Brokers to access the same input directory.
  
  Platforms Affected:
  All Platforms
  ****************************************************************
  PROBLEM SUMMARY:
  When multiple Execution Groups are sharing an input directory
  for FileInput nodes it is possible for the 2 processes to
  experience contention creating a lockfile in the
  mqsitransitin/locks directory. If an execution group is unable
  to obtain any files from its directory list due to contention
  then it will emit a BIP3315 error to the syslog.
  

Problem conclusion

• WebSphere Message Broker has been modified so that the BIP
  message is no longer emitted in these circumstances as we assume
  that another EG or Broker will have obtained the lock and
  processed the target file.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  V6.1 - Maintenance Level 6.1.0.9
  
  V7.0 - Maintenance Level 7.0.0.2
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.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 in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• 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

  WMB WINDOWS V6

• Fixed component ID

  5724J0500

Applicable component levels

• R610 PSY

     UP