We had our Confluence and Jira Server running on Windows. We migrated our VM between servers. Now Jira runs, but Confluence does not. This VM migration would result in a CPU ID change. Would this cause a licensing issue or some other reason why Confluence won't run.
Log file entries include:
2021-01-26 00:49:14,403 WARN [C3P0PooledConnectionPoolManager[identityToken->1hge32vafgcfr9n1hi52b1|52d4675]-HelperThread-#2] [mchange.v2.resourcepool.BasicResourcePool] log com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@5c6129a0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
org.h2.jdbc.JdbcSQLException: General error: "java.lang.NullPointerException" [50000-196]
Caused by: java.lang.NullPointerException
2021-01-26 00:49:14,403 WARN [C3P0PooledConnectionPoolManager[identityToken->1hge32vafgcfr9n1hi52b1|52d4675]-HelperThread-#2] [mchange.v2.resourcepool.BasicResourcePool] log Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@4508c9db is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
2021-01-26 00:59:56,150 INFO [Catalina-utility-2] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.13.10 [build 7901 based on commit hash abf7b35644d5a5d1d7e4b0969a83e8eb2b569fb5] - synchrony version 2.1.0-release-confluence_6.13-84328589
2021-01-26 01:00:15,425 INFO [Catalina-utility-2] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization started
2021-01-26 01:00:28,675 INFO [Catalina-utility-2] [com.atlassian.confluence.lifecycle] <init> Loading EhCache cache manager
2021-01-26 01:01:40,361 INFO [Catalina-utility-2] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 84936 ms
There's a bit of an essay on what database pooling is, but the short version of it is that a connection can only handle a certain number of channels talking to the database at a time, and Confluence is trying to go over that and it is failing.
You are using the internal embedded database, h2, which is not supported and only suitable for demo or short-lived dev/test systems.
I don't know how to fix a pooling problem with h2, I've always shrugged, reverted to the previous system, and then rigged up a supported database and re-migrated/upgraded. I think this is probably what you need to do - go find the last backup, and rebuild a system on a supported database from it.
Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond. A long time favorite, Team Cale...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events