We've worked really hard to fix any session management issues, and in HSQL this constraint violation is never thrown. : Could not execute JDBC batch updateĪt .handledNonSpecificException(SQLStateConverter.java:103)Īt .convert(SQLStateConverter.java:91)Īt .convert(JDBCExceptionHelper.java:43)Īt .executeBatch(AbstractBatcher.java:253)Īt .executeActions(ActionQueue.java:237)Īt .executeActions(ActionQueue.java:143)Īt .AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)Īt .DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)Īt .flush(SessionImpl.java:1000)Īt .managedFlush(SessionImpl.java:338)Īt .commit(JDBCTransaction.java:106)Īt .(HibernateObjectWriter.java:41)Īt .(HibernateObjectWriter.java:54)Īt .(MultiObjectInsertion.java:41)Īt .(BlockSellerInsertion.java:88)Īt .(BlockSellerInsertion.java:63)Īt .yBlock(UnsubscribeController.java:138)Īt .UnsubscribeController.handleRequest(UnsubscribeController.java:89)Īt .(SimpleControllerHandlerAdapter.java:48)Īt .DispatcherServlet.doDispatch(DispatcherServlet.java:857)Īt .DispatcherServlet.doService(DispatcherServlet.java:792)Īt .FrameworkServlet.processRequest(FrameworkServlet.java:461)Īt .FrameworkServlet.doGet(FrameworkServlet.java:416)Īt .service(HttpServlet.java:690)Īt .service(HttpServlet.java:803)Īt .ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)Īt .ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)Īt .StandardWrapperValve.invoke(StandardWrapperValve.java:210)Īt .StandardContextValve.invoke(StandardContextValve.java:174)Īt .StandardHostValve.invoke(StandardHostValve.java:127)Īt .ErrorReportValve.invoke(ErrorReportValve.java:117)Īt .StandardEngineValve.invoke(StandardEngineValve.java:108)Īt .rvice(CoyoteAdapter.java:151)Īt 11.Http11Processor.process(Http11Processor.java:870)Īt 11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)Īt .(PoolTcpEndpoint.java:528)Īt .(LeaderFollowerWorkerThread.java:81)Īt .threads.ThreadPool$n(ThreadPool.java:685)Īlso resulting from these operations that can't be completed are these constraint violations that only manifest themselves right before the deadlock occurs. 20:01:47,568 ERROR - Could not synchronize database state with session 20:01:47,568 ERROR - ERROR: deadlock detected Call getNextException() to see the cause. 20:01:47,568 ERROR - Batch entry 2 delete from UserWalkthroughs where SID= was aborted. PostgreSQL 7.4.16, Java 1.5 on Debian Linux, Tomcat 5.5.23, Spring 2.0įull stack trace of any exception that occurs: If anybody could shed some light on the situation, I would really appreciate it. I searched for known issues between PostgreSQL and Hibernate in performing queries and found this discussion, referencing an older but similar problem: While I'm mostly concerned that it's a PostgreSQL configuration issue, I can't be certain that Hibernate is not playing a role. I've pumped a lot of sample data into the HSQLDB instance and not seen anywhere near the time taken by PostgreSQL. When more than one user tries to get to this page, the database almost immediately hits deadlock.ĭeveloping locally, I've been using HSQLDB as a lightweight development database, and run times on the same queries are much smaller (loading one of the heavier pages, with plenty of collections of objects and several substantial queries takes ~1.5 seconds, PostgreSQL verges on 10-15). Our firm's production server, which is currently running PostgreSQL 7.4.16, seems to be having a tremendously hard time performing relatively simple queries (max 3 joins) on a small db (in that case, a join table between 300 x 22 tuples). I've been developing a web app with Spring/Hibernate/Tomcat5.5 in the Eclipse IDE. I've been good about not posting superfluous things, but I've run into a problem that I can't resolve.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |