title: Single MySql Database Connection for REST service
body: <p>I am developing Android application which Gets and Posts data to database through REST service. I have configures REST service with Jersey and Tomcat in Java.</p>
  
  <p>I created single database connection when REST service starts.Now all the android clients using the single database connection.Now i just want to know is it good practice to use single database connection in my scenario..Can single database connection can entertain more than one concurrent requests ?? </p>
  
  <p>Kindly suggest....</p>
  
  <p><strong>Updated</strong>
  When i test following scenario ,it gives different results..i just configured simple REST server with tomcat using Jersey with Get annotation only, inside this annotation i write the code to get the name of employee whose id is 300 using database connection which was established when REST was started..so that when i write             <code>http://192.168.15.9:8080/Rest/rest/person/sample</code> on my web browser i got employee name...Then i created batch file to open the url in 100 tabs, i executed the batch file. At same time i open the url from my virtual machine and got the employee name with no delay..Also employee name is displayed in 100 tabs after 20 seconds..If single database connection can not be used for concurrent users then why i gives response rapidly ??  Can any one please explain ?? </p>