欧美bbbwbbbw肥妇,免费乱码人妻系列日韩,一级黄片

Java如何自定義異常打印非堆棧信息詳解

 更新時間:2018年04月19日 10:33:07   作者:Charse  
這篇文章主要給大家介紹了關(guān)于Java如何自定義異常打印非堆棧信息的相關(guān)資料,文中通過示例代碼介紹的非常詳細(xì),對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友們下面隨著小編來一起學(xué)習(xí)學(xué)習(xí)吧。

前言

在學(xué)習(xí)Java的過程中,想必大家都一定學(xué)習(xí)過異常這個篇章,異常的基本特性和使用這里就不再多講了。什么是異常?我不知道大家都是怎么去理解的,我的理解很簡單,那就是不正常的情況,比如我現(xiàn)在是個男的,但是我卻有著女人所獨(dú)有的東西,在我看來這尼瑪肯定是種異常,簡直不能忍。想必大家都能夠理解看懂,并正確使用。

但是,光學(xué)會基本異常處理和使用不夠的,在工作中出現(xiàn)異常并不可怕,有時候是需要使用異常來驅(qū)動業(yè)務(wù)的處理,例如: 在使用唯一約束的數(shù)據(jù)庫的時候,如果插入一條重復(fù)的數(shù)據(jù),那么可以通過捕獲唯一約束異常DuplicateKeyException來進(jìn)行處理,這個時候,在server層中就可以向調(diào)用層拋出對應(yīng)的狀態(tài),上層根據(jù)對應(yīng)的狀態(tài)再進(jìn)行處理,所以有時候異常對業(yè)務(wù)來說,是一個驅(qū)動方式。

有的捕獲異常之后會將異常進(jìn)行輸出,不知道細(xì)心的同學(xué)有沒有注意到一點(diǎn),輸出的異常是什么東西呢?

下面來看一個常見的異常:

java.lang.ArithmeticException: / by zero
 at greenhouse.ExceptionTest.testException(ExceptionTest.java:16)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
 at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
 at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)

一個空指針異常:

java.lang.NullPointerException
 at greenhouse.ExceptionTest.testException(ExceptionTest.java:16)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
 at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
 at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)

大家有沒有發(fā)現(xiàn)一個特點(diǎn),就是異常的輸出是中能夠精確的輸出異常出現(xiàn)的地點(diǎn),還有后面一大堆的執(zhí)行過程類調(diào)用,也都打印出來了,這些信息從哪兒來呢? 這些信息是從棧中獲取的,在打印異常日志的時候,會從棧中去獲取這些調(diào)用信息。能夠精確的定位異常出現(xiàn)的異常當(dāng)然是好,但是我們有時候考慮到程序的性能,以及一些需求時,我們有時候并不需要完全的打印這些信息,并且去方法調(diào)用棧中獲取相應(yīng)的信息,是有性能消耗的,對于一些性能要求高的程序,我們完全可以在這一個方面為程序性能做一個提升。

所以如何避免輸出這些堆棧信息呢? 那么自定義異常就可以解決這個問題:

首先,自動異常需要繼承RuntimeException, 然后,再通過是重寫fillInStackTrace, toString 方法, 例如,下面我定義一個AppException異常:

package com.green.monitor.common.exception;
import java.text.MessageFormat;
/**
 * 自定義異常類
 */
public class AppException extends RuntimeException {
 private boolean isSuccess = false;
 private String key;
 private String info;
 public AppException(String key) {
 super(key);
 this.key = key;
 this.info = key;
 }
 public AppException(String key, String message) {
 super(MessageFormat.format("{0}[{1}]", key, message));
 this.key = key;
 this.info = message;
 }
 public AppException(String message, String key, String info) {
 super(message);
 this.key = key;
 this.info = info;
 }
 public boolean isSuccess() {
 return isSuccess;
 }
 public String getKey() {
 return key;
 }
 public void setKey(String key) {
 this.key = key;
 }
 public String getInfo() {
 return info;
 }
 public void setInfo(String info) {
 this.info = info;
 }
 @Override
 public Throwable fillInStackTrace() {
 return this;
 }
 @Override
 public String toString() {
 return MessageFormat.format("{0}[{1}]",this.key,this.info);
 }
}

那么為什么要重寫fillInStackTrace, 和 toString 方法呢? 我們首先來看源碼是怎么一回事.

public class RuntimeException extends Exception {
 static final long serialVersionUID = -7034897190745766939L;
 /** Constructs a new runtime exception with <code>null</code> as its
 * detail message. The cause is not initialized, and may subsequently be
 * initialized by a call to {@link #initCause}.
 */
 public RuntimeException() {
 super();
 }
 /** Constructs a new runtime exception with the specified detail message.
 * The cause is not initialized, and may subsequently be initialized by a
 * call to {@link #initCause}.
 *
 * @param message the detail message. The detail message is saved for 
 *  later retrieval by the {@link #getMessage()} method.
 */
 public RuntimeException(String message) {
 super(message);
 }
 /**
 * Constructs a new runtime exception with the specified detail message and
 * cause. <p>Note that the detail message associated with
 * <code>cause</code> is <i>not</i> automatically incorporated in
 * this runtime exception's detail message.
 *
 * @param message the detail message (which is saved for later retrieval
 *  by the {@link #getMessage()} method).
 * @param cause the cause (which is saved for later retrieval by the
 *  {@link #getCause()} method). (A <tt>null</tt> value is
 *  permitted, and indicates that the cause is nonexistent or
 *  unknown.)
 * @since 1.4
 */
 public RuntimeException(String message, Throwable cause) {
 super(message, cause);
 }
 /** Constructs a new runtime exception with the specified cause and a
 * detail message of <tt>(cause==null ? null : cause.toString())</tt>
 * (which typically contains the class and detail message of
 * <tt>cause</tt>). This constructor is useful for runtime exceptions
 * that are little more than wrappers for other throwables.
 *
 * @param cause the cause (which is saved for later retrieval by the
 *  {@link #getCause()} method). (A <tt>null</tt> value is
 *  permitted, and indicates that the cause is nonexistent or
 *  unknown.)
 * @since 1.4
 */
 public RuntimeException(Throwable cause) {
 super(cause);
 } 
}

RuntimeException是繼承Exception,但是它里面去只是調(diào)用了父類的方法,本身是沒有做什么其余的操作。那么繼續(xù)看Exception里面是怎么回事呢?

public class Exception extends Throwable {
 static final long serialVersionUID = -3387516993124229948L;
 /**
 * Constructs a new exception with <code>null</code> as its detail message.
 * The cause is not initialized, and may subsequently be initialized by a
 * call to {@link #initCause}.
 */
 public Exception() {
 super();
 }
 /**
 * Constructs a new exception with the specified detail message. The
 * cause is not initialized, and may subsequently be initialized by
 * a call to {@link #initCause}.
 *
 * @param message the detail message. The detail message is saved for 
 *  later retrieval by the {@link #getMessage()} method.
 */
 public Exception(String message) {
 super(message);
 }
 /**
 * Constructs a new exception with the specified detail message and
 * cause. <p>Note that the detail message associated with
 * <code>cause</code> is <i>not</i> automatically incorporated in
 * this exception's detail message.
 *
 * @param message the detail message (which is saved for later retrieval
 *  by the {@link #getMessage()} method).
 * @param cause the cause (which is saved for later retrieval by the
 *  {@link #getCause()} method). (A <tt>null</tt> value is
 *  permitted, and indicates that the cause is nonexistent or
 *  unknown.)
 * @since 1.4
 */
 public Exception(String message, Throwable cause) {
 super(message, cause);
 }
 /**
 * Constructs a new exception with the specified cause and a detail
 * message of <tt>(cause==null ? null : cause.toString())</tt> (which
 * typically contains the class and detail message of <tt>cause</tt>).
 * This constructor is useful for exceptions that are little more than
 * wrappers for other throwables (for example, {@link
 * java.security.PrivilegedActionException}).
 *
 * @param cause the cause (which is saved for later retrieval by the
 *  {@link #getCause()} method). (A <tt>null</tt> value is
 *  permitted, and indicates that the cause is nonexistent or
 *  unknown.)
 * @since 1.4
 */
 public Exception(Throwable cause) {
 super(cause);
 }
}

從源碼中可以看到, Exception里面也是直接調(diào)用了父類的方法,和RuntimeException一樣,自己其實(shí)并沒有做什么。 那么直接來看Throwable里面是怎么一回事:

public class Throwable implements Serializable {
 public Throwable(String message) {
 fillInStackTrace();
 detailMessage = message;
 }
 
 /**
 * Fills in the execution stack trace. This method records within this
 * <code>Throwable</code> object information about the current state of
 * the stack frames for the current thread.
 *
 * @return a reference to this <code>Throwable</code> instance.
 * @see java.lang.Throwable#printStackTrace()
 */
 public synchronized native Throwable fillInStackTrace();
 
 /**
 * Provides programmatic access to the stack trace information printed by
 * {@link #printStackTrace()}. Returns an array of stack trace elements,
 * each representing one stack frame. The zeroth element of the array
 * (assuming the array's length is non-zero) represents the top of the
 * stack, which is the last method invocation in the sequence. Typically,
 * this is the point at which this throwable was created and thrown.
 * The last element of the array (assuming the array's length is non-zero)
 * represents the bottom of the stack, which is the first method invocation
 * in the sequence.
 *
 * <p>Some virtual machines may, under some circumstances, omit one
 * or more stack frames from the stack trace. In the extreme case,
 * a virtual machine that has no stack trace information concerning
 * this throwable is permitted to return a zero-length array from this
 * method. Generally speaking, the array returned by this method will
 * contain one element for every frame that would be printed by
 * <tt>printStackTrace</tt>.
 *
 * @return an array of stack trace elements representing the stack trace
 *  pertaining to this throwable.
 * @since 1.4
 */
 public StackTraceElement[] getStackTrace() {
 return (StackTraceElement[]) getOurStackTrace().clone();
 }
 private synchronized StackTraceElement[] getOurStackTrace() {
 // Initialize stack trace if this is the first call to this method
 if (stackTrace == null) {
  int depth = getStackTraceDepth();
  stackTrace = new StackTraceElement[depth];
  for (int i=0; i < depth; i++)
  stackTrace[i] = getStackTraceElement(i);
 }
 return stackTrace;
 }
 
 /**
 * Returns the number of elements in the stack trace (or 0 if the stack
 * trace is unavailable).
 *
 * package-protection for use by SharedSecrets.
 */
 native int getStackTraceDepth();
 /**
 * Returns the specified element of the stack trace.
 *
 * package-protection for use by SharedSecrets.
 *
 * @param index index of the element to return.
 * @throws IndexOutOfBoundsException if <tt>index &lt; 0 ||
 *  index &gt;= getStackTraceDepth() </tt>
 */
 native StackTraceElement getStackTraceElement(int index);
 
 /**
 * Returns a short description of this throwable.
 * The result is the concatenation of:
 * <ul>
 * <li> the {@linkplain Class#getName() name} of the class of this object
 * <li> ": " (a colon and a space)
 * <li> the result of invoking this object's {@link #getLocalizedMessage}
 * method
 * </ul>
 * If <tt>getLocalizedMessage</tt> returns <tt>null</tt>, then just
 * the class name is returned.
 *
 * @return a string representation of this throwable.
 */
 public String toString() {
 String s = getClass().getName();
 String message = getLocalizedMessage();
 return (message != null) ? (s + ": " + message) : s;
 }

從源碼中可以看到,到Throwable就幾乎到頭了, 在fillInStackTrace() 方法是一個native方法,這方法也就是會調(diào)用底層的C語言,返回一個Throwable對象, toString 方法,返回的是throwable的簡短描述信息, 并且在getStackTrace 方法和 getOurStackTrace 中調(diào)用的都是native方法getStackTraceElement, 而這個方法是返回指定的棧元素信息,所以這個過程肯定是消耗性能的,那么我們自定義異常中的重寫toString方法和fillInStackTrace方法就可以不從棧中去獲取異常信息,直接輸出,這樣對系統(tǒng)和程序來說,相對就沒有那么”重”, 是一個優(yōu)化性能的非常好的辦法。那么如果出現(xiàn)自定義異常那么是什么樣的呢?請看下面吧:

@Test
 public void testException(){
 try {
 String str =null;
 System.out.println(str.charAt(0));
 }catch (Exception e){
 throw new AppException("000001","空指針異常");
 }
 }

那么在異常異常的時候,系統(tǒng)將會打印我們自定義的異常信息:

000001[空指針異常]
Process finished with exit code -1

所以特別簡潔,優(yōu)化了系統(tǒng)程序性能,讓程序不這么“重”, 所以對于性能要求特別要求的系統(tǒng)。趕緊自己的自定義異常吧!

總結(jié)

以上就是這篇文章的全部內(nèi)容了,希望本文的內(nèi)容對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,如果有疑問大家可以留言交流,謝謝大家對腳本之家的支持。

相關(guān)文章

  • Java并發(fā)編程this逃逸問題總結(jié)

    Java并發(fā)編程this逃逸問題總結(jié)

    本篇文章給大家詳細(xì)分析了Java并發(fā)編程this逃逸的問題分享,對此有需要的朋友參考下。
    2018-02-02
  • JavaWeb動態(tài)導(dǎo)出Excel可彈出下載

    JavaWeb動態(tài)導(dǎo)出Excel可彈出下載

    這篇文章主要介紹了JavaWeb動態(tài)導(dǎo)出Excel,對Excel可彈出進(jìn)行下載操作,感興趣的小伙伴們可以參考一下
    2016-03-03
  • 解決java maven項(xiàng)目找不到j(luò)console-1.8.0.jar和tools-1.8.0.jar包問題

    解決java maven項(xiàng)目找不到j(luò)console-1.8.0.jar和tools-1.8.0.jar包問題

    這篇文章主要介紹了解決java maven項(xiàng)目找不到j(luò)console-1.8.0.jar和tools-1.8.0.jar包問題,具有很好的參考價值,希望對大家有所幫助。一起跟隨小編過來看看吧
    2020-08-08
  • Spring?Session(分布式Session共享)實(shí)現(xiàn)示例

    Spring?Session(分布式Session共享)實(shí)現(xiàn)示例

    這篇文章主要介紹了Spring?Session(分布式Session共享)實(shí)現(xiàn)示例,文章內(nèi)容詳細(xì),需要的朋友可以參考下
    2023-01-01
  • Springboot webscoket自定義定時器

    Springboot webscoket自定義定時器

    這篇文章主要介紹了Springboot webscoket自定義定時器問題,總的來說這并不是一道難題,那為什么要拿出這道題介紹?拿出這道題真正想要傳達(dá)的是解題的思路,以及不斷優(yōu)化探尋最優(yōu)解的過程。希望通過這道題能給你帶來一種解題優(yōu)化的思路
    2023-01-01
  • Mybatis中TypeAliasRegistry的作用及使用方法

    Mybatis中TypeAliasRegistry的作用及使用方法

    Mybatis中的TypeAliasRegistry是一個類型別名注冊表,它的作用是為Java類型建立別名,使得在Mybatis配置文件中可以使用別名來代替完整的Java類型名。使用TypeAliasRegistry可以簡化Mybatis配置文件的編寫,提高配置文件的可讀性和可維護(hù)性
    2023-05-05
  • SpringMVC學(xué)習(xí)之JSTL條件行為和遍歷行為詳解

    SpringMVC學(xué)習(xí)之JSTL條件行為和遍歷行為詳解

    這篇文章主要介紹了SpringMVC學(xué)習(xí)之JSTL條件行為和遍歷行為詳解,具有很好的參考價值,希望對大家有所幫助。如有錯誤或未考慮完全的地方,望不吝賜教
    2021-08-08
  • Windows下后端如何啟動SpringBoot的Jar項(xiàng)目

    Windows下后端如何啟動SpringBoot的Jar項(xiàng)目

    這篇文章主要介紹了Windows下后端如何啟動SpringBoot的Jar項(xiàng)目問題,具有很好的參考價值,希望對大家有所幫助,如有錯誤或未考慮完全的地方,望不吝賜教
    2024-07-07
  • 簡述Java List去重五種方法

    簡述Java List去重五種方法

    這篇文章主要介紹了簡述Java List去重五種方法,文中通過示例代碼介紹的非常詳細(xì),對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友們下面隨著小編來一起學(xué)習(xí)學(xué)習(xí)吧
    2020-01-01
  • Spring boot配置多數(shù)據(jù)源代碼實(shí)例

    Spring boot配置多數(shù)據(jù)源代碼實(shí)例

    這篇文章主要介紹了Spring boot配置多數(shù)據(jù)源代碼實(shí)例,文中通過示例代碼介紹的非常詳細(xì),對大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價值,需要的朋友可以參考下
    2020-07-07

最新評論