Abstract
This chapter discusses the perils that await the unwary programmer once threads come on the scene. The bugs I’m discussing can be nasty ones to find because they’re often timing related. They tend to manifest once a month (or once a year), not every time the program executes, and they can be almost impossible to duplicate when they do occur. (The actions that caused the program to hang once might not cause it to hang all the time, and in fact, might have been working fine for the last year.) This unpredictability makes it all the more important to recognize and stamp out these bugs early in the design process.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2000 Allen I. Holub
About this chapter
Cite this chapter
Holub, A. (2000). The Perils of Multithreaded Programming. In: Taming Java Threads. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-1129-7_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-1129-7_2
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-893115-10-1
Online ISBN: 978-1-4302-1129-7
eBook Packages: Springer Book Archive