Class DevUtils

java.lang.Object
org.archive.util.DevUtils
public class DevUtils extends Object
Write a message and stack trace to the 'org.archive.util.DevUtils' logger.
Version:
$Revision$ $Date$
Author:
gojomo

  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    static Logger
    logger
     

  • Constructor Summary

    Constructors
    Constructor
    Description
    DevUtils()
     

  • Method Summary

    Modifier and Type
    Method
    Description
    static String
    extraInfo()
     
    static void
    sigquitSelf()
    Send this JVM process a SIGQUIT; giving a thread dump and possibly a heap histogram (if using -XX:+PrintClassHistogram).
    static void
    warnHandle(Throwable ex, String note)
    Log a warning message to the logger 'org.archive.util.DevUtils' made of the passed 'note' and a stack trace based off passed exception.

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

  • Field Details

    • logger

      public static Logger logger

  • Constructor Details

    • DevUtils

      public DevUtils()

  • Method Details

    • warnHandle

      public static void warnHandle(Throwable ex, String note)
      Log a warning message to the logger 'org.archive.util.DevUtils' made of the passed 'note' and a stack trace based off passed exception.
      Parameters:
      ex - Exception we print a stacktrace on.
      note - Message to print ahead of the stacktrace.

    • extraInfo

      public static String extraInfo()
      Returns:
      Extra information gotten from current Thread. May not always be available in which case we return empty string.

    • sigquitSelf

      public static void sigquitSelf()
      Send this JVM process a SIGQUIT; giving a thread dump and possibly a heap histogram (if using -XX:+PrintClassHistogram). Used to automatically dump info, for example when a serious error is encountered. Would use 'jmap'/'jstack', but have seen JVM lockups -- perhaps due to lost thread wake signals -- when using those against Sun 1.5.0+03 64bit JVM.