Hello
It happened again... 2 years later (QB 8.20).
After deleting a configuration, the server logged this exception:
2019-08-01 16:51:08,989 [qtp1141797772-8570018] ERROR com.pmease.quickbuild.web.WicketConfig - Error handling wicket request.
org.apache.wicket.WicketRuntimeException: Method onLinkClicked of interface org.apache.wicket.markup.html.link.ILinkListener targeted at [ [Component id = deleteConfiguration]] on component [ [Component id = deleteConfiguration]] threw an exception
at org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:282)
at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:220)
at org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:179)
at org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:165)
2019-08-01 16:51:08,992 [qtp1141797772-8570018] WARN com.mchange.v2.c3p0.impl.NewPooledConnection - [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
2019-08-01 16:51:08,997 [qtp1141797772-8570018] WARN com.mchange.v2.c3p0.impl.NewPooledConnection - [c3p0] Another error has occurred [ java.sql.SQLNonTransientConnectionException: (conn=43188288) Connection is closed ] which will not be reported to listeners!
java.sql.SQLNonTransientConnectionException: (conn=43188288) Connection is closed
at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.get(ExceptionMapper.java:234)
at org.mariadb.jdbc.internal.util.exceptions.ExceptionMapper.getException(ExceptionMapper.java:165)
at org.mariadb.jdbc.MariaDbStatement.executeExceptionEpilogue(MariaDbStatement.java:238)
at org.mariadb.jdbc.MariaDbPreparedStatementClient.executeInternal(MariaDbPreparedStatementClient.java:232)
After this exception the configuration was still present in the tree and the user had to delete it again.
From that moment, many builds anywhere in QB started failing with the error "could not extract ResultSet" and we had to restart the server to fix the issue.
We have checked our DB's integrity and everything is ok.
It's not the first time we have a problem after deleting a configuration and each time we have to restart the server.
Here are the server logs with callstacks. Hope it'll help.
log1
log2
Thank you
Mathieu