Workaround: The creation of the Money that Matters lifecycle sample might fail with a socket timeout

Knut Radloff
Last Updated: September 14, 2012
Build Basis: Rational Requirements Composer 4.0 and 4.0.0.1

Summary

The creation of the Money that Matters lifecycle sample might fail with a socket timeout.

More Information

In the Money that Matters lifecycle sample, the step to create sample artifacts in the Requirements Management (RM) application can take a long time to complete, especially if you are using a clustered environment. If the step takes too long, the browser displays a 500 error message with the following details: “SocketTimeoutException: Read timed out“.

Workaround

1. In the Lifecycle Project Administration (LPA) application, which is in the conf/admin directory, open the admin.properties file.
2. In the file, search for http.socket.timeout=1800000, and then do one of these steps:
   • If the file does not contain the line, add it.
   • If the file contains the line, edit it to contain a longer timeout, such as 1800000.
3. Restart the server.
4. Rename the Money that Matters lifecycle projects that are in each of the applications, and archive the projects.
5. Create the sample again.

Related Information

The following links point to related information:

• 59434: Clustering – Error creating the sample: java.net.SocketTimeoutException