felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r921214 - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/apache-felix-event-admin.html
Date Thu, 04 Sep 2014 09:45:11 GMT
Author: buildbot
Date: Thu Sep  4 09:45:10 2014
New Revision: 921214

Log:
Staging update by buildbot for felix

Modified:
    websites/staging/felix/trunk/content/   (props changed)
    websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-event-admin.html

Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Sep  4 09:45:10 2014
@@ -1 +1 @@
-1621566
+1622436

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-event-admin.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-event-admin.html
(original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-event-admin.html
Thu Sep  4 09:45:10 2014
@@ -210,13 +210,15 @@ A timeout can be configured which is use
 The Felix Event Admin can be configured either through framework properties or through the
configuration admin using PID <code>org.apache.felix.eventadmin.impl.EventAdmin</code>.
This is a list of configuration properties:
 |Function|Property Name|Type and Default|Description|
 |--|--|--|
-|Cache Size|org.apache.felix.eventadmin.CacheSize|Integer, 30|The size of various internal
caches. The default value is 30. Increase in case of a large number (more then 100) of services.
A value less then 10 triggers the default value.|
-|Thread Pool Size|org.apache.felix.eventadmin.ThreadPoolSize|Integer, 10|The size of the
thread pool. The default value is 10. Increase in case of a large amount of synchronous events
where the event handler services in turn send new synchronous events in the event dispatching
thread or a lot of timeouts are to be expected. A value of less then 2 triggers the default
value. A value of 2 effectively disables thread pooling.|
+|Thread Pool Size|org.apache.felix.eventadmin.ThreadPoolSize|Integer, 20|The size of the
thread pool used for event delivery. The default value is 20. Increase in case of a large
amount of events. A value of less then 2 triggers the default value. If the pool is exhausted,
event delivery is blocked until a thread becomes available from the pool. Each event is delivered
in a thread from the pool unless the ignore timeouts is configured for the receiving event
handler.|
+|Async/sync Thread Pool Ratio|org.apache.felix.eventadmin.AsyncToSyncThreadRatio|Double,
0.5|The ratio of asynchronous to synchronous threads in the internal thread pool. Ratio must
be positive and may be adjusted to represent the distribution of post to send operations.
 Applications with higher number of post operations should have a higher ratio. This option
is available starting with release 1.4.2.|
 |Timeout|org.apache.felix.eventadmin.Timeout|Integer, 5000|The black-listing timeout in milliseconds.
The default value is 5000. Increase or decrease at own discretion. A value of less then 100
turns timeouts off. Any other value is the time in milliseconds granted to each event handler
before it gets blacklisted.|
 |Require Topic|org.apache.felix.eventadmin.RequireTopic|Boolean, true|Are event handlers
required to be registered with a topic? This is enabled by default. The specification says
that event handlers must register with a list of topics they are interested in. Disabling
this setting will enable that handlers without a topic are receiving all events (i.e., they
are treated the same as with a topic=*).|
-|Ignore Timeouts|org.apache.felix.eventadmin.IgnoreTimeout|String, empty|Configure event
handlers to be called without a timeout. If a timeout is configured by default all event handlers
are called using the timeout. For performance optimization it is possible to configure event
handlers where the timeout handling is not used - this reduces the thread usage from the thread
pools as the timout handling requires an additional thread to call the event handler. However,
the application should work without this configuration property. It is a pure optimization!
The value is a list of strings. If a string ends with a dot, all handlers in exactly this
package are ignored. If the string ends with a star, all handlers in this package and all
subpackages are ignored. If the string neither ends with a dot nor with a start, this is assumed
to define an exact class name.|</p>
+|Ignore Timeouts|org.apache.felix.eventadmin.IgnoreTimeout|String, empty|Configure event
handlers to be called without a timeout. If a timeout is configured by default all event handlers
are called using the timeout. For performance optimization it is possible to configure event
handlers where the timeout handling is not used - this reduces the thread usage from the thread
pools as the timout handling requires an additional thread to call the event handler. However,
the application should work without this configuration property. It is a pure optimization!
The value is a list of strings. If a string ends with a dot, all handlers in exactly this
package are ignored. If the string ends with a star, all handlers in this package and all
subpackages are ignored. If the string neither ends with a dot nor with a start, this is assumed
to define an exact class name.|
+|Ignore Topics|org.apache.felix.eventadmin.IgnoreTopic|String, empty|For performance optimization
it is possible to configure topics which are ignored by the event admin implementation. In
this case, a event is not delivered to registered event handlers. The value is a list of strings
(separated by comma). " +If a single value ends with a dot, all topics in exactly this package
are ignored. If a single value ends with a star, all topics in this package and all sub packages
are ignored. If a single value neither ends with a dot nor with a start, this is assumed to
define an exact topic. A single star can be used to disable delivery completely. This options
is available starting with release 1.4.0.|
+|Log Level|org.apache.felix.eventadmin.LogLevel|Integer, 2 (=WARNING)|This sets the log level
used for messages outputted by the event admin implementation. Valid values are 1 (=ERROR),
2 (=WARNING), 3 (=INFO), and 4 (=DEBUG). The default is 2 and an invalid value sets the level
to the default value.|</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1461588 by fmeschbe on Wed, 27 Mar 2013 14:09:59 +0000
+        Rev. 1622436 by cziegeler on Thu, 4 Sep 2014 09:44:43 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project



Mime
View raw message