Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by rhero
, 1 year ago
Timestamp limit changed underneath us (limit in memory: 46126139, limit in DB: 47126145). This may indicate that an other timestamp service is running against this database! If you get this error check that your client.prefs in dispatch is configured correctly.
com.palantir.timestamp.MultipleRunningTimestampServiceError: Timestamp limit changed underneath us (limit in memory: 46126139, limit in DB: 47126145). This may indicate that an
other timestamp service is running against this database!  If you get this error check that your client.prefs in dispatch is configured correctly.	at com.palantir.atlasdb.keyvalue.dbkvs.timestamp.InDbTimestampBoundStore$1.run(InDbTimestampBoundStore.java:95)	at com.palantir.atlasdb.keyvalue.dbkvs.timestamp.InDbTimestampBoundStore$1.run(InDbTimestampBoundStore.java:84)	at com.palantir.nexus.db.pool.RetriableTransactions$1LexicalHelper.attemptTx(RetriableTransactions.java:191)	at com.palantir.nexus.db.pool.RetriableTransactions$1LexicalHelper.run(RetriableTransactions.java:147)	at com.palantir.nexus.db.pool.RetriableTransactions.run(RetriableTransactions.java:249)	at com.palantir.atlasdb.keyvalue.dbkvs.timestamp.InDbTimestampBoundStore.runOperation(InDbTimestampBoundStore.java:84)