title: H2 in Tomcat SqlException locked by another process when embedded mode
body: <p>My web project is running in Tomcat 7. My server provider has already a MySql server, however I want to use H2 as it give me a lot more flexibility and speed. My server provider has impose me a limitation that said that I should not start a new thread, doing so will automatically result in a tomcat stop.
  My project is in an alpha near beta stage, so it is been tested locally. I am getting an SqlException Locked by another process often. This is happening when Tomcat updates the thread pool, most of the times happend when automatically publishing from Eclipse (which it is not a deal, as it won't happend on the server) but some times it just happends randomly.
  My application doesn't access the database directly but through a wrapper that I am confident about it is not creating the issue but also prevents it to happend a lot.
  It looks like Tomcat it is sending the thread that holds the connection to the background and any foreground thread will fail (my app it is database intensive).
  Open a connection in server mode will fix the problem, but it will run in a new process which I'm not aloud to.
  I will like to keep H2, so before I have to switch to MySql I will need a solution for any of the following answers:</p>
  
  <ul>
  <li>Can I somehow connect to embedded H2 without Tomcat thread pool collisions?</li>
  <li>Can I connect to server mode H2 without H2 creating a new process?</li>
  </ul>
  
  <p>Note: I can not post any actual code. I am sure is not my application issue. I don't think it is necessary but I will write a description of how my wrapper handle the connection if required, but the problem has been identified as explained above.</p>