mrc logo mrc logo
  • m-Power m-Power
    What is m-Power?
    Overview Demos Build Process Case Studies Specs Pricing Trial
    m-Power Resources
    Overview How-To Videos Webinars & Podcasts White Papers Fact Sheets
  • Solutions Solutions
    What does m-Power build?
    Overview Database Front-Ends Reporting Business Intelligence Dashboards Mobile Apps ERP Enhancements Modernization Spreadsheets to the web MS Access to the web B2B/Web Portals Scheduling Embedded Analytics Web Forms Workflow Data Exploration Budgeting & Forecasting APIs and Web Services
    Solutions by Industry
    Overview Manufacturing Government Foodservice Software Vendors Logistics & Supply Chain Software Consultants Healthcare
  • Services Services
    Overview Training Project Consulting Staff Consulting Mentoring
  • About About
    Overview Partners Press Releases Careers Events Contact Blog
  • Support Support
    Support Home FAQ Documentation Customer Portal Enhancements Updates Roadmap Techblog
Try m-Power

m-Power Manual

Browse:

  • Home
  • m-Power Administration
  • Configuring Tomcat to not Reload for Production Tomcat
Back to Manual

Configuring Tomcat to not Reload for Production Tomcat

 

Your application server, Tomcat, comes with a feature called "Reload". Reload is a must in a development environment. After you compile an application or save an application, Tomcat reloads your changes, making them available to you for testing purposes. The downside of this is that at each reload, Tomcat must release all users (if Sign-on Security has been implemented) and it can take a small hit in terms of performance. In a development environment, both of these effects are understandable.

In a production environment, on the other hand, a user should never be asked to sign in twice, nor should there be any performance hit. To solve this problem, the makers of Tomcat have given you the ability to turn off the ability for Tomcat to reload.

Note: The following methods should only be needed on a production instance of Tomcat running on a Windows server.

Edit the following file: \m-power\tomcat\conf\server.xml

Note the above highlighted area. This path is your runtime path (the location that controls your generated application). On the first highlighted line, change the value of reloadable from "true" to "false".

When completed, your page should look something like this:

Some other things to consider:

Because reload has now been turned off, any time a new application is moved from development to production, Tomcat will ignore the application until Production Tomcat is restarted. Because of this, you might want to schedule Tomcat to be restarted on a nightly or weekly basis during non-peak hours of activity.

Created: May 1, 2008 | Modified: June 12, 2017

Search


Browse By Category

Build Process (13)
Starting with m-Power (8)
Retrievals (10)
Reports (15)
Summaries (4)
Maintainers (17)
Graphs (8)
m-Power Data Explorer (4)
General (24)
Calculations (5)
Utilities (9)
m-Power Administration (23)
Security (11)
Freemarker (6)
m-Painter (29)
Form Validation (5)
External Objects & UDFs (12)
Deprecated Documentation (23)
Bootstrap Templates (7)

Popular Tags

Video Administration Graph Properties Java Record Selections Summaries App Properties Data Dictionary Parameters mrc-Productivity Series Popular Graphing Email Getting Started RPG Graphs Performance Security Dropdowns Build Process Advanced External Objects Form Validation Maintainer Bootstrap Templates Maintainers Report Production Compiling Bar Graphs Calculations Prompt Screens Retrieval Retrievals Tomcat Freemarker Application Properties m-Painter Dates Reports Database Admin DB2 SQL Excel

See all tags »

michaels, ross & cole, ltd. (mrc)
Privacy Settings Privacy Policy Cookie Policy Employee Intranet
© 2018 mrc. All rights reserved.
mrc (US)

2001 Midwest Road
Suite 310
Oak Brook, IL 60523
630-916-0662

mrc (UK)

Mortlake Business Centre
20 Mortlake High Street
London, SW14 8JN
+44-20-335-59566