Stash does not understand Crowd's nested groups


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( ~[crowd-api-2.6.2-m1.jar:na]
        at ~[crowd-core-2.6.2-m1.jar:na]
        at ~[crowd-ldap-2.6.2-m1.jar:na]
        at ~[crowd-ldap-2.6.2-m1.jar:na]
        at ~[crowd-ldap-2.6.2-m1.jar:na]
        at ~[crowd-core-2.6.2-m1.jar:na]
        at ~[crowd-core-2.6.2-m1.jar:na]
        at ~[crowd-core-2.6.2-m1.jar:na]
        at [crowd-core-2.6.2-m1.jar:na]
        at org.springframework.scheduling.quartz.QuartzJobBean.execute( [spring-context-support-3.2.1.RELEASE.jar:3.2.1.RELEASE]
        at [quartz-1.8.6.jar:na]
        at org.quartz.simpl.SimpleThreadPool$ [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

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 for it. Please 'watch' the issue to keep track of our progress in resolving the issue.


Hights, thanks for raising a ticket for it.

Suggest an answer

Log in or Join to answer
Community showcase
Alexey Matveev
Published Saturday in Jira

How to run Jira in a docker container

Everything below is tested on Ubuntu 17.10. I prefer to use Jira in a docker container because: 1. I can install Jira with a couple of commands. 2. I can start and stop Jira just by starting and s...

113 views 2 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot