|Subject||Re: various errors during night tests|
> Have you looked at my yesterday's post? That errors are moreYes, I have read your post. But I have no idea, especially without a
> frequent than the deadlock one and maybe they can give some clue
> about the cause of the problem.
test case. In order to be able to say where the problem is, we need a
reproducable test case.
> However during normal debugging tests (so very low load on theIf you want to exclude the probability that this is
> application) i have no problems. Problems occurs when i have more
> clients that continuosly stress the application: normally i have
> about 40 or 50 clients that connect simultaneously and perform
> requests continuosly to the application.
FBWrappingDataSource bug, try using another JDBC pool. There's a
plenty of them.
> i don't think so. i forget to mention that the inserted row isThis is quite strange, because it should not happen. Anyway, without
> updated by the same thread in the same connection and that other
> threads work on different rows and connections (from the same pool).
> they never update a row inserted by another thread.
reproducable test case we cannot tell you anything.
> Maybe should i synchronize the access to the FBWrappingDataSource?Try to synchronize your calls. FBWrappingDataSource was developed by
> Or the getConnection method is already synchronized?
David Jencks, so he knows better any effects that can be caused by