The DOI matches its Crossref record; 6 of the 6 references it cites were found in a registry or an index.
Software rejuvenation: analysis, module and applications
Abstract
Software rejuvenation is the concept of gracefully terminating an application and immediately restarting it at a clean internal state. In a client-server type of application where the server is intended to ran perpetually for providing a service to its clients, rejuvenating the server process periodically during the most idle time of the server increases the availability of that service. In a long-running computation-intensive application, rejuvenating the application periodically and restarting it at a previous checkpoint increases the likelihood of successfully completing the application execution. We present a model for analyzing software rejuvenation in such continuously-running applications and express downtime and costs due to downtime during rejuvenation in terms of the parameters in that model. Threshold conditions for rejuvenation to be beneficial are also derived. We implemented a reusable module to perform software rejuvenation. That module can be embedded in any existing application on a UNIX platform with minimal effort. Experiences with software rejuvenation in a billing data collection subsystem of a telecommunications operations system and other continuously-running systems and scientific applications in AT&T are described.>
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Transaction Processing: Concepts and Techniques
Gray, J., & Reuter, A. (1992) · Cited by 3,000
Software Reliability: Measurement, Prediction, Application
Musa, D., Iannino, A., & Okumoto, K. (1987) · Cited by 1,675
Parnas, D. L. (1994) · doi:10.5555/257734.257788 · Cited by 655
Software reliability measurement
Musa, J. D. (1979) · Journal of Systems and Software · doi:10.1016/0164-1212(79)90023-2 · Cited by 569
Optimizing Preventive Service of Software Products
Adams, E. N. (1984) · IBM Journal of Research and Development · doi:10.1147/rd.281.0002 · Cited by 373
Parnas, D. L. (2002) · Proceedings of 16th International Conference on Software Engineering · doi:10.1109/icse.1994.296790 · Cited by 369
Cited by
Deswarte, Y., Quisquater, J.-J., & Saïdane, A. (2005) · IFIP International Federation for Information Processing · doi:10.1007/1-4020-7901-x_1 · Cited by 321
Analysis of Software Aging in a Web Server
Grottke, M., Li, L., Vaidyanathan, K., & Trivedi, K. S. (2006) · IEEE Transactions on Reliability · doi:10.1109/tr.2006.879609 · Cited by 285
Controlling software architecture erosion: A survey
de Silva, L., & Balasubramaniam, D. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2011.07.036 · Cited by 184
A survey of AIOps methods for failure management
Notaro, P., Cardoso, J., & Gerndt, M. (2021) · ACM Transactions on Intelligent Systems and Technology · doi:10.1145/3483424 · Cited by 142
Metadata
- Authors
- Huang, Y., Kintala, C., Kolettis, N., & Fulton, N. D.
- Venue
- Twenty-Fifth International Symposium on Fault-Tolerant Computing. Digest of Papers
- Publisher
- IEEE Comput. Soc. Press
- Published
- 2002-11-19
- Pages
- 381-390
- OpenAlex
- W2109192777
- Cited by
- 926
- References
- 6
- FWCI
- 21.13
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Software rejuvenation: analysis, module and applications. https://app.cochat.ai/papers/10.1109/ftcs.1995.466961
- The paper
- Huang, Y., Kintala, C., Kolettis, N., & Fulton, N. D. (2002). Software rejuvenation: analysis, module and applications. Twenty-Fifth International Symposium on Fault-Tolerant Computing. Digest of Papers. https://doi.org/10.1109/ftcs.1995.466961
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.
