Hi
While it has never turned out to be an actual problem, whenever we restart Bitbucket, a lot of the following error statements appear in the log:
ERROR [http-nio-7990-exec-4] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
This was always the case with older Bitbucket versions and I hoped they might disappear after migrating to a docker-compose deployment and the latest LTS 7.21.8, but these ERROR statements still appear.
What's the problem behind this? Is there any way to fix it?
Regards
Dominik
PS: some more output after a service restart:
Starting Bitbucket webapp at http://localhost:7990
2023-01-24 12:15:50,034 INFO [main] c.a.b.i.b.BitbucketServerApplication Starting BitbucketServerApplication v7.21.8 using Java 11.0.17 on 89f3b628cd85 with PID 63 (/opt/atlassian/bitbucket/app/WEB-INF/classes started by bitbucket in /var/atlassian/application-data/bitbucket)
2023-01-24 12:15:50,039 INFO [main] c.a.b.i.b.BitbucketServerApplication No active profile set, falling back to 1 default profile: "default"
2023-01-24 12:15:51,509 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Starting Bitbucket 7.21.8 (820bd98 built on Thu Jan 19 12:52:42 CET 2023)
2023-01-24 12:15:51,509 INFO [main] c.a.b.i.boot.log.BuildInfoLogger JVM: Eclipse Adoptium OpenJDK 64-Bit Server VM 11.0.17+8
2023-01-24 12:15:53,312 INFO [main] c.a.b.i.b.BitbucketServerApplication Started BitbucketServerApplication in 5.005 seconds (JVM running for 6.04)
2023-01-24 12:15:58,641 INFO [spring-startup] c.a.s.internal.home.HomeLockAcquirer Successfully acquired lock on home directory /var/atlassian/application-data/bitbucket
2023-01-24 12:15:58,656 INFO [spring-startup] c.a.s.internal.home.HomeValidator Upgrading Bitbucket from 7.21.5 to 7.21.8
2023-01-24 12:15:59,837 ERROR [http-nio-7990-exec-4] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:02,565 ERROR [http-nio-7990-exec-5] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:14,866 ERROR [http-nio-7990-exec-5] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:15,100 INFO [spring-startup] c.a.s.internal.home.HomeLockAcquirer Successfully acquired lock on home directory /var/atlassian/application-data/bitbucket/shared
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.hazelcast.internal.networking.nio.SelectorOptimizer (file:/opt/atlassian/bitbucket/app/WEB-INF/lib/hazelcast-3.12.13.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
WARNING: Please consider reporting this to the maintainers of com.hazelcast.internal.networking.nio.SelectorOptimizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
2023-01-24 12:16:17,192 WARN [spring-startup] com.hazelcast.instance.Node [10.89.0.5]:5701 [bitbucket] [3.12.13] No join method is enabled! Starting standalone.
2023-01-24 12:16:17,601 ERROR [http-nio-7990-exec-6] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:29,803 ERROR [http-nio-7990-exec-8] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:32,565 ERROR [http-nio-7990-exec-10] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:44,790 ERROR [http-nio-7990-exec-7] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:47,559 ERROR [http-nio-7990-exec-9] c.a.p.s.ServletModuleContainerServlet Could not get ServletModuleManager?
2023-01-24 12:16:47,941 INFO [spring-startup] c.a.s.i.hook.DefaultHookService Hook callback socket listening on 127.0.0.1:36325
2023-01-24 12:16:50,537 INFO [spring-startup] c.a.s.i.s.g.t.DefaultTranscodeServer Callback socket listening at 127.0.0.1:36963
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.