I would like to know more about the counter count-up conditions.

Please be aware that the page you are viewing has been machine translated from Japanese into English and may contain some translation errors. If you observe any issues with the translation, please contact us.

Issue

• The counter seems to go up 100 counts after rebooting.I am not sure of the specifications under what conditions it counts up.

Environment

• DXP7.0+

solution

• When Liferay stores data in the database, the counter function automatically retrieves the numbering.
  Also, to prevent overloading the database, the numbering is pre-assigned in batches according to the value of counter.increment.
  Specifically, it obtains the value of the counter in the database at startup and reserves 100 of the graded numbers in advance in the default configuration.
  In the general operation of Liferay, when there is a write to the database, the reserved quotas are consumed.When the allocation runs out, it is again secured in the next batch.
  
  
• If the system is restarted with an excess number of grading, that excess will be lost.In that case, there will be a gap in the numbering.
  
  
• Other than a restart, the unconsumed portion of the secured grading is lost only when Liferay is stopped.
  
  
• In portal-ext.properties, when the value of counter.increment is set to 1, the setting itself can be set so that the missing number does not appear even after a restart.(e.g. 104 last time ⇨ after restart, numbering starts at 105)
  However, we do not recommend setting the value to 1, as this will affect performance.
  
  

Additional Information

• Counter Service auto increasing to "100" after everytime restart server
• Why are User-ID counters decreasing in a cluster system?