2010-06-03 125 views
37

的问题很简单,我想读的异常的全堆栈跟踪,我捕捉:)如何打印完整的堆栈跟踪Java中

例如:

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot load JDBC driver class 'com.ibm.db2.jcc.DB2Driver' 
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136) 
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) 
at com.azurian.lce.usuarios.ConnectionManager.getConnection(ConnectionManager.java:65) 
at com.azurian.lce.usuarios.db2.UsuarioDAOImpl.autenticar(UsuarioDAOImpl.java:101) 
at com.azurian.lce.usuarios.UsuarioServiceImpl.autenticar(UsuarioServiceImpl.java:31) 
at com.azurian.lce.web.admin.actions.LoginAction.execute(LoginAction.java:49) 
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) 
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) 
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) 
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) 
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) 
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) 
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) 
at java.lang.Thread.run(Unknown Source) 
Caused by: java.lang.ClassNotFoundException: COM.ibm.db2.jcc.DB2Driver 
at java.net.URLClassLoader$1.run(Unknown Source) 
at java.security.AccessController.doPrivileged(Native Method) 
at java.net.URLClassLoader.findClass(Unknown Source) 
at java.lang.ClassLoader.loadClass(Unknown Source) 
at java.lang.ClassLoader.loadClass(Unknown Source) 
at java.lang.ClassLoader.loadClassInternal(Unknown Source) 
at java.lang.Class.forName0(Native Method) 
at java.lang.Class.forName(Unknown Source) 
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130) 
... 23 more 

(我想读“...... 23多个”)

问候:)

+2

Gahhhh ......如此多的运行和进程,调用和执行以及DOS ... http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns。 html – naiad 2010-06-03 22:57:38

+1

请参阅:http://stackoverflow.com/questions/1167888/howto-increase-lines-of-java-stack-trace-dump和 http://stackoverflow.com/questions/1043378/print-full-call -stack-on-printstacktrace和 http://stackoverflow.com/questions/437756/how-do-i-stop-stacktraces-truncating-in-logs只列出几个 – akf 2010-06-03 23:18:18

+0

嗨! 看看http://people.inf.elte.hu/balopat/bug.html我生成了你,将鼠标悬停在圆圈上,我希望它能帮助你理解'... 23更多'的意思:) 基本上答案是真的,这只是一个例证。 – 2010-06-22 14:56:47

回答

29

答案很简单,那些线已经在堆栈跟踪:)

at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) 
at com.azurian.lce.usuarios.ConnectionManager.getConnection(ConnectionManager.java:65) 
at com.azurian.lce.usuarios.db2.UsuarioDAOImpl.autenticar(UsuarioDAOImpl.java:101) 
at com.azurian.lce.usuarios.UsuarioServiceImpl.autenticar(UsuarioServiceImpl.java:31) 
at com.azurian.lce.web.admin.actions.LoginAction.execute(LoginAction.java:49) 
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) 
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) 
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) 
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) 
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:852) 
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) 
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) 
at java.lang.Thread.run(Unknown Source) 

基本上,以下是发生在BasicDataSource#createDataSource()

try { 
    Class.forName(driverClassName); // Line 1130 
} catch (ClassNotFoundException e) { 
    throw new SQLNestedException(e, "Cannot load JDBC driver class '" + driverClassName + "'"); // Line 1136 
} 
+1

怎么样? [....] – OscarRyz 2010-06-03 22:59:05

+0

嗯,现在当很长一段时间过去了,我读到答案非常简单,这是一个瓶子问题(或者在这种情况下,它缺少DB2驱动程序的jar,它在: “引起:java.lang.ClassNotFoundException:COM.ibm.db2.jcc.DB2Driver” – 2013-08-27 12:35:43

+1

对我来说,这并不回答这个问题。是的,这些行已经在堆栈跟踪中,但它们没有被打印出来! 如何打印出来是一个问题,你根本没有回答! – plainOldNerd 2017-05-17 18:54:43

24

BalusC是正确的。在这里看到:http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Throwable.html#printStackTrace()

特别是:

注含 字符线的存在 “...”。这些线 表明 堆栈跟踪此例外的其余部分相匹配 从 ,其通过本 异常(以下简称“封闭”的异常)引起的异常 的堆栈跟踪底部的指示的数量的帧。 此速记可以极大地减少 常见的 情况下的输出长度,其中包装的例外是 ,与 引发的“引发异常”相同。

这意味着在你的例子是:

BasicDataSource.java线1136抓到扔在行1130 ClassNotFoundException并重新抛出它作为一个SQLNestedException。因此,ClassNotFoundException的堆栈跟踪的其余部分与上面的SQLNestedException相匹配,并且stacktrace以更简洁的格式打印。

7

当外部异常(SQLNestedException)包装内部异常(ClassNotFoundError)时,它们位于同一个线程中,因此共享一个公共基址到它们的堆栈跟踪中。

(23更多...)显示了公共堆栈启动内部异常的位置,这也是引发外部异常的地方。所以,无论何时你看到(XX more ......),只要看看上面的异常就可以看到堆栈跟踪的其余部分。

如果您想以编程方式打印出没有常见曲线省略号的堆栈轨迹,那么您可以使用Throwable.getStackTrace()并自行打印出所有元素。

+0

感谢所有的答案:)它帮助了我很多(了解它正在发生什么,我正在做的程序) 关于 – 2010-06-04 13:47:36

4

试试看。该逻辑遍历主异常及其所有原因,直到没有其他原因(cause == null)需要处理。这样你就可以避免23个以上的信息。我还没有测试过,但我相信这应该适合你。

顺便说一句 - logWriter是一个缓冲作家。您可能想要使用System.out.print或任何其他日志记录API。

public static void debugError(final String message, final Throwable th) { 
    final String logMessage = "[ERROR] - " + message; 

    try { 
     logWriter.write(logMessage); 
     logWriter.newLine(); 

     // dump exception stack if specified 
     if (null != th) { 
      final StackTraceElement[] traces = th.getStackTrace(); 
      if (null != traces && traces.length > 0) { 
       logWriter.write(th.getClass() + ": " + th.getMessage()); 
       logWriter.newLine(); 

       for (final StackTraceElement trace : traces) { 
        logWriter.write(" at " + trace.getClassName() + '.' + trace.getMethodName() + '(' + trace.getFileName() + ':' + trace.getLineNumber() + ')'); 
        logWriter.newLine(); 
       } 
      } 

      Throwable cause = th.getCause(); 
      while (null != cause) { 
       final StackTraceElement[] causeTraces = cause.getStackTrace(); 
       if (null != causeTraces && causeTraces.length > 0) { 
        logWriter.write("Caused By:"); 
        logWriter.newLine(); 
        logWriter.write(cause.getClass() + ": " + cause.getMessage()); 
        logWriter.newLine(); 

        for (final StackTraceElement causeTrace : causeTraces) { 
         logWriter.write(" at " + causeTrace.getClassName() + '.' + causeTrace.getMethodName() + '(' + causeTrace.getFileName() + ':' + causeTrace.getLineNumber() + ')'); 
         logWriter.newLine(); 
        } 
       } 

       // fetch next cause 
       cause = cause.getCause(); 
      } 
     } 
    } catch (final IOException ex) { 
     System.err.println(logMessage); 

     if (null != th) { 
      th.printStackTrace(); 
     } 
    } 
} 
+0

您可以使用'Reader'来读取'printStackTrace'输出,直到它遇到_Caused by_,然后得到原因并打印它的堆栈跟踪(寻找下一个_由_引起)...并递归地重复这个过程直到出现不再有堆栈痕迹。这样你就不必建立你自己的定制堆栈跟踪格式化程序 - 你可以使用已有的':)' – ADTC 2013-08-27 10:28:21

+0

你的代码运行良好。 要发送跟踪到system.out,我只需添加 'BufferedWriter logWriter = new BufferedWriter(new OutputStreamWriter(System.out));' 并在结尾: 'logWriter.flush();' – Ben 2018-02-27 16:44:56