Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>The issue us that the connection does not close properly and is stuck in the 'sleep' mode</p> </blockquote> <p>This was actually only half right.</p> <p>The problem I ran into was actually that each app was defining a new connection to the database sever. So each time I closed all the connections App A would make a bunch of new connections as per it's WEB.xml config file and run happily. App B would do the same. The problem is that they are <em>independent pools</em> which try to grab up to the server defined limit. It is a kind of race condition I guess. So when App A has finished with the connections it sits waiting to to use them again until the timeout has passed while App B who needs the connection now is denied the resources even though App A has finished with the and should be back in the pool. Once the timeout has passed, the connection is freed up and B (or C etc) can get at it again.</p> <p>e.g. if the limit is 10 (mySQL profile limit) and each app has been configured to use a max of 10 the there will be 20 attempts at connections. Obviously this is a bad situation.</p> <p>The solution is to RTFM and put the <a href="http://tomcat.apache.org/tomcat-5.5-doc/config/context.html" rel="nofollow">connection details in the right place</a>. This does make shared posting a pain but there are ways around it (such as linking to other xml files from the context).</p> <p>Just to be explicit: I put the connection details in the WEB.xml for each app and the had a fight about it.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload