ThreadSafe

ThreadSafe is a source code analysis tool that identifies application risks and security vulnerabilities associated with concurrency in Java code bases, using whole-program interprocedural analysis.[1][2][3][4] ThreadSafe is used to identify and avoid software failures in concurrent applications running in complex environments.[1][2][5][6]

ThreadSafe
ThreadSafe for Eclipse
Developer(s)Contemplate
Stable release
1.3 / March 28, 2014 (2014-03-28)
Operating systemCross-platform: Linux, OS X, Windows
TypeStatic code analysis
LicenseProprietary software
Websitewww.contemplateltd.com/threadsafe

Features

ThreadSafe detects Java concurrency defects:[2][3][4]

  • Race conditions – which lead to incorrect or unpredictable behaviour that is difficult to reproduce in a debugger.
  • Deadlocks[7] – caused by circular waits between threads waiting for shared resources.
  • Unpredictable results – caused by incorrect handling of concurrent collections, bad error handling, or mixed object synchronization.
  • Performance bottlenecks – caused by incorrect API usage, redundant synchronization, and unnecessary use of shared mutable state.

ThreadSafe is integrated with the Eclipse software development environment and with the SonarQube software quality management platform. Contextual information is provided within the development environment to assist the developer with the investigation and resolution of concurrency issues, directly in the code.[2][3][4] A command-line version is available for users of IDEs other than Eclipse and for build process integration.

Checking adherence to standards

ThreadSafe detects violations of the concurrency-related rules in the CERT Oracle Secure Coding Standard for Java.[8]

gollark: What if golflang with Huffman coding for instructions (or arithmetic coding or whatever the trendy thing is now) based on measured frequency of instructions in arbitrary code golf challenges?
gollark: Consider the finite field GF(2) then?
gollark: It happened again in the simulation, so we had to use the simulation to simulate another simulation.
gollark: Running on the Oort cloud nodes mostly.
gollark: Technically, Earth was destroyed and this is just a GTech™ simulation.

See also

References
  1. Grazi, Victor (August 28, 2013). "ThreadSafe Concurrency Static Analysis Tool Announces First Public Release". InfoQ.com.
  2. Taft, Darryl (September 4, 2013). "Contemplate Delivers ThreadSafe Java Concurrency Static Analysis Tool". DevX.com.
  3. Atkey, Robert (January 14, 2014). "Discover and Diagnose Java Concurrency Problems Using Contemplate's ThreadSafe". InfoQ.com.
  4. Atkey, Robert; Sannella, Donald (2015). "ThreadSafe: Static Analysis for Java Concurrency". Electronic Communications of the EASST. 72. doi:10.14279/tuj.eceasst.72.1025.995.
  5. Roy, Ritobaan (May 1, 2013). "Software Errors: New Technology Briefing For CFOs". CFO Insight. Archived from the original on October 14, 2013. It claims to have developed technology [refers to ThreadSafe, as explained in caption of image, missing from archived version] that can identify errors in software code that don't pop up regularly enough to be detected by conventional tools.
  6. Rubens, Paul (March 12, 2014). "Why Software Testing Can't Save You From IT Disasters". Reference to ThreadSafe on page 2. CIO.com.
  7. Raible, Matt (June 26, 2014). "Contemplate ThreadSafe Introduces Deadlock Detection". InfoQ.com.
  8. "SEI CERT Oracle Coding Standard for Java". Software Engineering Institute, Carnegie Mellon University. Retrieved March 18, 2016.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.