Unable to create pull request after Bitbucket upgrade
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
Learn why you are unable to create a pull request after a Bitbucket upgrade, with error “An error occurred while processing the request. Check the server logs for more information.”
Diagnosis
"Could not initialize class"
The following error is observed in the Bitbucket logs:
2025-04-14 14:27:09,179 ERROR [http-nio-7990-exec-1] wolfi @1RR66FDx867x618x3 keswih 192.168.200.109,127.0.0.1 "GET /rest/ui/latest/projects/TEST/repos/bitbuckettest/pull-requests/5/merge HTTP/1.1" c.a.p.r.v.e.ThrowableExceptionMapper Uncaught exception 1d2e6932-1f1f-4221-ba68-f96610c85b71 thrown by REST service: Could not initialize class com.bitbooster.hook.Config
java.lang.NoClassDefFoundError: Could not initialize class com.bitbooster.hook.Config
at com.bitbooster.hook.ControlFreakHook.isHookEnabled(ControlFreakHook.java:1340)
at com.bitbooster.hook.ControlFreakHook.check(ControlFreakHook.java:805)
at com.bitbooster.hook.ControlFreakHook.preUpdate(ControlFreakHook.java:301)
at com.bitbooster.hook.ControlFreakHook.preUpdate(ControlFreakHook.java:201)
at com.atlassian.stash.internal.hook.repository.DefaultRepositoryHookService.preUpdate(Def
In this case, the error points to the class com.bitbooster.hook.Config, which is related to the third-party app Control Freak (the app vendor is Bit-booster Software).
Cause
The app is incompatible with the Bitbucket version
The app is incompatible with your current version of Bitbucket, causing the error.
Solution
Upgrade or disable the app
To resolve the problem, you will need to either upgrade the app to a compatible version or disable it.
Was this helpful?