Jira Error Occurred While Retrieving User With Username
Contents |
users wih assigned issuesLog In ExportXMLWordPrintableDetails Type: directory is not functional during authentication of skipped Bug Status: Resolved (View Workflow) Priority: High
Tried To Login But They Do Not Have Use Permission Or Weren T Found
Resolution: Duplicate Affects Version/s: 4.1.2 Fix Version/s: None Component/s: None
Jira Ldap Configuration
Labels: administration crowd, crowd_triage_required kaap294 Environment: Linux Server, Tomcat 6, Java 1.6, .tar.gz/war distribution Description we use
Confluence Sorry, An Error Occurred Trying To Log You In. Please Try Again.
JIRA to authenticate users via CROWD. crowd retrieves the users from an ActiveDirectory. when the users is deleted in the active directory it sooner or later 'disappears' from crowd (or the administrator deletes sorry, a communication error occurred while trying to contact the remote authentication server. the user in the crowd directory). then the user is no longer availble in jira. so issues assigned to that user cannot be re-assigned or edited. there is a stacktrace screen in the browser. the logs show an entity not found exception: 2011-01-11 10:36:05,371 TP-Processor19 ERROR [500ErrorPage.jsp] Exception caught in 500 page Error occurred while retrieving user with username 'mabr'. com.atlassian.jira.exception.DataAccessException: Error occurred while retrieving user with username 'mabr'. at com.atlassian.jira.issue.IssueImpl.getUser(IssueImpl.java:1124) at com.atlassian.jira.issue.IssueImpl.getAssignee(IssueImpl.java:403) at com.atlassian.jira.issue.IssueImpl.setAssignee(IssueImpl.java:416) at com.atlassian.jira.issue.fields.AssigneeSystemField.updateIssue(AssigneeSystemField.java:231) at com.atlassian.jira.web.action.issue.AssignIssue.doExecute(AssignIssue.java:132) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:171) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFil
tickets when the ticket owner or current assignee is deleted from Windows-AD-DirectoryLog In ExportXMLWordPrintableDetails Type: Bug Status: Open (View ldap error code 49 Workflow) Priority: Medium Resolution: Unresolved Affects Version/s: 3.13.4 Fix Version/s: None Component/s: Project Administration - Workflows, User Management - Others Labels: None Environment: Issue does not depend on client environment Symptom Severity: Major Description As in all companies people come and go, but https://jira.atlassian.com/browse/JRA-23424 Jira can not handle this correctly. With leaving the company the peoples are deleted from our Windows-ActiveDirectory. When doing so and the person has created tickets or is current assignee the tickets can be opened but you can not change the owner or https://jira.atlassian.com/browse/JRA-20959 assigne or close the issues. At present we do recreate a "dummy-account" with the former username of the deleted account in crowd to be able to shift the tickets to an other person. Further more: you can not search for "deleted" accounts deleted accounts can not be deleted from the projekt roles as they are not listed in the edit view A well working solution is very much appreciated. Best Andreas See the error message below while trying to close or editing a ticket from a deleted person. Snip>--------------------------------------------------------------------- Ursache: com.atlassian.jira.exception.DataAccessException: Error occurred while retrieving user with username 'ssalles'. Stapelüberwachung: [hide] com.atlassian.jira.exception.DataAccessException: Error occurred while retrieving user with username 'ssalles'. at com.atlassian.jira.issue.IssueImpl.getUser(IssueImpl.java:1099) at com.atlassian.jira.issue.IssueImpl.getAssignee(IssueImpl.java:394) at com.atlassian.jira.issue.fields.AssigneeSystemField.populateFromIssue(AssigneeSystemField.java:507) at com.atlassian.jira.issue.fields.screen.FieldScreenRenderLayoutItemImpl.populateFromIssue(FieldScreenRenderLayoutItemImpl.java:85) at com.atlassian.jira.web.action.issue.CommentAssignIssue.doDefault(CommentAssignIssue.java:90) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
dashboard, WARN messages similar like the following https://samebug.io/exceptions/2543105/com.atlassian.jira.exception.DataAccessException/error-occurred-while-retrieving-user-with-username?soft=false will appear in the atlassian-jira.log file: 2012-11-14 20:28:28,913 DirectoryEntryResolverThread-1 WARN kneissl 1228x9693x1 1oi7gfq 79.224.75.250,127.0.0.1 /rest/config/1.0/directory.json [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for http://confluence.zentrale.local/rest/gadgets/1.0/g/com.atlassian.confluence.plugins.gadgets:confluence-page-gadget/gadgets/confluence-page-gadget.xml [......] 2012-11-15 08:41:20,846 error occurred DirectoryEntryResolverThread-3 WARN kneissl 521x10546x1 16p56qy 79.224.94.167,127.0.0.1 /rest/config/1.0/directory.json [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for http://confluence.zentrale.local/rest/gadgets/1.0/g/com.atlassian.confluence.plugins.gadgets:confluence-page-gadget/gadgets/confluence-page-gadget.xml 2015-07-31 11:26:22,904 http-bio-8443-exec-4 WARN admin 686x2875x1 uyftg2 59.167.252.230 /secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for error occurred while rest/gadgets/1.0/g/com.atlassian.jira.ext.calendar:issuescalendar-gadget/templates/plugins/jira/portlets/calendar/gadget/calendar-gadget.xml Diagnosis Check the URL in the warning message is the one you use for Confluence and and returns valid XML. Cause The root cause of this is because previously a Confluence gadget has been added to JIRA Gadget Directory. However at some point, Confluence URL has been changed to new one, and JIRA was not updated with the changes. Hence, JIRA will still try to communicate to Confluence using the old URL, and when the application could not be contacted, the WARN message will appear in the logs file. Resolution We can try to remove the stale gadget
help others com.atlassian.jira.exception.DataAccessException: Error occurred while retrieving user with username 'mabr'. Atlassian JIRA | werner mueller | 6 years ago 0 mark we use JIRA to authenticate users via CROWD. crowd retrieves the users from an ActiveDirectory. when the users is deleted in the active directory it sooner or later 'disappears' from crowd (or the administrator deletes the user in the crowd directory). then the user is no longer availble in jira. so issues assigned to that user cannot be re-assigned or edited. there is a stacktrace screen in the browser. the logs show an entity not found exception: {code} 2011-01-11 10:36:05,371 TP-Processor19 ERROR [500ErrorPage.jsp] Exception caught in 500 page Error occurred while retrieving user with username 'mabr'. com.atlassian.jira.exception.DataAccessException: Error occurred while retrieving user with username 'mabr'. at com.atlassian.jira.issue.IssueImpl.getUser(IssueImpl.java:1124) at com.atlassian.jira.issue.IssueImpl.getAssignee(IssueImpl.java:403) at com.atlassian.jira.issue.IssueImpl.setAssignee(IssueImpl.java:416) at com.atlassian.jira.issue.fields.AssigneeSystemField.updateIssue(AssigneeSystemField.java:231) at com.atlassian.jira.web.action.issue.AssignIssue.doExecute(AssignIssue.java:132) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:171) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46) at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:55) at com.atlassian.plugin.servlet.filter.ServletFilterModuleContainerFilter.doFilter(ServletFilterModuleContainerFilter.java:41) at org.apache.ca