[
https://issues.apache.org/activemq/browse/SM-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38615
]
Jamie Goodyear commented on SM-108:
-----------------------------------
Hi All,
Reviewing this report it appears that the timer restart issue was resolved
a while ago but the JIRA entry was not updated to reflect change of status.
To test this issue I inserted System.out.println's into the start and
schedule
timer methods of AutoDeploymentService.java and StatisticsService.java, and
built
a new servicemix-core jar file to run with the Servicemix 3.1 kit. When
ServiceMix
was started I would observe only one instance of the timers being started.
The setStatsInterval methods now only update a variable, it does not
explicitly
restart a timer.
Could we update this issue as Resolved-Fixed?
Cheers,
Jamie
>From Logging:
C:\Apache\kit\bin>servicemix
Starting Apache ServiceMix ESB: 3.2-incubating-SNAPSHOT
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.2-incubating-SNAPSHOT JBI
Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please
see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
INFO - jetty - Logging to [EMAIL PROTECTED] via
org.apache.service
mix.http.jetty.JCLLogger
INFO - DeploymentService - Restoring service assemblies
JG:: START Method
JG:: Schedule Stats Timer Method
INFO - ComponentMBeanImpl - Setting running state for Component:
servicemix-eip to Started
INFO - ComponentMBeanImpl - Initializing component: servicemix-eip
INFO - ComponentMBeanImpl - Setting running state for Component:
servicemix-http to Started
INFO - ComponentMBeanImpl - Initializing component: servicemix-http
INFO - ComponentMBeanImpl - Setting running state for Component:
servicemix-jms to Started
INFO - ComponentMBeanImpl - Initializing component: servicemix-jms
INFO - ComponentMBeanImpl - Setting running state for Component:
servicemix-saxon to Started
INFO - ComponentMBeanImpl - Initializing component:
servicemix-saxon
INFO - ServiceAssemblyLifeCycle - Starting service assembly: bridge-sa
INFO - ServiceUnitLifeCycle - Initializing service unit:
bridge-http-su
INFO - ServiceUnitLifeCycle - Initializing service unit:
bridge-eip-su
INFO - ServiceUnitLifeCycle - Initializing service unit:
bridge-xslt-su
INFO - ServiceUnitLifeCycle - Initializing service unit:
bridge-jms-su
INFO - ServiceUnitLifeCycle - Starting service unit: bridge-http-su
INFO - jetty - jetty-6.0.1
INFO - jetty - Started SelectChannelConnector @
0.0.0.0:8192
INFO - ServiceUnitLifeCycle - Starting service unit: bridge-eip-su
INFO - ServiceUnitLifeCycle - Starting service unit: bridge-xslt-su
INFO - ServiceUnitLifeCycle - Starting service unit: bridge-jms-su
JG:: framework start
JG:: sched Dir Timer method
INFO - JBIContainer - ServiceMix JBI Container (ServiceMix)
started
> Timer is repeatedly setup/cancelled during startup
> --------------------------------------------------
>
> Key: SM-108
> URL: https://issues.apache.org/activemq/browse/SM-108
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-core
> Affects Versions: 1.0
> Reporter: Peter Smith
> Priority: Minor
>
> EnvironmentContext.java
> The scheduleStatsTImer() method is called during startup as a side-effect of
> setStatsInterval. In this case wouldn't it make more sense to defer actually
> doing anything until the EnvironmentContext.start processing. Otherwise the
> timer get set & cancelled several timers during startup.
> Ditto for other similar cases like
> AutoDeploymentService.scheduleDirectoryTimer
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
