Home › Forums › implementation › Implementation discussion ›

Tomcat 7/OpenVPMS 1.8 log worries

Submitted by Guest on Tue, 21/07/2015 - 04:57
in

I have just done a Tomcat 6 to 7 upgrade on a system running OpenVPMS 1.8

On a Tomcat shutdown the Tomcat log shows:

Do I need to worry about these entries?

Regards, Tim G

‹ Cloud install 1.8 6650 Investigations - page to end problem ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Tomcat 7/OpenVPMS 1.8 log worries

Submitted by tanderson on Tue, 21/07/2015 - 09:31.

You only need to worry about it if you repeatedly start and stop OpenVPMS via Tomcat Manager. If you shut down Tomcat itself, not so much.

The errors regarding the scheduler_worker threads can probably be removed by changing <TOMCAT_HOME>/webapps/openvpms/WEB-INF/openvpms-framework.xml to include waitForJobsToCompleteOnShutdown:

<bean id="scheduler" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
    <property name="jobFactory">
        <bean class="org.springframework.scheduling.quartz.SpringBeanJobFactory"/>
    </property>
    <property name="quartzProperties">
        <props>
            <prop key="org.quartz.plugin.jobHistory.class">org.quartz.plugins.history.LoggingJobHistoryPlugin</prop>
        </props>
    </property>
    <property name="waitForJobsToCompleteOnShutdown" value="true"/>
</bean>

The Pipe: threads will need a code change.

I'm a bit surprised you are seeing the error regarding the MySQL driver. You can ignore it, but it shouldn't occur as the MySQL driver should be in the Tomcat lib/ directory and thus be loaded by the jvm. See http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-...

Raised as https://openvpms.atlassian.net/browse/OVPMS-1640

 

Syndicate content