Repository paused due to error

Repository paused due to error

org.hibernate.exception.GenericJDBCException: Cannot open connection

java.sql.SQLException: com.mchange.v2.c3p0.PoolBackedDataSource@dc007ae6 connectionPoolDataSource -> com.mchange.v2.c3p0.WrapperConnectionPoolDataSource@b7847691 acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, debugUnreturnedConnectionStackTraces -> false, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 2rxmf28ob7dno0o1la7y|318e45a8, idleConnectionTestPeriod -> 0, initialPoolSize -> 5, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 1800, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 20, maxStatements -> 50, maxStatementsPerConnection -> 0, minPoolSize -> 5, nestedDataSource -> com.mchange.v2.c3p0.DriverManagerDataSource@c79963d6 description -> null, driverClass -> null, factoryClassLocation -> null, identityToken -> 2rxmf28ob7dno0o1la7y|55ea0024, jdbcUrl -> jdbc:hsqldb:file:/jira01/atlassian/FishEye/fecru-2.7.10/var/data/crudb/crucible, properties -> {user=******, password=******, autocommit=false} , preferredTestQuery -> null, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false; userOverrides: {} , dataSourceName -> null, factoryClassLocation -> null, identityToken -> 2rxmf28ob7dno0o1la7y|7fd3510d, numHelperThreads -> 3 has been closed() -- you can no longer use it.

1 answer

0 votes

I think we'd need to see a stacktrace to understand the context of this error fully. FishEye indexing does not use the SQL database so there is a chance that the repository being paused is not related to the JDBC error you have posted.

I recommend you open a support case on https://support.atlassian.com to explore this issue. The best thing would be to turn on DEBUG logging and capture logs around the problem.

Thanks Conor. Do we must need to create a new data directory for fisheye or can we set bydefault installation directory?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

482 views 0 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you