-
Bug
-
Resolution: Fixed
-
High
-
5.4.2
-
None
On a brand new installation or upgraded instance, the plugin Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.atlassian-oauth-service-provider-plugin) fail to start with the following stacktrace:
2014-01-28 13:13:30,705 WARN [Timer-4] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] timeout Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.oauth.atlassian-oauth-service-provider-plugin, config=osgibundle:/META-INF/spring/*.xml)]
2014-01-28 13:13:30,708 ERROR [Timer-4] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] fail Unable to create application context for [com.atlassian.oauth.atlassian-oauth-service-provider-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.sal.api.auth.OAuthRequestVerifierFactory)] (from bean [&oAuthRequestVerifierFactory])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.oauth.atlassian-oauth-service-provider-plugin' has timed out
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
2014-01-28 13:13:30,709 ERROR [Timer-4] [plugin.osgi.factory.OsgiPlugin] logAndClearOustandingDependencies Never resolved service '&oAuthRequestVerifierFactory' for plugin 'com.atlassian.oauth.serviceprovider' with filter (objectClass=com.atlassian.sal.api.auth.OAuthRequestVerifierFactory)
2014-01-28 13:13:30,710 ERROR [Timer-4] [plugin.osgi.factory.OsgiPlugin] onPluginContainerFailed Unable to start the plugin container for plugin com.atlassian.oauth.serviceprovider
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.oauth.atlassian-oauth-service-provider-plugin' has timed out
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
As a consequence, OAuth authentication does not work in the application links.
This has been reproduced with the timeout set to 5 minutes (-Datlassian.plugins.enable.wait=300)
- is blocked by
-
CRUC-990 Create a review with multiple revisions of the same file or add multiple revisions of the same file via the manage files tab.
- Closed
- relates to
-
-
- Closed
-
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-32397] OAuth Plugin cannot be enabled on startup
Chris Johnson
added a comment - We are hitting this bug in 5.4.2 also, will be moving to 5.4.3 this weekend. What's the impact when we see these errors?
Chris Johnson
added a comment - We are hitting this bug in 5.4.2 also, will be moving to 5.4.3 this weekend. What's the impact when we see these errors? 
Daniel Reichelt
added a comment - Muhammad Rizki from Atlassian Support Team pointed me to this bug report and suggested to change from OAuth to "Trusted" or "Basic" authentification. This is a workaround I can live with at them moment.
Daniel Reichelt
added a comment - Muhammad Rizki from Atlassian Support Team pointed me to this bug report and suggested to change from OAuth to "Trusted" or "Basic" authentification. This is a workaround I can live with at them moment. 
Devu Heda
added a comment - When can we get this ...? We are completely stuck at this point of time This defect does not only affect new installs. It also affects upgrades (for me, this was from v5.3.1).
Hi Borre.
Please note that making the timeout 300 was only a test to prove this wasn't a timing issue. It does not solve the problem. I recommend you to set the old value back and if you find a problem, please open a ticket with Atlassian Support.
Hi Alex!
We are not able to get Confluence in service...
I tried to set the timeout to 300, and after that i'm not able to access Confluence.
I have also tried to remove the timeout setting, but stil not able to access,
Getting alot of this messages in my log:
--------------------------------------------------------
2014-01-31 09:58:54,426 WARN [ListenableFutureAdapter-thread-10] [atlassian.activeobjects.osgi.ActiveObjectsServiceFactory] apply Resubmitting AO bundle with longer timeout 180000 ms for bundle : com.atlassian.plugins.atlassian-nav-links-plugin [144]
2014-01-31 09:59:24,425 WARN [active-objects-ddl-0] [atlassian.activeobjects.osgi.AOConfigurationServiceProviderImpl] getAndWait Timeout (30000 MILLISECONDS) waiting for ActiveObjectConfiguration for Bundle : com.atlassian.confluence.plugins.confluence-jira-metadata [66].
To avoid this warning add an ao configuration module to your plugin
2014-01-31 09:59:24,426 WARN [active-objects-ddl-0] [atlassian.activeobjects.osgi.AOConfigurationServiceProviderImpl] getConfiguration Didn't find any configuration service for bundle com.atlassian.confluence.plugins.confluence-jira-metadata nor any entities scanning for default AO packages.
2014-01-31 09:59:24,427 WARN [ListenableFutureAdapter-thread-11] [atlassian.activeobjects.osgi.ActiveObjectsServiceFactory] apply Resubmitting AO bundle with longer timeout 180000 ms for bundle : com.atlassian.confluence.plugins.confluence-jira-metadata [66]
2014-01-31 09:59:54,427 WARN [active-objects-ddl-0] [atlassian.activeobjects.osgi.AOConfigurationServiceProviderImpl] getAndWait Timeout (30000 MILLISECONDS) waiting for ActiveObjectConfiguration for Bundle : com.atlassian.confluence.plugins.confluence-jira-content [65].
To avoid this warning add an ao configuration module to your plugin
2014-01-31 09:59:54,428 WARN [active-objects-ddl-0] [atlassian.activeobjects.osgi.AOConfigurationServiceProviderImpl] getConfiguration Didn't find any configuration service for bundle com.atlassian.confluence.plugins.confluence-jira-content nor any entities scanning for default AO packages.
2014-01-31 09:59:54,431 WARN [ListenableFutureAdapter-thread-12] [atlassian.activeobjects.osgi.ActiveObjectsServiceFactory] apply Resubmitting AO bundle with longer timeout 180000 ms for bundle : com.atlassian.confluence.plugins.confluence-jira-content [65]
Hello Borre.
Confluence 5.4.3 should be released in the next weeks. This bug is probably also present in Confluence 5.4 so I do not recommend you to downgrade.
Hello cjoh44.
This bug would only affect you if you have an application link set up between Confluence and another application and the authentication mechanism is OAuth.
In any other case, this bug should not affect you, even though the error will appear in the logs every time you start Confluence.