Attempting to delete repository causes 500 Error ("A database error has occurred")

[chrisssc]

After trying to delete a reasonably large repository (~1GB) from the web interface, the connection hangs, and when attempting to access it again Bitbucket gives a 500 Error.

Looking at the log shows the following:

2018-06-27 15:20:49,449 WARN [Navlink Plugin Executor:thread-11] o.h.e.jdbc.spi.SqlExceptionHelper SQL Error: 0, SQLState: null
2018-06-27 15:20:49,450 ERROR [Navlink Plugin Executor:thread-11] o.h.e.jdbc.spi.SqlExceptionHelper bitbucket - Connection is not available, request timed out after 15001ms.
2018-06-27 15:21:04,458 WARN [Navlink Plugin Executor:thread-11] o.h.e.jdbc.spi.SqlExceptionHelper SQL Error: 0, SQLState: null
2018-06-27 15:21:04,458 ERROR [Navlink Plugin Executor:thread-11] o.h.e.jdbc.spi.SqlExceptionHelper bitbucket - Connection is not available, request timed out after 15001ms.

Restarting fixes the hang, but the repository has not been deleted.

[Caterina Curti]

Hi @chrisssc,

The logs don't seem related to a problem deleting a repository.

It seems that either the database was not available at that time or Bitbucket Server could not connect (maybe a network problem)?

This also seems to be confirmed by the fact that a restart of Bitbucket Server was required.

If you are still able to reproduce the issue, please enable the debug log in Bitbucket Server (Go to "Bitbucket Server Administration > Logging and profiling" and click to check/enable the "Enable debug logging" option) and share here the full stack trace as available in the $BITBUCKET_HOME/log/atlassian-bitbucket.log.

Cheers,

Caterina - Atlassian