xan/awips2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

remove geospatial cron firing now that warngen geometries are pre-generated

Browse source
This commit is contained in:
mjames-upc 2017-06-25 15:41:59 -06:00
parent 47a69a149f
commit c84990d571
2 changed files with 0 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
edexOsgi/com.raytheon.edex.plugin.warning/res/spring/warning-request.xml
View file

@ -42,8 +42,6 @@
<camelContext id="geospatialDataGenerator-camel"
xmlns="http://camel.apache.org/schema/spring"
errorHandlerRef="errorHandler">
<endpoint id="geospatialDataUpdaterCron"
uri="clusteredquartz://warning/checkGeospatialData/?cron=${geospatial.updater.cron}" />
<!-- Generate once on context start -->
<route id="geospatialDataGeneratorRoute">
@ -51,19 +49,6 @@
<bean ref="geospatialDataGenerator" method="generateUniqueGeospatialMetadataGeometries"/>
</route>
<!-- check generate periodically -->
<route id="geospatialDataUpdaterRoute">
<from ref="geospatialDataUpdaterCron"/>
<doTry>
<bean ref="geospatialDataGenerator" method="generateUniqueGeospatialMetadataGeometries"/>
<doCatch>
<exception>java.lang.Throwable</exception>
<to
uri="log:geospatialDataUpdater?level=ERROR" />
</doCatch>
</doTry>
</route>
<!-- Route to send geospatial data update notification -->
<route id="geospatialUpdateNotify">
<from uri="vm:edex.geospatialUpdateNotification" />

6
edexOsgi/com.raytheon.edex.plugin.warning/resources/warning.properties
View file

@ -1,6 +0,0 @@
# Schedule for checking/updating warngen geometries
geospatial.updater.cron=0+0+0/1+*+*+?
# Maximum number of threads to determine a site's features geometry.
#geospatial.geometry.threads=5