https://issues.apache.org/bugzilla/show_bug.cgi?id=53995
Philippe Mouawad <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |[email protected] | |om --- Comment #1 from Philippe Mouawad <[email protected]> --- I am not sure your analysis is correct. There are 2 modes for JDBC Connection Configuration. If max pool is set to 0, there will be one pool for each thread, connections will never be shared, so this one is OK Now, if max pool is set, it can happen at one time that 2 threads will use the same connection, but in my understanding, it will never happen at the same time as pool will return an idle connection (so different from the one in use) or it will wait if no one is available. So the case you describe cannot happen. It is true that the pool shares PreparedStatement but they are always associated to the same connection. So I don't think there is an issue as connection will never be shared by two threads at the same time, but I may be wrong. Could you submit a Test Plan showing the issue and the exact error ? or one of the 2 issues ? Thank you. -- You are receiving this mail because: You are the assignee for the bug.
