[JRASERVER-26636] Database sequences can reach a certain size that prevents additional sequences from being created Created: 21/Dec/2011 Updated: 20/Feb/2017 Resolved: 26/May/2015
|Project:||JIRA Server (including JIRA Core)|
|Component/s:||Infrastructure & Services - Application Lifecycle|
|Affects Version/s:||4.2.1, 4.4.5|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
In certain situations it is possible for OfBiz sequences to reach a certain size that prevents additional sequences from being created.
JIRA will continue to operate as normal.
Either of the following:
The below errors can be found in the Catalina log:
According to entitymodel.xml column SEQ_ID in table SEQUENCE_VALUE_ITEM defined with numeric type
Which for Mysql defined (in fieldtype-mysql.xml) as decimal(18,0) and mapped to a Java Long:
In SequenceUtil in ofbcore-jira-entity-2.1.7.jar in lines 205, 237 called method ResultSet.getInt, instead of ResultSet.getLong. This causes total JIRA unavailability after one of Sequence (in our case OSPropertyEntry) surpasses the border of the upper signed integer limit. This limit is Integer.MAX_VALUE, 2147483647.
|Comment by David Currie [ 26/May/2015 ]|
Tested this on JIRA 6.4.4 using MySQL and was not able to replicate, the sequences are correctly increased:
Test was to create a new issue and comment on it, we can see the below are successfully incremented:
|Comment by Matt Doar [ServiceRocket] [ 19/Nov/2015 ]|
I would expect this still exists. It may depend on the OS on which MySQL is running, or version of MySQL. Also I don't see how your test shows that the seq_ids have been incremented. You seem to be searching for ones that have not changed.
|Comment by David Currie [ 19/Nov/2015 ]|
This is true, I just tested this on JIRA 7 and wasn't able to repro. Test was:
Worked fine to me - if you can repro please give us exact steps and we can investigate further.