Java -runtime- code analysis tool capable to detect common issues? [closed]

I'm aware of various good Java static analysis tools (see Static Analysis tool recommendation for Java? for some) but by nature these tools are limited in capabilites in the way the look at very large projects and are usually unable to pinpoint issues due to runtime interaction between our code and containers.

Thus I'm looking for Java runtime analytics capable to augment bytecode at runtime (like the code coverage tools do) and detect anomalies in the usage of Input/Output Streams during a specific run. I'm specifically looking for a tool which can detect:

• Unclosed streams
• Streams which have been opened but have not been read/written
• Useless wrapping of buffered streams around other buffered streams

Ideally I'd like to be able to add this tool to the pipeline and run it during the unit tests in order to automatically detect and report such anomalies.

Ideally I'd also appreciate being able to run it interactively within the Eclipse environment but this is not mandatory.