INVALID_TIMESTAMP - User Changes Component does not Start

Last updated 3 months ago

Learn how to clear MongoDB from timestamps.

What you'll learn

Clear MongoDB from timestamps

Prerequisites

Having a CoreMedia system

Time matters

Reading time: 5 minute

Should I read this?

This guide is for Developers, Administrators.

Table of Contents

Solution
Workaround

You cannot start the User Changes webapp because of an INVALID_TIMESTAMP message.

The INVALID_TIMESTAMP indicates that the timestamps in the MongoDB database and the content repository don’t match.

The User Changes webapp is a content repository listener. The webapp listens to content events on Content Server and stores its timestamps in MongoDB. These events are triggered among others by the Studio user, for example, when editing content, checking in a content or deleting content.

When you first set up the CoreMedia system, the User Changes webapp starts with an empty MongoDB collections and starts listening for repository events. When restarting the User Changes webapp, the webapp tries to register itself as a listener with the Content Server with the last timestamp that it has saved in the MongoDB. If this timestamp is not found by the Content Server in the ChangeLog table, the Content Repository throws an error and the User Changes webapp doesn’t start.

Solution

Beginning with release 2506.0.0, the app will start even with a missing timestamp and only log a warning.

Workaround

You can clear the MongoDB collection with name "properties" and reboot the User Changes webapp. The collection is part of one of the following MongoDB databases:

blueprint_internal_models
cms_internal_models

You can use the following command to check for MongoDB databases and clear the MongoDB collection (replace coremedia:coremedia@localhost:27017 with your MongoDB connection string):

mongo 'mongodb://coremedia:coremedia@localhost:27017'

db.adminCommand( { listDatabases: 1 } )

{
...
{
"name" : "blueprint_internal_models",
"sizeOnDisk" : 557056,
"empty" : false
},
...

use blueprint_internal_models

show tables

db.properties.find()

db.properties.drop()

When you have cleared the MongoDB collection, you can restart the User Changes webapp:

service user-changes restart

Is this page useful?