HIbernate 不会抛出异常或显示错误

HIbernate doesn't throw exception or show errors

我正在使用 Jersey 和 Hibernate 开发小型 REST Web 服务器。在此过程中,我遇到了一些代表 Hibernate 的奇怪行为。即,在 POST 从 curl 请求后尝试 Session.save() 一个对象时,服务器回复 500,但我在命令 window.[=14 中没有看到任何错误=]

但是,当我切换断点并越过光标时,光标会在依赖项中的某些 jar 中运行,最终我会在其中找到错误消息。它仍然没有在任何地方显示它。

如何强制休眠显示所有这些错误?还是需要设置Jersey?

我切换断点的方法:

@POST
@Path("{id}/comments/new")
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public Response handlePostNewComment(@PathParam("id") int taskId, ItemComment newComment) {
    newComment.setItemId(taskId);
    Session s = HibernateUtil.getSessionFactory().openSession();
    Transaction tx = s.beginTransaction();
    **Integer newCommentId = (Integer)s.save(newComment);**
    s.flush();
    tx.commit();
    s.close();
    HashMap res = new HashMap();
    res.put("id", newCommentId);
    return Response.status(201).entity(res).build();
}

服务器对 curl 的响应:

$ curl -i -X POST -H "Content-type: application/json" --data @comm.json localhost:8000/task/19/comments/new

HTTP/1.1 500 Request failed. Content-Type: text/html;charset=ISO-8859-1 Date: Tue, 27 Oct 2015 20:34:16 GMT Connection: close Content-Length: 1033

IntelliJ 控制台中的消息:

Connected to the target VM, address: '127.0.0.1:57501', transport: 'socket'
task tracker enterprise Edition running
Oct 27, 2015 9:34:12 PM org.glassfish.grizzly.http.server.NetworkListener start
INFO: Started listener bound to [localhost:8000]
Application started.
Stop the application using CTRL+C
Oct 27, 2015 9:34:12 PM org.glassfish.grizzly.http.server.HttpServer start
INFO: [HttpServer] Started.
Oct 27, 2015 9:34:14 PM org.hibernate.Version logVersion
INFO: HHH000412: Hibernate Core {5.0.2.Final}
Oct 27, 2015 9:34:14 PM org.hibernate.cfg.Environment <clinit>
INFO: HHH000206: hibernate.properties not found
Oct 27, 2015 9:34:14 PM org.hibernate.cfg.Environment buildBytecodeProvider
INFO: HHH000021: Bytecode provider name : javassist
Oct 27, 2015 9:34:14 PM org.hibernate.annotations.common.reflection.java.JavaReflectionManager <clinit>
INFO: HCANN000001: Hibernate Commons Annotations {5.0.0.Final}
Oct 27, 2015 9:34:14 PM org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
WARN: HHH000402: Using Hibernate built-in connection pool (not for production use!)
Oct 27, 2015 9:34:14 PM org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl buildCreator
INFO: HHH000401: using driver [org.postgresql.Driver] at URL [jdbc:postgresql://localhost:5432/tracker]
Oct 27, 2015 9:34:14 PM org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl buildCreator
INFO: HHH000046: Connection properties: {user=cristian, password=****}
Oct 27, 2015 9:34:14 PM org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl buildCreator
INFO: HHH000006: Autocommit mode: false
Oct 27, 2015 9:34:14 PM org.hibernate.engine.jdbc.connections.internal.DriverManagerConnectionProviderImpl configure
INFO: HHH000115: Hibernate connection pool size: 1 (min=1)
Oct 27, 2015 9:34:14 PM org.hibernate.dialect.Dialect <init>
INFO: HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL94Dialect
Oct 27, 2015 9:34:15 PM org.hibernate.engine.jdbc.env.internal.LobCreatorBuilderImpl useContextualLobCreation
INFO: HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
Oct 27, 2015 9:34:15 PM org.hibernate.type.BasicTypeRegistry register
INFO: HHH000270: Type registration [java.util.UUID] overrides previous : org.hibernate.type.UUIDBinaryType@43aa6671
Oct 27, 2015 9:34:15 PM org.hibernate.hql.internal.QueryTranslatorFactoryInitiator initiateService
INFO: HHH000397: Using ASTQueryTranslatorFactory

它在成功请求时看起来是一样的,除了一些 SQL 从休眠回显。

在调试时我终于在 org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher class

的某个地方遇到了异常

java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer

这已经发生了好几次,错误信息各不相同。

我该怎么做才能强制这些组件在 stdout 或 stderr 上向我显示错误消息?或者将它们记录在某处?

这种情况我就注册一个ExceptionMapper<Throwable>。这些用于将异常映射到 Responses。有时存在未处理的异常,Jersey 会吞下它,向客户端发送有时无用的 500 服务器错误。在这些情况下,ExceptionMapper 将允许我们自己处理它,至少在发送响应之前打印堆栈跟踪

@Provider
public class DebugExceptionMapper implements ExceptionMapper<Throwable> {

    @Overrride
    public Response toResponse(Throwable e) {
        e.printStackTrace();
        return Response.serverError()
           .entity(e.getMessage())
           .build();
    }
}

另见: