IT42719: EBICS SERVER - FDL FROM CLIENT INTERMITTENTLY FAILING

APAR status

• Closed as program error.

Error description

• EBICS Server - FDL from Client intermittently failing. Some
  download orders like FDL are failing with error
  EBICS_INTERNAL_ERROR (return code 61099).
  The handleEBICSRequest BP is failing at the Ebics Server Service
  step and reports EBICS_INTERNAL_ERROR with a "No Msg Record"
  message in the status report.
  From Filegateway UI - Message Details, it is happening during
  the Transfer Response phase.
  
  Below errors is reported at the same time in the Ebics Server
  logs:
  
  [2022-11-29 12:02:49.552] ERROR
  [TransactionMgr.processDownloadTransferResponse()] Caught
  Exception:
  [2022-11-29 12:02:49.553] ERROR [1669723369553] 000110011504
  WORKFLOW.WORKFLOW.ERR_Document_SQLException8
  java.io.FileNotFoundException: WF608157657.dat (No such file or
  directory)
  [2022-11-29 12:02:49.553] ERRORDTL
  [1669723369553]java.sql.SQLException: 000110011504
  WORKFLOW.WORKFLOW.ERR_Document_SQLException8
  java.io.FileNotFoundException: WF608157657.dat (No such file or
  directory)
  at com.sterlingcommerce.woodstock.workflow.BaseDocument.getBody
  (BaseDocument.java:1765)
  at com.sterlingcommerce.woodstock.workflow.Document.getBody(Doc
  ument.java:2762)
  at com.sterlingcommerce.woodstock.services.ebics.server.Transac
  tionMgr.processDownloadTransferResponse(TransactionMgr.java:538
  3)
  at com.sterlingcommerce.woodstock.services.ebics.server.Transac
  tionMgr.processResponse(TransactionMgr.java:1079)
  at com.sterlingcommerce.woodstock.services.ebics.server.EBICSSe
  rverService.handleResponse(EBICSServerService.java:267)
  at sun.reflect.GeneratedMethodAccessor396.invoke(Unknown Source)
  
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
  thodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at com.sterlingcommerce.woodstock.services.ebics.EBICSService.p
  rocessMsg(EBICSService.java:150)
  at com.sterlingcommerce.woodstock.services.ebics.EBICSService.p
  rocessData(EBICSService.java:110)
  at com.sterlingcommerce.woodstock.workflow.activity.engine.Acti
  vityEngineHelper.invokeService(ActivityEngineHelper.java:1826)
  at com.sterlingcommerce.woodstock.workflow.activity.engine.Acti
  vityEngineHelper.nextMainLogic(ActivityEngineHelper.java:631)
  at com.sterlingcommerce.woodstock.workflow.activity.engine.Acti
  vityEngineHelper.next(ActivityEngineHelper.java:362)
  at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueL
  istener.doWork(WorkFlowQueueListener.java:459)
  at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueL
  istener.run(WorkFlowQueueListener.java:240)
  at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueL
  istener.onMessage(WorkFlowQueueListener.java:197)
  at com.sterlingcommerce.woodstock.workflow.queue.WorkFlowQueueL
  istener.onMessage(WorkFlowQueueListener.java:184)
  at com.sterlingcommerce.woodstock.workflow.queue.wfTransporter.
  run(wfTransporter.java:447)
  at com.sterlingcommerce.woodstock.workflow.queue.BasicExecutor$
  Worker.run(BasicExecutor.java:508)
  at java.lang.Thread.run(Thread.java:822)
  

Local fix

Problem summary

• Users Affected:
  EBICS Client user
  
  Problem Description:
  EBICS Server: FDL from Client is intermittently failing.
  The download document is written to the filesystem, so other
  nodes can't search it.
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  A code has been fixed to store document as per the workflow
  settings.
  
  Delivered in:
  6010104
  All future Fix Packs can be found in the Release Timeline Matrix
  - https://www.ibm.com/support/pages/node/6194265
  

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