Hi,
>From time to time we get an error in one of our production databases:
org.hibernate.TransactionException: commit failed
at
org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:187)
at
de.oktopos.dataBase.tools.DatabaseOperationRunner.run(DatabaseOperationRunner.java:75)
at
de.oktopos.dataBase.receipts.converter.ReceiptConverter.saveReceipt(ReceiptConverter.java:346)
at
de.oktopos.dataBase.receipts.converter.ReceiptCacheWriter.saveReceipt(ReceiptCacheWriter.java:31)
at
de.oktopos.oktoDeskService.remote.OktoDeskModel.saveChangeLog(OktoDeskModel.java:382)
at
de.oktopos.controller.OktoCashDeskController.sendOrders(OktoCashDeskController.java:1733)
at
de.oktopos.controller.OktoCashDeskController.finishReceipt(OktoCashDeskController.java:1656)
at
de.oktopos.controller.BookingController.doBook(BookingController.java:149)
at
de.oktopos.controller.ReceiptOperationsManager.book(ReceiptOperationsManager.java:262)
at
de.oktopos.controller.ReceiptOperationsManager.finishBooking(ReceiptOperationsManager.java:245)
at
de.oktopos.controller.ReceiptOperationsManager.finalizeBooking(ReceiptOperationsManager.java:203)
at
de.oktopos.controller.ReceiptOperationsManager.finalizeBooking(ReceiptOperationsManager.java:183)
at
de.oktopos.controller.ReceiptOperationsManager.doBook(ReceiptOperationsManager.java:176)
at
de.oktopos.controller.ReceiptOperationsManager.bookCash(ReceiptOperationsManager.java:128)
at
de.oktopos.view.cashdesk.ScanBookingPanel$8.run(ScanBookingPanel.java:802)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown
Source)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.hibernate.TransactionException: unable to commit against JDBC
connection
at
org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:116)
at
org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:180)
... 21 more
Caused by: org.h2.jdbc.JdbcSQLException: Allgemeiner Fehler:
"java.lang.IllegalStateException: Chunk 0 no longer exists [1.4.191/9]"
General error: "java.lang.IllegalStateException: Chunk 0 no longer exists
[1.4.191/9]"; SQL statement:
COMMIT [50000-191]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at org.h2.command.Command.executeUpdate(Command.java:266)
at org.h2.jdbc.JdbcConnection.commit(JdbcConnection.java:467)
at
org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doCommit(JdbcTransaction.java:112)
... 22 more
Caused by: java.lang.IllegalStateException: Chunk 0 no longer exists
[1.4.191/9]
at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:773)
at org.h2.mvstore.MVStore.getChunkIfFound(MVStore.java:949)
at org.h2.mvstore.MVStore.getChunk(MVStore.java:931)
at org.h2.mvstore.MVStore.removePage(MVStore.java:1976)
at org.h2.mvstore.MVMap.removePage(MVMap.java:1097)
at org.h2.mvstore.Page.removePage(Page.java:935)
at org.h2.mvstore.Page.copy(Page.java:307)
at org.h2.mvstore.MVMap.remove(MVMap.java:664)
at org.h2.mvstore.MVMap.remove(MVMap.java:545)
at org.h2.mvstore.db.TransactionStore.commit(TransactionStore.java:361)
at
org.h2.mvstore.db.TransactionStore$Transaction.commit(TransactionStore.java:779)
at org.h2.engine.Session.commit(Session.java:611)
at
org.h2.command.dml.TransactionCommand.update(TransactionCommand.java:46)
at org.h2.command.CommandContainer.update(CommandContainer.java:98)
at org.h2.command.Command.executeUpdate(Command.java:258)
... 24 more
(it's not necessarily chunk 0 that is missing, and so far we didn't detect a
pattern).
It only seems to occur after the database has been used for some time or
contains a lot of data, as we never see this in a test or development
environment.
We are using Version 1.4.191.
Is that an issue with h2, or is there anything we could be doing wrong on
our side that could cause this?
--
Sent from: http://h2-database.66688.n3.nabble.com/
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
