Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Paige Livingston (PaigeL16845303)
UnitedHealth Group
SR Software Developer
UnitedHealth Group
US
PaigeL16845303 Member since 2023 8 posts
UnitedHealth Group
Posted: Feb 5, 2018
Last activity: Feb 6, 2018
Posted: 5 Feb 2018 10:22 EST
Last activity: 6 Feb 2018 7:25 EST
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

To see attachments, please log in.
Data Integration

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice