New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-2651
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Owen Fellows
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

"Could not add permission: ... it already existed?" warning on startup

Created: 11/Nov/03 03:23 PM   Updated: 30/Jul/06 07:36 PM
Component/s: None
Affects Version/s: 2.5 Pro, 2.5 Enterprise
Fix Version/s: 3.0 Pro Preview

Time Tracking:
Not Specified

Participants: Jeff Turner [Atlassian] and Owen Fellows
Since last comment: 4 years, 9 weeks, 4 days ago
Resolution Date: 24/Jun/04 09:54 AM
Labels:


 Description  « Hide
Some people are getting warnings on startup:

2003-11-10 16:04:10,843 WARN [atlassian.jira.security.PermissionsCache] Could not add permission Permission:
[type=22][scheme=null][group=etg-administrators][permType=group] - it already existed?

It doesn't appear to cause problems, but is probably a symptom of something that needs fixing.

Data donations to support@ from people experiencing this welcome



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Owen Fellows added a comment - 24/Jun/04 09:54 AM
Added an integrity checker so users with this problem can remove the unwanted permissions.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13_beta1-#328) - Bug/feature request - Atlassian news - Contact Administrators