I've been spending my weekends developing a SAS Publishing book proposal. (For those interested, it involves learning how to fully leverage SAS Stored Processes as a beginning programmer.) Creating examples and jumping between coding, testing and then writing about everything, I have had a heck of a time with my web application timing out on me. I had already added the Log back In button, but it would be even easier if the web application stayed active for sixty minutes. Keeping the writing cycle productive is much more important than my laptop's ability to handle multiple active sessions for that length of time. I have written about this before but two years ago when everything was in Tomcat. Fortunately, the SAS Documentation has the detail on where in jBoss the session timeout interval should now be included.

1. My jBoss files are exploded (not ka-boom, but converted from .ear to physical folders), so I went directly to: C:\jboss-4.2.3.GA\server\SASServer1\deploy_sas\sas.storedprocess9.3.ear\sas.storedprocess.war\WEB-INF
2. Based on prior experiences, I find it best to copy the original before making changes. Always saves me headaches somewhere.
3. Then I included the following code at the bottom of the web.xml file (before the closing </web-app> xml tag and restarted jBoss:

<session-config> <session-timeout>60</session-timeout></session-config>

A couple of important notes on making these changes:

• My change only affects the Stored Process web application. If this change is needed for Information Delivery Portal, Web Report Studio, and so on, each has it's own web.xml file.
• If you redeploy the web application, any changes made directly to jBoss application files are removed. The SAS Documentation provides the installation directory where making these changes will not be affected by redeploy steps. However, in the same token if you upgrade the web applications these changes are typically lost during the installation process.
• Consider the business/security rules as well as the server's ability to handle these long running active sessions before making any modifications.