Question

2
Replies
41
Views
PaigeR11 Member since 2014 6 posts
United Health Group
Posted: 2 years ago
Last activity: 2 years 8 months ago
Closed

JMS Fatal Exceptions

We are receiving errors in our logs: Steps to reproduce. Has anyone seen these errors:

  • File listener will read the File and gives each record as input to JMS queue and save the record data in Data base accordingly

  • If JMS cannot Process in first run , we have agent which again pulls the record from DB and resend it to JMS queue

  • JMS will do either of following may be case creation if that data does not exist in system else updates the existing case if that data is already associated with a case

  • After successful process Record will be updated as processed in Data base

2018-02-02 03:31:13,655 [default-threads - 41] [ STANDARD] [ ] [ CLMS:01.01.01] (internal.database.ReporterImpl) FATAL JMS|UPMCReconMergeIntake|Services|ReconcileClaimMergeIntake|A470D09934E9676871574E5DC01B8C821 - The element at the top of the stack:

2018-02-02 03:31:13,655 [default-threads - 41] [ STANDARD] [ ] [ CLMS:01.01.01] (internal.database.ReporterImpl) FATAL JMS|UPMCReconMergeIntake|Services|ReconcileClaimMergeIntake|A470D09934E9676871574E5DC01B8C821 - Element being removed

java.lang.Throwable

Data Integration
Moderation Team has archived post
Share this page LinkedIn