Getting java.sql.SQLException: Login timeout

Question

Installed this Subversion ALM plugin yesterday on a repo with 300K+ revisions.

Today when i access the config page, it fails with:

/secure/ViewSubversionRepositories.jspa [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.sql.SQLException: Login timeout
java.sql.SQLException: Login timeout
        at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208)
        at com.kintosoft.svnwebclient.db.PluginConnectionPool.getConnection(PluginConnectionPool.java:191)
        at com.kintosoft.svnwebclient.db.PluginConnectionPool.getConnection(PluginConnectionPool.java:202)

Any advice?

/Bjarte

Guillermo López · Answer

I'd say this is not related to Jira database but to subversion alm h2 database. Look at the "h2" package within the exception:

Caused by: java.sql.SQLException: Login timeout at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:208) 
at com.kintosoft.svnwebclient.db.PluginConnectionPool.getConnection(PluginConnectionPool.java:163) 
at com.kintosoft.svnwebclient.db.PluginConnectionPool.getConnection(PluginConnectionPool.java:174) at com.kintosoft.svnwebclient.db.PluginConnectionPool.getProperty(PluginConnectionPool.java:381) 
at com.kintosoft.jira.plugin.ext.subversion.action.ViewSubversionRepositoriesAction.getAgree(ViewSubversionRepositoriesAction.java:107) 
at sun.reflect.GeneratedMethodAccessor667.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.runtime.parser.node.PropertyExecutor.execute(PropertyExecutor.java:142) 
at org.apache.velocity.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:525) 
at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:198) ... 189 more

I've restarted Jira today and I have not gotten the error so far however the repository keeps stating "Index progress: 8536 / 8728" and it seems it does not goes forward after I've ran manually the index process :-(.

Guillermo López · Answer

The stack is a bit long to paste it here. Is there anyway I can send it to you? I'll do it next Monday.

Thanks for your help!!!

Giuliano C. · Answer

Heya Guillermo, Would you be able to provide us some details on the stack trace given, if is not the same for the SQL long queries again? Otherwise, can you confirm if the transaction level is set to transaction-isolation = READ-COMMITTED? We can get more information throhgh this KB article: https://confluence.atlassian.com/display/JIRAKB/JIRA+MySQL+Usage+Fails+With+Error+-+java.sql.BatchUpdateException+Lock+wait+timeout+exceeded Hope it helps ya! Cheers, Giu