The Custom Query mappers modules are not getting loaded once the server is restarted.

This is causing a serious problem in Ad hoc Workflows. The workaround is manually reloading the lucene-query-mapper modules.

Recreating the problem:

• When the plugin containing the lucene-query-mapper modules is installed, no problem, everything works
• When the server is restarted, trying to access the query causes an exception like this one:

  com.atlassian.confluence.search.v2.lucene.LuceneMapperNotFoundException: A lucene mapper could not be found to map an object of type: com.atlassian.confluence.search.v2.SearchQuery and key: workflowassignee
          at com.atlassian.confluence.search.v2.lucene.DelegatingLuceneSearchMapper.convertToLuceneQuery(DelegatingLuceneSearchMapper.java:28)
          at com.atlassian.confluence.search.v2.lucene.mapper.BooleanQueryMapper.addSubQueries(BooleanQueryMapper.java:43)
          at com.atlassian.confluence.search.v2.lucene.mapper.BooleanQueryMapper.convertToLuceneQuery(BooleanQueryMapper.java:29)
          at com.atlassian.confluence.search.v2.lucene.DelegatingLuceneSearchMapper.convertToLuceneQuery(DelegatingLuceneSearchMapper.java:30)
          at com.comalatech.confluence.workflowreports.TwoPointNineWorkflowReportCreator.debugQuery(TwoPointNineWorkflowReportCreator.java:138)
          at com.comalatech.confluence.workflowreports.TwoPointNineWorkflowReportCreator.makeEntries(TwoPointNineWorkflowReportCreator.java:131)
          at com.comalatech.confluence.workflowreports.TwoPointNineWorkflowReportCreator.createDashboardReport(TwoPointNineWorkflowReportCreator.java:78)
  

Please note that this is a confluence issue, which happens to have an effect in Ad hoc Workflows