PrintStackTrace().....is it needed at all ?

Question

class Test
public static void main(String args[])
   try
     int x=1;
     int y=0;
     int z=x/y;
   catch(Exception ex)
      System.out.println(ex);
      ex.printStackTrace();
}output:
java.lang.ArithmeticException: / by zero
java.lang.ArithmeticException: / by zero
at Test.main(Test.java:10)
note the two output message ......are not these two are same ? so whats the use of printStackTrace() ? it should be a redundant thing .....i am not clear about the use of printStackTrace() method . can anybody help me to show the difference ?

Answer 1

Have you ever created a large production system
without a single line of logging?
It's very easy to configure what to log, and not. So I
don't have to look at log records not produced by me.
You should also apply common sence to logging. Don't
log in a tight loop etc.
I've been a consultant for many years, and during that
time I have seen many enterprise applications at
different clients, but I have never seen a single
system that doesn't log information.
/KajI also have been a 'consultant' for many years. All enterprise systems I have worked on have had some form of hierarchical logging which has had to been pretty well turned off during production to stop it impacting on performance. Once logging is turned off then it does nothing to help you find problem in a production environment.
I like some form of logging but I believe that only error conditions should be logged in detail. I have had to maintain too much code that has a log statement every other line. If code is properly unit tested then most logging can be removed. If code is tested only as part of the full system test (not an uncommon occurance in the real world) then logging may be the only way it can be tested and debugged (UURGH).