My Oracle Support Banner

Empty Handoff File Is Generated at Host Server Location If Uploaded File Has More than 100 Records. (Doc ID 2734130.1)

Last updated on JULY 26, 2021

Applies to:

Oracle Banking Digital Experience - Version 18.2.0.0.0 to 18.2.0.0.0 [Release 18]
Information in this document applies to any platform.

Symptoms

If uploaded file has more than 100 records then OBDX (Oracle Banking Digital Experience) application is placing empty handoff file at host server location.

ERROR
-----------------------
[<Date>] [<Server Name>] [ERROR] [] [com.ofss.digx.app.fileupload.service.UploadService] [tid: [ACTIVE].ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <Ecid Value>] [APP: <App Value>] [partition-name: <Partition-name value>] [tenant-name: <Tenant-name value>] RuntimeException from writeHandoffFile method of class com.ofss.digx.app.fileupload.service.UploadService for responseDTO 'com.ofss.fc.service.response.TransactionStatus@22c52a79'[[
java.lang.ClassCastException: java.lang.String incompatible with [Ljava.lang.Object;


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login with corporate maker user.
2. Navigate to File Upload > Upload file with more than 100 records against File level approval file identifier.
3. Login with corporate checker user.
4. Authorize file.
5. Once file status is changed to ''Authorized', an empty handoff file will be placed at host server location as uploaded file has are more than 100 records.


*Note : Applicable for FCR (Flexcube Retail) ,OBPM (Oracle Banking Payments) host.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.