HTTP Server for i Gets Isolation Chambers
October 21, 2014 Alex Woodie
|
Running big Web workloads on the IBM i server is about to get easier, thanks to changes IBM made to the HTTP Server for i with the latest Technology Refreshes. IBM has done a great job with its HTTP Server for i, the one powered by Apache. It’s powerful, standardized, and integrated directly into IBM i, giving users the best of both worlds. And with application modernization on the upswing, it’s no surprise that the HTTP Server is getting a good workout at shops around the world. But with all that use comes a cost, particularly when hundreds or thousands of users are hitting the Web server simultaneously. The HTTP Server can scale to meet surging demand, but it could gobble up system resources, thereby making other applications on the box run slower. Currently, all HTTP Server for i jobs run in the system-defined subsystem QHTTPSVR. But with IBM i 7.1 TR9 and 7.2 TR1, IBM is giving IBM i shops the option to isolate HTTP workloads from other applications by putting HTTP server jobs in customized subsystems. With the HTTP Server jobs running in their own subsystems, it reduces the chance that a surge on the Web will siphon memory and CPU from other jobs. The new IBM i TRs also bring support for timeouts with the HTTP Server for i. The new “mod_reqtimeout” parameter enables various timeouts to be set for receiving the request headers and the request body from the client. If the client fails to send headers or body within the configured time, a 408 REQUEST TIME OUT error is sent, IBM says. The new features will become available with the new TRs on November 11. For more info on IBM i 7.1 TR9, see United States Software Announcement 214-399. For IBM i 7.2 TR1, see United States Software Announcement 214-418.
|
