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
I m getting this error repetedly and cannot get it to work. It worked at the beginning but it stoped to work. I did try to disable and enable back the plugin, restart de server and I end up getting the same issue after some time.
At this time within the plugin's configuration page, I can only see a "beautifull" and long stack trace so my only option right now is to restart the whole server but since I have don this earlier I know that reindexing will keep working forever and finally an error similiar to this one will be raised.
I'm currently working with Jira v6.
Help will be appreciated!
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!
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:174) at com.kintosoft.svnwebclient.db.PluginConnectionPool.getProperty(PluginConnectionPool.java:381)
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.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 :-(.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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!
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