xmsTrigger Silently Crashes when Processing Delivery Receipts/Reports if xmsStore Isn't Running
Last updated on SEPTEMBER 27, 2017
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), Messaging Manager (MM) is a functional component used to process Short Message Service (SMS) messages.
One of the important features of MM is the ability to process Delivery Receipts/Reports (DRs) which are used to alert the sender of the SMS that the message has been successfully delivered to the intended recipient.
DRs are usually genereated by a Short Message Service Center (SMSC) (which MM will submit an SMS to) once it has successfully delivered the SMS to a handset. However because MM has the ability to perform direct delivery of SMS' to handsets (ie. emulating an SMSCs behavior), it too has the ability to generate a DR if the attempt to deliver the SMS to the handset was successful.
In MM, DRs are correlated to SMS' which can arrive days after the SMS was processed. As xmsTrigger has no concept of storage, it needs to interface with the xmsStore process which can store data long term in the underlying Oracle database.
If xmsStore is not running when xmsTrigger tries to process a DR, xmsTrigger will silently crash. No errors are logged so check the start time of the xmsTrigger process to see if it was recently started by the watchdog.
Introduction of DRs to MM.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms