2018-02-19 10:05:49,834 C3P0PooledConnectionPoolManager[identityToken->31alg59t187kpw61r3sacz|6a3140aa]-AdminTaskTimer WARN [mchange.v2.async.ThreadPoolAsynchronousRunner] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@98898a0 -- APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
Is this a bug? I only tried to remove a user from a group and the Crowd server appears to have crashed...
Hi, trying to remember as this was a while back. I seem to remember it being caused by the Crowd cache being out of sync with the current configuration.
Try deleting the Crowd cache directory. I think its in .../var/... on Linux and restarting the Crowd server with clean cache.
Also check the ownership of the Crowd cache directory tree, that it matches the user who the Crowd server is running as.
Also beware of running an Atlassian server as a user other than root as you cannot bind to ports 80 or 443 without major headaches
Cheers,
Nathan
Sounds good, lets monitor it for couple of days and then close this topic here.
Best Regards,
Marcin Kempa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @N B
It's hard to tell what is the underlying issue without seeing the complete log and stack traces. But maybe those answers will keep you going forward:
Generally it looks like a problem with resources, and a high load.
Best Regards,
Marcin Kempa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.