playframework - IOExceptions with H2 database -

-

recentently ioexceptions play app uses h2 database. this:

caused by: java.io.ioexception: block not found in id [1, -68, 2, 2] [1.4.187/50]   @ org.h2.mvstore.streamstore$stream.read(streamstore.java:466) ~[com.h2database.h2-1.4.187.jar:1.4.187]   @ sun.nio.cs.streamdecoder.readbytes(streamdecoder.java:284) ~[na:1.8.0_40]   @ sun.nio.cs.streamdecoder.implread(streamdecoder.java:326) ~[na:1.8.0_40]   @ sun.nio.cs.streamdecoder.read(streamdecoder.java:178) ~[na:1.8.0_40]   @ java.io.inputstreamreader.read(inputstreamreader.java:184) ~[na:1.8.0_40]   @ java.io.bufferedreader.fill(bufferedreader.java:161) ~[na:1.8.0_40]   @ java.io.bufferedreader.read1(bufferedreader.java:212) ~[na:1.8.0_40]   @ java.io.bufferedreader.read(bufferedreader.java:286) ~[na:1.8.0_40]   @ org.hibernate.type.descriptor.java.datahelper.extractstring(datahelper.java:88) ~[org.hibernate.hibernate-core-4.3.11.final.jar:4.3.11.final]

it might issue talking in https://groups.google.com/forum/#!topic/h2-database/myx5rh6cv-8 or https://groups.google.com/forum/#!topic/h2-database/gv5nu2subzm. here writes '1.4.186, 1.4.187 , 1.4.188 vulnerable versions.'. in play version (2.4.3) h2 version 1.4.187 used.

it seems happen sporadically , far not find reason when happened.

i wonder why there not more find in internet issue. unstable database seems quite important. set version latest 1.4.191 , closely monitor it. have had similar experiences h2 , play?

to answer original question. yes, had experience when using build .187.

i had following exception:

org.h2.jdbc.jdbcsqlexception: io exception: "java.io.ioexception: block not found in id [1, -109, 3, 1] [1.4.187/50]"; "lob: null table: -3 id: 7" [90031-187]

... similar stacktrace yours.

once moved build .192 problem went away completely. problem listed fixed in version 1.4.189 beta (2015-09-13) based on change logs:

http://www.h2database.com/html/changelog.html

so, move .192 , close our fingers doesn't happen again !!!


Comments

Post a Comment

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

-
this error has shown on many times, seems. prominent answer issue seems restkit 0.20 — coredata: error: failed call designated initializer on nsmanagedobject class however, solution posted doesn't work me. let's start beginning: i want upload file server. want parse response make sure uploaded. if not, try again later. model has boolean variable called nsnumber *senttoserver purpose (in coredata, bool saved nsnumber ) . because don't know whether sending going successful, save entity coredata model first before sending via restkit. when post request successful, server returns json string this: {"id":14,"created":true} notice that, of course, id not set on coredata model yet, both id , created new informations model. here's model: @interface recording : nsmanagedobject @property (nonatomic, retain) nsstring * audiofilepath; @property (nonatomic, retain) nsdate * createdat; @property (nonatomic, retain) nsstring * deviceid; @
Read more

java - Digest auth with Spring Security using javaconfig -

-
so i'm trying create digest authentication spring following documentation trying translate xml "requirements" in java requirements. let's have xml in docs: <bean id="digestfilter" class= "org.springframework.security.web.authentication.www.digestauthenticationfilter"> <property name="userdetailsservice" ref="jdbcdaoimpl"/> <property name="authenticationentrypoint" ref="digestentrypoint"/> <property name="usercache" ref="usercache"/> </bean> <bean id="digestentrypoint" class= "org.springframework.security.web.authentication.www.digestauthenticationentrypoint"> <property name="realmname" value="contacts realm via digest authentication"/> <property name="key" value="acegi"/> <property name="noncevalidityseconds" value="10"/> </b
Read more

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -

-
my .env: app_env=local app_debug=true app_key=myappkey app_url=http://localhost db_connection=mysql db_host=localhost db_port=3306 db_database=gestiontaller db_username=root db_password='root' cache_driver=file session_driver=file queue_driver=sync redis_host=127.0.0.1 redis_password=null redis_port=6379 mail_driver=smtp mail_host=mailtrap.io mail_port=2525 mail_username=null mail_password=null mail_encryption=null i've tried password ", ' , without, restarting server every time. i've tried changing localhost 172.0.0.1. yes, password correct, running mysql -u root -p introducing password root in prompt can go mysql. users table: +------------------+-----------+ | user | host | +------------------+-----------+ | debian-sys-maint | localhost | | mysql.sys | localhost | | root | localhost | | root1 | localhost | +------------------+-----------+ i've added homestead.yaml this: database_port: 3306
Read more