Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,075
Community Members
 
Community Events
176
Community Groups

Stash does not understand Crowd's nested groups

Hi,

I have a Stash installation linked to Crowd (linked to Active Directory with nested groups enabled)

It looks like Stash does not understand nested group even if the related checkbox is enabled.

At the end of the sync the error message is "Synchronisation failed. See server logs for details."

The log file says:

2013-03-28 14:46:06,385 ERROR [scheduler_Worker-8]  c.a.c.d.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory [ 425985 ].
java.lang.IllegalArgumentException: can't parse argument number: 672ad2a4-ced0-43f8-aa51-d0560057675a
        at java.text.MessageFormat.makeFormat(Unknown Source) ~[na:1.7.0_17]
        at java.text.MessageFormat.applyPattern(Unknown Source) ~[na:1.7.0_17]
        at java.text.MessageFormat.<init>(Unknown Source) ~[na:1.7.0_17]
        at java.text.MessageFormat.format(Unknown Source) ~[na:1.7.0_17]
        at com.atlassian.crowd.util.TimedOperation.complete(TimedOperation.java:18) ~[crowd-api-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations.syncUserMembersForGroup(DirectoryCacheImplUsingChangeOperations.java:124) ~[crowd-core-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:145) ~[crowd-ldap-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:84) ~[crowd-ldap-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.ldap.cache.EventTokenChangedCacheRefresher.synchroniseAll(EventTokenChangedCacheRefresher.java:59) ~[crowd-ldap-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:622) ~[crowd-core-2.6.2-m1.jar:na]
        at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63) ~[crowd-core-2.6.2-m1.jar:na]
        at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50) ~[crowd-core-2.6.2-m1.jar:na]
        at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJobBean.executeInternal(DirectoryPollerJobBean.java:29) [crowd-core-2.6.2-m1.jar:na]
        at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:113) [spring-context-support-3.2.1.RELEASE.jar:3.2.1.RELEASE]
        at org.quartz.core.JobRunShell.run(JobRunShell.java:223) [quartz-1.8.6.jar:na]
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549) [quartz-1.8.6.jar:na]
Caused by: java.lang.NumberFormatException: For input string: "672ad2a4-ced0-43f8-aa51-d0560057675a"
        at java.lang.NumberFormatException.forInputString(Unknown Source) ~[na:1.7.0_17]
        at java.lang.Integer.parseInt(Unknown Source) ~[na:1.7.0_17]
        at java.lang.Integer.parseInt(Unknown Source) ~[na:1.7.0_17]
        ... 16 common frames omitted


How to make all these things work together?

1 answer

1 accepted

2 votes
Answer accepted

Hi Samuel,

Unfortunately, you've hit a bug that is triggered by a group name containing the { and } characters ({672ad2a4-ced0-43f8-aa51-d0560057675a}). This groupname triggers the system to try and format a log message incorrectly.

I've raised https://jira.atlassian.com/browse/CWD-3241 for it. Please 'watch' the issue to keep track of our progress in resolving the issue.

Michael

Hights, thanks for raising a ticket for it.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events