Hi,
I'm tring to upgrade Confluence Server 6.15.9 to 7.4.3, but Confluence stills down after the migration.
What i've tried:
- Upgrade Confluence 6.15.9 to 7.4.3: KO
- Upgrade Confluence 6.15.9 to 7.0.5: It works perfectly
- Upgrade Confluence 7.0.5 to 7.4.3: KO
- Upgrade Confluence 6.15.9 to 7.4.3 with Docker: KO
I have that error on the landing page:
Database: Database connection failed
The database (MSSQL) is up and the configuration is correct.
This error appears in my catalina.out:
20-Aug-2020 09:27:36.244 WARNING [Catalina-utility-3] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [http-nio-8090-exec-1] (id=[39]) has been active for [66,708] milliseconds (since [8/20/20 9:26 AM]) to serve the same request for [http://confluence.mydomain:8080/confluence/] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [1] thread(s) in total that are monitored by this Valve and may be stuck.
java.lang.Throwable
at java.base@11.0.8/java.lang.Object.wait(Native Method)
at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1503)
at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:644)
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:554)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConnectionInUse(C3P0PooledConnectionPool.java:758)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:685)
at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:140)
at net.sf.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:36)
at com.atlassian.hibernate.adapter.adapters.ConnectionProviderV5Adapter.getConnection(ConnectionProviderV5Adapter.java:35)
at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:35)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:99)
at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getPhysicalConnection(LogicalConnectionManagedImpl.java:129)
at org.hibernate.internal.SessionImpl.connection(SessionImpl.java:514)
at com.atlassian.hibernate.adapter.adapters.session.SessionV2Adapter.connection(SessionV2Adapter.java:159)
at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:422)
at com.atlassian.confluence.impl.hibernate.ConfluenceHibernateTransactionManager.doBegin(ConfluenceHibernateTransactionManager.java:41)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:378)
at jdk.internal.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
.
.
.
20-Aug-2020 09:28:16.252 WARNING [Catalina-utility-1] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadCompleted Thread [http-nio-8090-exec-1] (id=[39]) was previously reported to be stuck but has completed. It was active for approximately [98,144] milliseconds.
OS: RHEL 7.8
JAVA: OpenJDK 1.8.0_262-b10
Confluence Server: 6.15.9
MSSQL: 12.0.4100.1
Do you have any suggestions?
Thanks in advance.
I recommend you open a ticket with atlassian support if you are still experiencing this issue: https://support.atlassian.com/contact/#/
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.