你也可以使用异常来打印堆栈，而不是痛苦地输入新的行字符:

Exception e = new Exception();
e.setStackTrace(Thread.currentThread().getStackTrace());
loggr.info(e);

在Java 9中有一种新的方法:

public static void showTrace() {

  List<StackFrame> frames =
    StackWalker.getInstance( Option.RETAIN_CLASS_REFERENCE )
               .walk( stream  -> stream.collect( Collectors.toList() ) );

  for ( StackFrame stackFrame : frames )
    System.out.println( stackFrame );
}

如果希望检查进程的当前调用堆栈，可以使用jstack实用程序。

Usage:
    jstack [-l] <pid>
        (to connect to running process)
    jstack -F [-m] [-l] <pid>
        (to connect to a hung process)
    jstack [-m] [-l] <executable> <core>
        (to connect to a core file)
    jstack [-m] [-l] [server_id@]<remote server IP or hostname>
        (to connect to a remote debug server)

Options:
    -F  to force a thread dump. Use when jstack <pid> does not respond (process is hung)
    -m  to print both java and native frames (mixed mode)
    -l  long listing. Prints additional information about locks
    -h or -help to print this help message

也许你可以试试这个:

catch(Exception e)
{
    StringWriter writer = new StringWriter();
    PrintWriter pw = new PrintWriter(writer);
    e.printStackTrace(pw);
    String errorDetail = writer.toString();
}

字符串'errorDetail'包含了堆栈跟踪。

我真傻，它是Thread.currentThread().getStackTrace();

托尼，作为对公认答案的评论，给出了似乎是最好的答案，实际上回答了OP的问题:

Arrays.toString(Thread.currentThread().getStackTrace()).replace( ',', '\n' );

．.． OP没有询问如何从异常的堆栈跟踪中获取字符串。尽管我是Apache Commons的忠实粉丝，但当有像上面这么简单的东西时，使用外部库是没有逻辑理由的。