On Fri, Aug 6, 2010 at 05:04, Joe <[email protected]> wrote: > However, I'm still concerned about the mechanism for waiting. It is > 30 'wait cycles' where each wait cycle would complete from one of the > following conditions: > 1) the connection becomes available > 2) the 1000ms wait call completes and the thread resumes > 3) the notifyAll method is called causing the wait to return > immediately (not just after 1000ms). > > Under high contention for those connections I believe two things can > happen: > - starvation of access to a connection because the waiting mechanism > is unfair > - waiting potentially way less than 30 seconds because the waiting > mechanism isn't really much about time at all (it is about wait/ > notifyAll cycles in high contention).
Thank you for the information. > I might just be reading the code wrong or misunderstand the wait/ > notifyAll behavior...but I'm quite sure I'm seeing these 'Login > timeout' exceptions at times way before 30 seconds hit. I am not in the H2 developer team so I didn't look into the source code. I think one of the developers should answer this. -- Martin Wildam http://www.google.com/profiles/mwildam -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
