classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view


Mark Whitlock

Sorry for using the jargon. Yes, FFDC is First Failure Data Capture. The
idea behind it is that if Axis C++ fails due to a bug in the code or a
system problem (like running out of memory) it should fail cleanly and
leave behind enough diagnostics so that someone can work out what happened.
This is especially important for intermittent or difficult-to-reproduce
bugs where it is impossible to debug them using a debugger or even trace.
FFDC is not really about application errors or user errors which are
reported effectively using exceptions already. FFDC is similar to assert()
in C.

Someone will probably explain this better than I,
Mark Whitlock

----- Forwarded by Mark Whitlock/UK/IBM on 13/05/2005 17:19 -----
             <Lilantha.Darshan                                          To
             [hidden email]>             "Apache AXIS C Developers List"    
                                       <[hidden email]>          
             13/05/2005 17:12                                           cc
             Please respond to         RE: FFDC                            
              "Apache AXIS C                                              
             Developers List"                                              

I'm also wondering what it is? :)

I can find this on googling: First Failure Data Capture (FFDC) - Is this
an IBM s/w?
Or available as an open source lib/tools etc?

-----Original Message-----
From: Davanum Srinivas [mailto:[hidden email]]
Sent: Friday, May 13, 2005 7:17 AM
To: Apache AXIS C Developers List
Subject: Re: FFDC

what's FFDC? :)

-- dims

On 5/13/05, John Hawkins <[hidden email]> wrote:

> Hi Folks,
> time to discuss FFDC again :-)
> We'd really like to see FFDC being used in the code. Here are some
> thoughts....
> FFDC is meant to be used in areas where the exception was completely
> unexpected. In WebSphere application server FFDC consists of two
> 1.        The Object Stack
> is a list of "useful things to have" so that when an FFDC situation
> the FFDC handler has some information as to what state objects were in
> to the Failure. This system is only as good as the information given
put on
> the stack and relies on developers putting the appropriate objects to
> stack.
> 2.        FFDC at every exception
> Websphere application server originally expected every exception to
have an
> FFDC record output. This led to situations where FFDC was being
produced and
> the exception was being thrown back up the stack. The next catcher
> then produce more FFDC. This is obviously not a good system.
> I don't believe that it's possible to automate the putting in of FFDC
> that it's a completely manual process - thoughts?
> Does everyone agree that we should have the Object stack or do we just
> an FFDC API only? I think the Object stack would be a good idea in
> circumstances - it does require that you know the code-paths (and
> respective entry points). However, we really only have a couple of

> paths so it should be fairly obvious?
> Does anyone have any thoughts on the API?
> thoughts please?
> cheers,
> John.

Davanum Srinivas - http://webservices.apache.org/~dims/

Visit www.siebel.com

This e-mail message is for the sole use of the intended recipient(s) and
contains confidential and/or privileged information belonging to Siebel
Systems, Inc. or its customers or partners. Any unauthorized review, use,
copying, disclosure or distribution of this message is strictly prohibited.
If you are not an intended recipient of this message, please contact the
sender by reply e-mail and destroy all soft and hard copies of the message
and any attachments. Thank you for your cooperation.