fixed bug that release the connection to the poll two times and makes the pool in an inconsistency status
This commit is contained in:
parent
dbe6d76c59
commit
dab357e82d
|
@ -163,7 +163,6 @@ public class ScholixIndexManager {
|
|||
final SearchHits<ScholixFlat> hits = client.search(searchQuery, ScholixFlat.class, IndexCoordinates.of(elasticSearchProperties.getIndexName()));
|
||||
|
||||
final Aggregations aggregations = hits.getAggregations();
|
||||
connectionPool.returnResource(resource);
|
||||
if (aggregations == null)
|
||||
return null;
|
||||
|
||||
|
|
2
pom.xml
2
pom.xml
|
@ -453,7 +453,7 @@
|
|||
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
|
||||
<maven.compiler.plugin.version>3.6.0</maven.compiler.plugin.version>
|
||||
<java.version>1.8</java.version>
|
||||
<dhp-schemas-version>3.16.1-SNAPSHOT</dhp-schemas-version>
|
||||
<dhp-schemas-version>3.17.2-FLAT-SNAPSHOT</dhp-schemas-version>
|
||||
<apache.solr.version>7.1.0</apache.solr.version>
|
||||
<mongodb.driver.version>3.4.2</mongodb.driver.version>
|
||||
<prometheus.version>0.10.0</prometheus.version>
|
||||
|
|
Loading…
Reference in New Issue