Retail Point-of-Service Solutions (MOSC)

MOSC Banner

Random parsing errors and Invalid POS log character

edited Nov 12, 2019 4:02AM in Retail Point-of-Service Solutions (MOSC) 1 commentAnswered

Hi,

We are getting random parsing errors on our poslog.xml coming from the store's pospoll.zip file.

For example, Store poslog has an XML tag not formatted correctly.

See line #97 and Transaction # 1566 from the poslog attachment.

we found below exceptions in xstore.log related to same transaction seq. [complete xstore.log attached]

WARN [ ] 2019-09-23 07:13:41,251 tmp\1-7117-1569196800000-1-1566.trn: Does not exist in temp storage! :: dtv.pos.common.TransactionHelper [startup]

WARN [ ] 2019-09-23 07:13:41,251 Orphaned transaction ID: 1::7117::1569196800000::1::1566 was written to database :: dtv.pos.startup.orphanedtrans.CheckForOrphanedTransWorker [startup]

WARN [ ] 2019-09-23 07:13:41,251 Orphaned transaction: 1::7117::1569196800000::1::1566 was written to TLog and marked as posted :: dtv.pos.startup.orphanedtrans.CheckForOrphanedTransWorker [startup]

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center