You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by de...@apache.org on 2015/12/16 22:06:07 UTC

svn commit: r1720453 - /uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties

Author: degenaro
Date: Wed Dec 16 21:06:07 2015
New Revision: 1720453

URL: http://svn.apache.org/viewvc?rev=1720453&view=rev
Log:
UIMA-4711 DUCC fix typos in default.ducc.properties

Modified:
    uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties

Modified: uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties
URL: http://svn.apache.org/viewvc/uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties?rev=1720453&r1=1720452&r2=1720453&view=diff
==============================================================================
--- uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties (original)
+++ uima/sandbox/uima-ducc/trunk/src/main/resources/default.ducc.properties Wed Dec 16 21:06:07 2015
@@ -20,7 +20,7 @@
 # WARNING: DO NOT EDIT THIS FILE.
 # All customizations must be created in a file "site.ducc.properties" that is in
 # your ducc_runtime/resources.  DUCC's startup procedures will merge this file and
-# your site.ducc.propeties into ducc.properties which is waht DUCC will use.
+# your site.ducc.propeties into ducc.properties which is what DUCC will use.
 # WARNING DO NOT EDIT THIS FILE.
 
 # ====================================================================================
@@ -92,7 +92,7 @@ ducc.broker.credentials.file=${ducc.priv
 # ActiveMQ Auto-management configuration
 #    docc.broker.automanage    - if true, DUCC will start and stop the broker as needed.  
 #                                Otherwise, the installation is responsible for
-#                                manageing ActiveMQ
+#                                managing ActiveMQ
 #    ducc.broker.memor.options - If automanaged, the memory configuration passed to the JVM
 #    ducc.broker.configuration - If automanaged, the location of the ActiveMQ broker configuration
 #    ducc.broker.home          - If automanaged, the location of the ActiveMQ installation
@@ -257,7 +257,7 @@ ducc.jd.share.quantum.reserve.count = 3
 #        UIMA-AS client onBeforeMessageSendHandler callbacks, and
 #        UIMA-AS client onBeforeProcessCAS callbacks
 # Note: should contain an Xmx a little below the "ducc.jd.share.quantum" value
-#       the Xmx entry is ignored if the user has speccified one
+#       the Xmx entry is ignored if the user has specified one
 ducc.driver.jvm.args  = -Xmx300M
 
 # Max number of threads in Jetty thread pool servicing incoming
@@ -274,7 +274,7 @@ ducc.driver.jvm.args  = -Xmx300M
 # ========== Service Manager Configuration block ========== 
 # Class used to implement the SM - internals only, don't change.
 ducc.sm.configuration.class=org.apache.uima.ducc.sm.config.ServiceManagerConfiguration
-# Name of the AMQ topic used to communicate wiht SM - internals, don't change
+# Name of the AMQ topic used to communicate with SM - internals, don't change
 ducc.sm.state.update.endpoint=ducc.sm.state
 # AMQ protocol to use - internals, don't change
 ducc.sm.state.update.endpoint.type=topic
@@ -290,7 +290,7 @@ ducc.sm.instance.failure.window 30
 ducc.sm.init.failure.limit  1
 # How often services are monitored to insure they're responding, in milliseconds
 ducc.sm.meta.ping.rate = 60000
-# How many consecutive missed pings are required to mark a service unresponive
+# How many consecutive missed pings are required to mark a service unresponsive
 ducc.sm.meta.ping.stability =  10
 # How long to wait for a ping to respond, in milliseconds
 ducc.sm.meta.ping.timeout =  15000
@@ -335,10 +335,10 @@ ducc.orchestrator.unmanaged.reservations
 ducc.rm.configuration.class=org.apache.uima.ducc.rm.config.ResourceManagerConfiguration
 # Queue name for broadcast RM state
 ducc.rm.state.update.endpoint=ducc.rm.state
-# If enabled, RM tries to start as soon as it recoveres state from an OR publication,
-# instread of waiting for init.stability for nodes to check in. 
+# If enabled, RM tries to start as soon as it recovers state from an OR publication,
+# instead of waiting for init.stability for nodes to check in. 
 ducc.rm.state.update.endpoint.type=topic
-# the frequency, relative to or publicatations, at which RM runs a schedule
+# the frequency, relative to or publications, at which RM runs a schedule
 ducc.rm.state.publish.ratio = 1
 
 # maximum allotment in GB for Non-preemptable shares - default is unlimited