Application/Data Server - Job Usage

This forum allows developers to post programming tips and coding techniques that may be useful to other Visual LANSA developers. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
User avatar
Stewart Marshall
Posts: 417
Joined: Thu Nov 05, 2015 5:25 pm

Application/Data Server - Job Usage

Post by Stewart Marshall » Fri Feb 12, 2016 3:04 pm

Despite the best efforts of developers, it is effectively impossible to ensure that all memory resources are used perfectly. The greater the complexity of the software and the more often its used, the greater the likelihood of memory leaks, corruption and ultimately a crash. Even a Boeing Dreamliner needs to be rebooted every 248 days to ensure that a variable doesn't overflow and cause the plane to fall from the sky.

http://www.engadget.com/2015/05/01/boei ... tware-bug/

The LANSA Data/Application server running on Windows regularly stops and starts web job instances (w3_p1200.exe). By default, it does this every time a request is received. This is a relatively expensive overhead, and while the power of the modern PC means that it goes largely unnoticed, it can cause short delays when running Web Pages directly from the IDE during development.

It is recommended that all developers executing Web Pages locally change the default setting to ensure better reuse of web jobs. This can be done using the LANSA Web Administrator utility.

http://docs.lansa.com/140/en/lansa085/# ... P_0300.htm
Stewart Marshall

Independent IT Consultant
www.marshallfloyd.com.au

Post Reply