RLK.IN
RLK (Resource Leak) issues are reported when resources are allocated but not properly disposed after use. Failing to properly dispose a resource can lead to such problems as:
- too many files being open
- an application not being able to access a temporary file when it is needed
RLK.IN indicates that an input stream that was opened is not explicitly closed.
Vulnerability and risk
Resources such as streams, connections and graphic objects must be explicitly closed. The close operation can unblock transactions or flush file changes in the file system. While a resource will eventually be closed by the garbage collector, resource exhaustion can occur before garbage collection starts. Depending on the nature of the resource, various exceptions will be thrown on a failed attempt to allocate another resource, for example: java.io.FileNotFoundException: Too many open files or too many database connections.
Mitigation and prevention
Explicitly close all resources that have the close method, even those that you think are not doing anything significant. Future code changes will then be safe from such errors.
Example 1
static final String propertyFile = "my_config.ini";
static String getProperyFromConfigFile(String name)
throws IOException {
Properties prop = new Properties();
FileInputStream st = new FileInputStream(propertyFile);
prop.load(st);
return prop.getProperty(name);
}RLK.IN is reported for the snippet on line 17: input stream 'st' is not closed after creation.
Example 2
static final String propertyFile = "my_config.ini";
static String getProperyFromConfigFile(String name)
throws IOException {
Properties prop = new Properties();
FileInputStream st = new FileInputStream(propertyFile);
try {
prop.load(st);
} finally {
st.close();
}
return prop.getProperty(name);
}The snippet from the previous section is fixed; RLK.IN is not reported here.
External guidance
Extension
This checker can be extended through the Klocwork knowledge base. See Tuning Java analysis for more information.
