RFR: 8003322: Add instrumentation points for tracing of I/O calls (original) (raw)

Staffan Larsen staffan.larsen at oracle.com
Tue Nov 13 10:16:57 UTC 2012


This is a request for review for adding tracing to I/O calls. For now, this is an empty infrastructure intended to enable diagnosing/tracing of i/o calls. A user of the API can register a callback for read and write operations on sockets and files. It does not (yet) cover asynchronous i/o calls. When not used, the implementation should add a minimum of overhead. To provide useful information to the user, FileInputStream, FileOutputStream and RandomAccessFile have been modified to keep track of the path they operate on (when available).

Webrev: http://cr.openjdk.java.net/~sla/8003322/webrev.00/ Bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8003322

I believe all comments from the preliminary review [1] have been addressed. In particular:

There is one remaining issue: IoTrace and IoTraceContext are now in sun.misc, but concerns where raised that this would be a problem with jigsaw. Suggestions are welcome if this is still a problem.

Thanks, /Staffan

[1] http://mail.openjdk.java.net/pipermail/core-libs-dev/2012-November/012066.html



More information about the core-libs-dev mailing list