|
Diagnosing Java Code : The Orphaned Thread bug pattern
| Link ID |
22414 |
| Title |
Diagnosing Java Code : The Orphaned Thread bug pattern |
|
|
| Url |
Visit : Diagnosing Java Code : The Orphaned Thread bug pattern |
| Description |
In multithreaded code, it is often common to use a single, master thread that drives the actions the other threads take. This master thread may send messages, often by placing them on a queue, that are then processed by the other threads. But if the master thread throws an exception, the remaining threads may continue to run, awaiting more input to the queue, causing the program to freeze. This article discusses detecting, fixing, and avoiding this bug pattern. |
| Category |
Java > Tutorials > Development |
| Keywords |
Diagnosing Java Code : The Orphaned Thread bug pattern |
| Date |
Sep 20, 2007 |
Refer it to Friend ( Diagnosing Java Code : The Orphaned Thread bug pattern )
Write a Review ( Diagnosing Java Code : The Orphaned Thread bug pattern )
Report Broken Link ( Diagnosing Java Code : The Orphaned Thread bug pattern )
Add : Diagnosing Java Code : The Orphaned Thread bug pattern To Favorites
More links included : Diagnosing Java Code : The Orphaned Thread bug pattern
Site links : Diagnosing Java Code : The Orphaned Thread bug pattern
Traffic Details from Alexa : Diagnosing Java Code : The Orphaned Thread bug pattern
|
|
Other links at Java > Tutorials > Development |
| 1. |
Data Management in J2EE Apps
|
|
|
This article examines two data management strategies available on the Java platform: Java object serialization and Java Database Connectivity (JDBC). While neither data management strategy is inherently superior or inferior to the other, when it comes to managing enterprise information systems, JDBC wins hands down.
|
| 2. |
Java Performance Tuning w/ Fat Clients
|
|
|
Tuning isnt always about speed, sometimes other aspects of the application need fixing. When your application needs tuning, your first course of action is normally to monitor the application with a profiler. But profiling is not always practical -- sometimes for ironic reasons. In this installment of Eye on performance, Jack Shirazi and Kirk Pepperdine, Director and CTO of Java Performance Tuning relate their recent experiences with profiling a fat client -- so fat, in fact, that it left no room for a profiler.
|
| 3. |
Unclogging Server Bottlenecks w/ Active Containers
|
|
|
In server-side control architectures a majority of the control events must be handled on the server side to update the state of the control. For every user event, the entire page data is sent back to the server as part of the form submission, even data that has not changed or is not affected by the user event. This article shows you how to use containers to overcome data-processing redundancy, which can otherwise drain the life out of your handheld or Web server.
|
| 4. |
Threading lightly : Reducing contention
|
|
|
While its common to hear that synchronized method calls can be 50 times as expensive as unsynchronized method calls, these numbers can actually be quite misleading. With each successive JVM version, overall performance has improved, and the cost of uncontended synchronization has been reduced, making the issue of uncontended synchronization overhead less significant. Contended synchronization, however, is quite expensive. Moreover, a high degree of contention is disastrous for scalability -- an application that had a high degree of contended synchronization will exhibit markedly worse performance as the load increases. This article explores several techniques for reducing contention, and hence improving scalability, in your programs.
|
| 5. |
Concurrency in JDK 5.0 Tutorial
|
|
|
JDK 5.0 added major new support for developing concurrent applications, including JVM changes, new low-level synchronization utilities, and higher-level, thread-safe, high-performance concurrency classes such as thread pools, concurrent collections, semaphores, latches, and barriers. Learn how these new classes can help make your code faster, more scalable, more reliable, and easier to maintain.
|
|
|
