My Oracle Support Banner

Uninstantiated Lazy Relationship Exceptions Are Observed in Logs for the Audit of Approval Payments (Doc ID 2853926.1)

Last updated on MARCH 10, 2022

Applies to:

Oracle Banking Digital Experience - Version 20.1.0.0.0 to 21.1.0.0.0 [Release 20 to 21]
Information in this document applies to any platform.

Symptoms

Below exceptions are observed in obdx logs when AuditMDBEAR runs.

ERROR
-----------------------
[com.ofss.digx.common.converter.JSONConverter] [tid: [ACTIVE].ExecuteThread: '84' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: ] [APP: AuditMDBEAR] [partition-name: DOMAIN] [tenant-name: GLOBAL] [< 107-2711-0485-3877-5344 >] Exception encountered while invoking the service com.ofss.digx.common.converter.JSONConverter in convertObjectValueToDataValue [[
com.fasterxml.jackson.databind.JsonMappingException:
Exception Description: An attempt was made to traverse a relationship using indirection that had a null Session. This often occurs when an entity with an uninstantiated LAZY relationship is serialized and that lazy relationship is traversed after serialization. To avoid this issue, instantiate the LAZY relationship prior to serialization. (through reference chain: com.ofss.digx.app.approval.dto.transaction.TransactionActionDTO["transactionDTO"]->com.ofss.digx.app.payment.dto.transaction.PaymentTransactionDTO["entityIdentifiers"])
at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:394)
at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:353)
.
.
.
at com.ofss.fc.infra.das.orm.eclipselink.EclipseLinkJTATransactionWrapper.commit(EclipseLinkJTATransactionWrapper.java:121)
at com.ofss.digx.domain.audit.entity.repository.adapter.LocalAuditRepositoryAdapter.create(LocalAuditRepositoryAdapter.java:77)
at com.ofss.digx.domain.audit.entity.repository.adapter.LocalAuditRepositoryAdapter.create(LocalAuditRepositoryAdapter.java:26)
at com.ofss.digx.domain.audit.entity.repository.AuditRepository.create(AuditRepository.java:82)
at com.ofss.digx.domain.audit.entity.Audit.create(Audit.java:806)
at com.ofss.digx.audit.mdb.AsyncAuditMDB.doAuditing(AsyncAuditMDB.java:129)
at com.ofss.digx.audit.mdb.AsyncAuditMDB.onMessage(AsyncAuditMDB.java:87)


EXPECTED BEHAVIOR
-----------------------
OBDX log file should not have lazy relationship exceptions.


STEPS
-----------
1. Login to OBDX application as corporate user.
2. Initiate a payment which goes to approver for approval.
3. Check the OBDX logs when approver approves and AuditMDBEAR runs.

Note - It doesn't have any impact on application behavior or any error at UI level.

 

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.