Emoticons doesn't work while replying to a comment in a pull request in Bitbucket Server
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Emoticons doesn't work while replying to a comment in a pull request.
Environment
Bitbucket 7.10.1
Diagnosis
The plugin (com.atlassian.bitbucket.server.bitbucket-comment-likes) that handles the emoticons is Disabled.
1
2
3
4
5
6
7
8
9
10
<plugin>
<key>com.atlassian.bitbucket.server.bitbucket-comment-likes</key>
<name>Bitbucket Server - Comment Likes</name>
<version>7.10.1</version>
<vendor>Atlassian</vendor>
<status>DISABLED</status>
<vendor-url>https://www.atlassian.com</vendor-url>
<framework-version>2</framework-version>
<bundled>Bundled</bundled>
</plugin>
Cause
The reason behind the plugin being disabled in timeout. Application context initialization for 'com.atlassian.bitbucket.server.bitbucket-comment-likes' times out waiting for (objectClass=com.atlassian.bitbucket.emoticons.EmoticonService).
1
2
3
4
5
6
7
ERROR [Spring DM Context Creation Timer] c.a.plugin.osgi.factory.OsgiPlugin Unable to start the plugin container for plugin 'com.atlassian.bitbucket.server.bitbucket-comment-likes'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.bitbucket.server.bitbucket-comment-likes' has timed out waiting for (objectClass=com.atlassian.bitbucket.emoticons.EmoticonService)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
By default, Bitbucket waits for 60 seconds for install/enabling the plugins post which it times out.Plugin startup time-out:60 seconds (default), increasing plugin timeout to a higher value might help solve the timeout issue.
Workaround
If you enable the plugin you should see the functionality return. Please read the following KB to learn know more about Enabling plugins
Solution
Increase plugin timeout parameter from 60 seconds to 300 seconds by setting JVM start up arguments in Bitbucket.
Steps:
Navigate to$BITBUCKET_INSTALLATION_DIR/bin/_start-webapp.sh
Add following parameter to JVM_SUPPORT_RECOMMENDED_ARGS in
_start-webapp.shand save it1JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.plugins.enable.wait=300"Restart your Bitbucket server nodes.
Was this helpful?