Actually, now that I look at that stack trace more closely, it's
specifically from identifying the issue's watchers (it really should
just look up the count, instead of identifying individuals, imo).
Btw, if you need someone to help figure out how to reproduce this
problem in a fresh-install JIRA database and/or how to resolve this
sort of db corruption, let me know. But I imagine Atlassian should
offer to help you guys out here.
- Daiji
java.lang.RuntimeException: Found more than one user with name
'aksonov'; ids [GenericEntity:OSUser][passwordHash,null][name,aksonov]
[id,23599], [GenericEntity:OSUser][passwordHash,null][name,aksonov][id,
23598]
at com.opensymphony.user.provider.ofbiz.OFBizAbstractProvider.findUser
(OFBizAbstractProvider.java:159)
at
com.opensymphony.user.provider.ofbiz.OFBizCredentialsProvider.handles
(OFBizCredentialsProvider.java:114)
at org.openqa.sass.osuser.SassOfbizProfileProvider.getPropertySet
(SassOfbizProfileProvider.java:24)
at com.opensymphony.user.Entity.getPropertySet(Entity.java:87)
at com.opensymphony.user.User.getFullName(User.java:83)
at com.atlassian.core.user.BestNameComparator.compare
(BestNameComparator.java:35)
at java.util.Arrays.mergeSort(Arrays.java:1284)
at java.util.Arrays.sort(Arrays.java:1223)
at java.util.Collections.sort(Collections.java:159)
at
com.atlassian.jira.issue.watchers.DefaultWatcherManager.getCurrentWatchList
(DefaultWatcherManager.java:59)
at
com.atlassian.jira.web.component.issuesummary.IssueSummaryWebComponent.getHtml
(IssueSummaryWebComponent.java:63)
at org.apache.jsp.decorators.issuesummary_jsp._jspService
(issuesummary_jsp.java:545)