Diagnostic tool reveals unexpected errors in complex networked applications

Researchers at the NYU Polytechnic School of Engineering and the University of British Columbia have developed the first tool of its kind for diagnosing failures in complex networked applications like Skype, Firefox, and Apache. Upending traditional application diagnostics, NetCheck requires neither source code nor application-specific information, but instead relies on modeling and simulating networking behaviors to identify issues that cause failures.

Justin Cappos, an assistant professor in the School of Engineering Department of Computer Science and Engineering, and his students designed NetCheck to sidestep a common shortcoming of current diagnostics. "Most are designed to function in an ideal network environment, but that's never the case in the ," explained Cappos. "NetCheck builds a simulated environment that allows programmers to see how applications perform amid unexpected network behaviors and configurations, and to address the errors that inevitably surface."

NetCheck requires only a single input that is easily collected. It has been tested on dozens of widely used applications, and it correctly identified 95 percent of the failures reported by bug trackers—outsiders who discover coding "bugs" and alert the organization. Cappos and his team released NetCheck under an open source license, making the tool freely available for download.

More information: Cappos presented NetCheck at the USENIX Symposium on Networked Design and Implementation (NSDI) in April 2014. To view the paper, visit www.usenix.org/conference/nsdi … /presentation/zhuang

Citation: Diagnostic tool reveals unexpected errors in complex networked applications (2014, May 13) retrieved 18 April 2024 from https://phys.org/news/2014-05-diagnostic-tool-reveals-unexpected-errors.html
This document is subject to copyright. Apart from any fair dealing for the purpose of private study or research, no part may be reproduced without the written permission. The content is provided for information purposes only.

Explore further

The dangers of too much Java

0 shares

Feedback to editors