You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi everyone
We unsuddenly have the following error when trying to login to JIRA (Jira Server 7.3.1 ):
Sorry, a communication error occurred while trying to contact the remote authentication server.
Although crowd works well. Authorization in Confluence works. And we can't authorize to JIRA as local user too. We tried to reboot JIRA few times. Nothing changed.
atlassian-jira.log:
2021-01-20 09:59:01,079 JIRA-Bootstrap ERROR [c.a.s.core.lifecycle.DefaultLifecycleManager] LifecycleAware.onStart() failed for component with class 'com.atlassian.oauth.serviceprovider.internal.ExpiredSessionRemoverScheduler' from
plugin 'com.atlassian.oauth.serviceprovider'
java.lang.IllegalArgumentException: Job handler already registered: Service Provider Session Remover
at com.atlassian.scheduler.compat.clustered.ClusteredCompatibilityPluginScheduler.registerJobHandler(ClusteredCompatibilityPluginScheduler.java:80)
at com.atlassian.scheduler.compat.AutoDetectingCompatibilityPluginScheduler.registerJobHandler(AutoDetectingCompatibilityPluginScheduler.java:64)
at com.atlassian.oauth.serviceprovider.internal.ExpiredSessionRemoverScheduler.onStart(ExpiredSessionRemoverScheduler.java:35)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(DefaultLifecycleManager.java:277)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(DefaultLifecycleManager.java:274)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecyleAware(DefaultLifecycleManager.java:303)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyOnStartIfStartedAndEnabled(DefaultLifecycleManager.java:273)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.access$300(DefaultLifecycleManager.java:49)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(DefaultLifecycleManager.java:235)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(DefaultLifecycleManager.java:232)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecycleAwares(DefaultLifecycleManager.java:258)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyStartableLifecycleAwares(DefaultLifecycleManager.java:231)
at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.onPluginEnabled(DefaultLifecycleManager.java:161)
... 2 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48)
at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:107)
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160)
at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79)
at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:73)
at com.atlassian.plugin.manager.DefaultPluginManager.broadcastIgnoreError(DefaultPluginManager.java:2122)
at com.atlassian.plugin.manager.DefaultPluginManager.onPluginRefresh(DefaultPluginManager.java:795)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
Please help us in resolving this.
Hi @N,
Unfortunately, the error that you have provided has nothing to do with the user authentication mechanism in Jira.
You should retrieve your local Jira Admin user account first and then troubleshoot the problem with the connection to the Crowd server. You may refer to Retrieving the JIRA Administrator.
I hope that this helps.
Thanks,
Moga
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.