The recent CCE problem was only evident in the stdout
log -- because it involved an uncaught runtime
exception (CCE) which triggered default behavior (dump
stack, end execution of that thread).
These should be caught and noted in the UI somehow.
(Additionally, looking at the Thread report gives no
indication that the threads are completely dead, rather
than just hung, because the state consulted for that
report is all still around. We probably need to add an
isAlive() check to that report -- and the general
thread-status assessment.)
Nobody/Anonymous
None
None
Public
|
Date: 2007-03-14 00:14
|
|
Date: 2004-10-14 18:36 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2004-10-14 18:35 | stack-sf |
| resolution_id | None | 2004-10-14 18:35 | stack-sf |
| close_date | - | 2004-10-14 18:35 | stack-sf |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use