This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Hi, I have a strange error occuring very rare during the tests of the database file record reading, with the usage of RadomAccessFile.
Then I execute the JUnittest when many threads trying to read random record and get this strange result:
I start with populating the static cache of database in the JUnit during the junit class loading (similar to JUnit4 beforeClass()):
After that, many threads are created, each one trying to read some random record:
And the simple code of RecordReader thread:
It happens very rare and with different records, no matter if a set the thread count to 10 or to 100. I looked through the log and found no other threads trying to change the file pointer. Do you have any idea of what can be wrong?
Man I don't know the Urly Bird spec but the problem that you mention seems to be a field length problem. I had a problem as yours on my project, I wasn't counting the first byt that indicates the total length, So sometimes my updates and selects came like yours are coming.
Well, it's just a wondering.... Try to log even more details and post here...
Hope you found this problem soon, wish you lucky
The Death of one is a tragedy, but the Death of a million is just a statistic. Joseph Stalin