随着Java 1.7的发布，现在有了使用try-with-resources块的额外选项。例如,

public class Closeable implements AutoCloseable {
    @Override
    public void close() {
        System.out.println("closing..."); 
    }
    public static void main(String[] args) {
        try (Closeable c = new Closeable()) {
            System.out.println("trying..."); 
            throw new Exception("throwing..."); 
        }
        catch (Exception e) {
            System.out.println("catching..."); 
        }
        finally {
            System.out.println("finalizing..."); 
        } 
    }
}

如果执行这个类，则在try块剩余时，在catch块和finally块执行之前，将执行c.close()。与finalize()方法不同，close()保证被执行。但是，不需要在finally子句中显式地执行它。

我完全同意其他答案，说不依赖执行的最后确定。

除了try-catch-finally块，还可以使用Runtime#addShutdownHook(在Java 1.3中引入)在程序中执行最后的清理。

这与析构函数不同，但是可以实现一个关机钩子，该钩子具有注册的侦听器对象，可以调用清理方法(关闭持久数据库连接、删除文件锁等)——这些事情通常在析构函数中完成。 同样，这不是析构函数的替代品，但在某些情况下，您可以使用它来实现所需的功能。

这样做的好处是使解构行为与程序的其余部分松散耦合。

我同意大部分答案。

你不应该完全依赖finalize或ShutdownHook

完成

The JVM does not guarantee when this finalize() method will be invoked. finalize() gets called only once by GC thread. If an object revives itself from finalizing method, then finalize will not be called again. In your application, you may have some live objects, on which garbage collection is never invoked. Any Exception that is thrown by the finalizing method is ignored by the GC thread System.runFinalization(true) and Runtime.getRuntime().runFinalization(true) methods increase the probability of invoking finalize() method but now these two methods have been deprecated. These methods are very dangerous due to lack of thread safety and possible deadlock creation.

shutdownHooks

public void addShutdownHook(Thread hook)

注册一个新的虚拟机关闭钩子。

Java虚拟机在响应两种事件时关闭:

The program exits normally, when the last non-daemon thread exits or when the exit (equivalently, System.exit) method is invoked, or The virtual machine is terminated in response to a user interrupt, such as typing ^C, or a system-wide event, such as user logoff or system shutdown. A shutdown hook is simply an initialized but non-started thread. When the virtual machine begins its shutdown sequence it will start all registered shutdown hooks in some unspecified order and let them run concurrently. When all the hooks have finished it will then run all uninvoked finalizers if finalization-on-exit has been enabled. Finally, the virtual machine will halt. Note that daemon threads will continue to run during the shutdown sequence, as will non-daemon threads if the shutdown was initiated by invoking the exit method. Shutdown hooks should also finish their work quickly. When a program invokes exit the expectation is that the virtual machine will promptly shut down and exit. But even Oracle documentation quoted that

在极少数情况下，虚拟机可能会中止，即停止运行而不完全关闭

这发生在虚拟机从外部终止时，例如在Unix上使用SIGKILL信号或在Microsoft Windows上使用TerminateProcess调用。如果本机方法出错，虚拟机也可能中止，例如破坏内部数据结构或试图访问不存在的内存。如果虚拟机中止，则不能保证是否会运行任何shutdown钩子。

结论:合理使用try{} catch{} finally{}块，释放finally(}块中的关键资源。在finally{}块中释放资源时，捕获Exception和Throwable。

Java没有任何析构函数。在Java中，它背后的主要原因是垃圾收集器总是被动地在后台工作，所有对象都在堆内存中创建，这是GC工作的地方。在c++中，我们必须显式调用delete函数，因为没有垃圾收集器之类的东西。

尽管Java的GC技术已经有了相当大的进步，但您仍然需要注意引用。我想到了许多看起来微不足道的参考模式的例子，它们实际上是罩下的老鼠窝。

从你的文章中，听起来你并不是为了对象重用而试图实现一个reset方法(真的吗?)您的对象是否持有需要清理的其他类型的资源(例如，必须关闭的流，必须返回的任何池化或借来的对象)?如果您唯一担心的是内存dealloc，那么我将重新考虑我的对象结构，并尝试验证我的对象是自包含的结构，将在GC时被清理。

随着Java 1.7的发布，现在有了使用try-with-resources块的额外选项。例如,

public class Closeable implements AutoCloseable {
    @Override
    public void close() {
        System.out.println("closing..."); 
    }
    public static void main(String[] args) {
        try (Closeable c = new Closeable()) {
            System.out.println("trying..."); 
            throw new Exception("throwing..."); 
        }
        catch (Exception e) {
            System.out.println("catching..."); 
        }
        finally {
            System.out.println("finalizing..."); 
        } 
    }
}

如果执行这个类，则在try块剩余时，在catch块和finally块执行之前，将执行c.close()。与finalize()方法不同，close()保证被执行。但是，不需要在finally子句中显式地执行它。