IT07586: RECOVER.BPML BUSINESS PROCESS HALTS BUSINESS PROCESSES THAT HAVETHE SFTP CLIENT PUT SERVICE IN "WAITING ON I/O" STATUS

5.2.6.0
si_52_build_5020500_interimfix_11
si_52_build_5020500_interimfix_11
iSeries_Media_5020601_2
Media_IM_5020601_2
iSeries_Media_5020601_2

APAR status

• Closed as program error.

Error description

• This issue only occurs once it has been a number of weeks
  since IBM Sterling B2B Integrator has been stopped and
  restarted. For the customer experiencing this issue, that
  interval was usually between six and eight weeks after the last
  restart. Once the issue starts occurring, when the SFTP PUT
  service goes into "Waiting on IO" status during transfers of
  one or more large files, if the Recover.bpml business process
  is run, it terminates the business processes assocated with the
  SFTP file transfers. There are no particular errors in the logs
  associated with this issue. It only occurred in cases where the
  Recover.bpml business process took at least 5 minutes to run.
  The issue occurred with the following settings in place in
  customer_overrides.properties:
  bprecovery.disableNodeCheck=false
  bprecovery.nodeCheckIn=5
  bprecovery.auto_terminate_days=3
  bprecovery.num_states=4
  bprecovery.auto_terminate_state2=interrupted_auto
  bprecovery.auto_terminate_state3=interrupted_man
  bprecovery.auto_terminate_state4=waiting
  bprecovery.auto_terminate_batch=10000
  

Local fix

• STRRTC - 439690
  NM / NM
  Circumvention:
  There are two ways to work around this issue. One is to
  schedule a stop and restart of IBM Sterling B2B integrator at
  an interval shorter than when the issue starts happening. For
  example, if the issue is seen to happen after the application
  has been up for 5 weeks, schedule a stop and restart once every
  four weeks.
  
  The other option is to change the value of the
  defaultDelayWaitingOnIO parameter to -1 in either
  sftp.properties or customer_overrides.properties. Doing that
  prevents the service from ever going into "Waiting on IO"
  status, so the Mark Service does not take note of the businss
  process. This may not be a viable option on instances where
  there a lot of large files being transferred at the same time,
  as there is a possibility of the system backing up. That is
  because threads are recovered for use while a business process
  is in "Waiting on IO" status, but that thread recovery does not
  occur if the business processes cannot go into that status.
  

Problem summary

• Users Affected:
  All
  
  PROBLEM DESCRIPTION:
  SFTP PUT Service goes into "Waiting on IO"
  status when transferring a large file and the Recover.bpml
  business process runs. Recover.bpml terminates the
  SFTP business process.
  
  Platforms Affected:
  All
  

Problem conclusion

• A code fix is provided.
  
  Delivered In:
  
  5020500_11
  5020601_2
  

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

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels