You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jim Hurley (JIRA)" <ji...@apache.org> on 2007/07/25 23:46:31 UTC
[jira] Created: (RIVER-38) Mechanism desired for suspending
activity in a space for debugging purposes
Mechanism desired for suspending activity in a space for debugging purposes
---------------------------------------------------------------------------
Key: RIVER-38
URL: https://issues.apache.org/jira/browse/RIVER-38
Project: River
Issue Type: Improvement
Components: com_sun_jini_outrigger
Affects Versions: jtsk_1.2
Reporter: Jim Hurley
Priority: Minor
Bugtraq ID [4616144|http:/bugs.sun.com/bugdatabase/view_bug.do?bug_id=4616144]
A mechanism for suspending activity in a Space (stopping any state
changes within the Space) should be available for use during debugging.
Should there be a fatal error, corruption, or invalid state detected
within the Space, the ability to suspend any activity that would
just "muddy" the facts and interfere with debugging and analysis
would be highly desirable. Such a mechanism might also be made available
in the field to be used in conjuction with a durable Space dump utility
for post-mortem analysis.A mechanism for suspending activity in a Space (stopping any state
changes within the Space) should be available for use during debugging.
Should there be a fatal error, corruption, or invalid state detected
within the Space, the ability to suspend any activity that would
just "muddy" the facts and interfere with debugging and analysis
would be highly desirable. Such a mechanism might also be made available
in the field to be used in conjuction with a durable Space dump utility
for post-mortem analysis.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.