Details
-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When JIRA is connected with Crowd and Crowd fails during the time that a user is using Confluence, the following stacktrace is displayed :
com.atlassian.crowd.exception.runtime.CommunicationException at com.atlassian.crowd.embedded.core.CrowdServiceImpl.convertOperationFailedException(CrowdServiceImpl.java:866) at com.atlassian.crowd.embedded.core.CrowdServiceImpl.authenticate(CrowdServiceImpl.java:79) at com.atlassian.crowd.embedded.core.DelegatingCrowdService.authenticate(DelegatingCrowdService.java:35) at com.atlassian.crowd.embedded.core.FilteredCrowdServiceImpl.authenticate(FilteredCrowdServiceImpl.java:51) at com.atlassian.jira.security.login.LoginManagerImpl$InternalStaticDependencies.authenticate(LoginManagerImpl.java:415)
Steps to reproduce :
- Integrate JIRA with Crowd
- Login to JIRA with a user from Crowd
- Shutdown Crowd
- Try to perform some action on JIRA.
JIRA should catch the Crowd exception in a better way and communicate to the user that the Crowd server is no longer accessible.
Diagnosis and Resolution
Please follow the diagnosis and resolution steps from the knowledge base article JIRA drops LDAP configuration - java.naming.provider.url property does not contain a URL.
Attachments
Issue Links
- is cloned from
-
CONFSERVER-29655 Confluence should catch Crowd failures gracefully
- Closed
- relates to
-
JRASERVER-40291 Jira should not remove directory configuration during sync to avoid the possibilty that the configuration isn't properly written back
- Closed
-
JRACLOUD-33521 JIRA should catch Crowd failures gracefully
- Closed