I forgot to mention: We also made sure there is only one thread accessing the JDBC connection from our application.
Thanx for any hints on how to investigate this further. Regards, Rob. Op vrijdag 15 april 2016 15:39:11 UTC+2 schreef Rob Van Dyck: > > Hi list, > > When inserting a large file (+40 MB) into a BLOB column using the H2 > server mode we get a connection reset on the second or third file (this > appears to be random) within our application. This connection reset results > from a protocol error on the server side traced back to > TcpServerThread.process(). > > The protocol error is the following: > Unknown operation: -46695848 > > The 'unknown operation' number is always exactly the same, no matter what > file we use for an insert. We have tried reproducing the issue using a > small test program, but we are unable to reproduce this. > > Because we are unable to reproduce this we suspect that our application is > triggering this. But from the output of the trace.db file and our own > internal SQL logging we see nothing wrong. We have tried to run the exact > same SQL commands from our small test program, but this does not fail. We > don't think our internal SQL logging missed a command, but there must be > something causing this. > > We do not get any errors using the H2 embedded mode. > > Does anyone recognizes this, or does anyone have a pointer on what might > be triggering this issue? > > H2 version: 1.3.176 > H2 URL: > "jdbc:h2:tcp://localhost/~/test;TRACE_LEVEL_FILE=3;TRACE_MAX_FILE_SIZE=200" > > We use the following settings: > c.setAutoCommit(false); > SET LOG=2 > SET LOCK_MODE=3 > SET UNDO_LOG=1 > SET CACHE_SIZE=16384 > > The statement we use that we think is triggering the issue (used in our > testcase, but similar to our application): > PreparedStatement ps = c.prepareStatement( > "INSERT INTO \"BinaryFileRecordAttachment$wc\" (\"oid\", > \"cid\", \"bytes\", \"compressed\", \"contentType\", \"date\", > \"description\", \"fileName\", \"type\", \"record$oid\", \"record$cid\") > VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"); > ps.setObject(3, inputStream, 2004); > > From our internal SQL logging we notice that the failing insertion is > triggered client-side, but is not registered in the database.trace.db file. > > Regards, > Rob. > -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
