Question #44129 on ERMA changed:
https://answers.launchpad.net/erma/+question/44129
JakubM gave more information on the question:
The wiring used:
<bean class="com.orbitz.monitoring.lib.BaseMonitoringEngineManager"
init-method="startup" destroy-method="shutdown">
<constructor-arg ref="mpf"/>
<!-- constructor-arg ref="decomposer"/ -->
</bean>
<bean id="mpf"
class="com.orbitz.monitoring.lib.factory.SimpleMonitorProcessorFactory">
<constructor-arg>
<list>
<ref bean="routeToLog"/>
</list>
</constructor-arg>
</bean>
<bean id="routeToLog" class="com.orbitz.monitoring.lib.factory.ProcessGroup">
<description>
Routes all monitoring events to the log files for easy development testing
of instrumentation
</description>
<constructor-arg ref="AsyncProcessor"/>
</bean>
<bean id="AsyncProcessor"
class="com.orbitz.monitoring.lib.processor.AsyncMonitorProcessor">
<constructor-arg>
<list>
<ref bean="LogProcessor"/>
</list>
</constructor-arg>
</bean>
<bean id="LogProcessor"
class="com.orbitz.monitoring.lib.processor.LoggingMonitorProcessor"/>
When I switched to this:
<bean id="routeToLog" class="com.orbitz.monitoring.lib.factory.ProcessGroup">
<description>
Routes all monitoring events to the log files for easy development testing
of instrumentation
</description>
<constructor-arg ref="LogProcessor"/>
</bean>
<bean id="LogProcessor"
class="com.orbitz.monitoring.lib.processor.LoggingMonitorProcessor"/>
everything is fine.
In first case startup method of LoggingMonitorProcessor was not called.
You received this question notification because you are a member of
Erma-core, which is an answer contact for ERMA.
_______________________________________________
Mailing list: https://launchpad.net/~erma-core
Post to : erma-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~erma-core
More help : https://help.launchpad.net/ListHelp
