View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0025442||mantisbt||db mssql||public||2019-02-04 17:44||2019-03-16 20:20|
|Target Version||2.20.0||Fixed in Version||2.20.0|
|Summary||0025442: Wrong/duplicate bugnote_text_id in mantis_bugnote_table|
After we upgraded to MantisBT 2.11.1 in December 2018, users have noticed phantom notes added to their ticket/issue with their names on it. A query of the database shows that we have multiple bug_id pointing to the same bugnot_text_id. Attached is a screenshot showing the result of the select statement below. It show three bugnote pointing to the same bugnote_text. Those 3 notes were submitted within 15 seconds by different users in different issue#. Can you please advise what the issue/cause may be?
select id, bug_id, reporter_id, bugnote_text_id, view_state,
|Steps To Reproduce|
Different users adding notes to different issue # withing seconds of each other. This issue appears to be random. However, we've had 83 instance of this occurring (83 bugnot_text_id, 181 issue#) since Dec 10, 2018.
|Tags||No tags attached.|
are you using sql-server?
with mssql it uses SELECT IDENT_CURRENT to get the id of the inserted note, which:
This is the first time I see such an issue.
The provided information is not sufficient to provide help in resolving the issue.
Why did you use this outdated version?
I recommend to upgrade to latest stable version (2.19.0 at the moment).
We are using SQL server. The reason we are using an outdated version of MantisBT has to do we the business requirement for using IE 11 in compatibility mode and to display realname instead of username. We've tried newer version of MantisBT but the primary problem is that it doesn't render correctly in IE compatibility mode. Below are answers to your questions about our build:
yes, with a debug session that is forced to wait between both inserts.
Some general remarks
I assume you are talking about this effect https://mantisbt.org/forums/viewtopic.php?f=3&t=25649
Is there still an issue after all those changes in 2.15.0 ?
I hope you are aware that
Your countdown for upgrades is running :-)
MantisBT: master c0c7eb1c
Committer: atrol Details Diff
|Fix mssql concurrent insert id
The implementation of db_insert_id() in mssql relied on IDENT_CURRENT
making it not thread safe.
Modify it to use ADOdb native implementation, based on SCOPE_IDENTITY()
which is session independent.
|mod - core/database_api.php||Diff File|
|2019-02-04 17:44||juliexn||New Issue|
|2019-02-04 17:44||juliexn||File Added: duplicate bugnote_text_id.JPG|
|2019-02-04 17:51||juliexn||File Added: duplicate bugnote_text_id-2.JPG|
|2019-02-04 17:55||cproensa||Note Added: 0061398|
|2019-02-04 18:01||atrol||Status||new => feedback|
|2019-02-04 18:01||atrol||Note Added: 0061399|
|2019-02-04 18:36||cproensa||Note Added: 0061400|
|2019-02-04 18:40||juliexn||Note Added: 0061401|
|2019-02-04 18:40||juliexn||Status||feedback => new|
|2019-02-04 19:07||cproensa||Category||bugtracker => db mssql|
|2019-02-04 19:07||cproensa||Description Updated||View Revisions|
|2019-02-04 19:07||cproensa||Assigned To||=> cproensa|
|2019-02-04 19:07||cproensa||Status||new => assigned|
|2019-02-04 19:07||cproensa||Note Added: 0061402|
|2019-02-04 19:13||cproensa||Note Added: 0061403|
|2019-02-04 20:21||juliexn||Note Added: 0061404|
|2019-02-04 20:32||cproensa||Note Added: 0061405|
|2019-02-07 13:29||atrol||Note Added: 0061445|
|2019-02-07 13:30||atrol||Target Version||=> 2.20.0|
|2019-02-07 13:42||juliexn||Note Added: 0061446|
|2019-02-11 15:35||atrol||Changeset attached||=> MantisBT master c0c7eb1c|
|2019-02-11 15:35||cproensa||Status||assigned => resolved|
|2019-02-11 15:35||cproensa||Resolution||open => fixed|
|2019-02-11 15:35||cproensa||Fixed in Version||=> 2.20.0|
|2019-03-16 20:20||vboctor||Status||resolved => closed|