If you're saving Java Exception information in the DB, what parts of the Exception should you save to help figure out the problem without redundancy? -



If you're saving Java Exception information in the DB, what parts of the Exception should you save to help figure out the problem without redundancy? -

which parts of java.lang.exception object need saved in database give best chance of recreating problem led exception beingness thrown?

and parts, if saved together, create redundant information?

for example, if save result of calling exception.getmessage(), , save exception.getcause().getmessage(), end duplicate information?

and, if save exception.getmessage, redundant save output exception.printstacktrace()?

my strategy save timestamp , stack trace of exception.

that of import thing needed seek diagnose problem provoked exception.

java exception-handling

Comments

Popular posts from this blog

iphone - Dismissing a UIAlertView -

intellij idea - Update external libraries with intelij and java -

javascript - send data from a new window to previous window in php -