Databases
StackOverflow2013
Postsdbo
POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
    primarykey
    data
    text
    <p>I have a couple of Grails 1.3.3 application running on Tomcat 6.0.18. I'm aware of the database connection staleness issue when using the default Grails datasource (connection gets killed after a period of inactivity), so I switched to JNDI provided by Tomcat.</p> <p>The first app I deployed has never had any stale database connection problems. Now I deployed a second app to the same server with the same JNDI datasource configuration, and while the first continues to work fine, the second app gets the connection timeout error after about 8 or so hours of inactivity. (After the error the connection gets refreshed and it works just fine again)</p> <p>The datasources are defined in Tomcat's context.xml as follows:</p> <pre><code>&lt;Resource name="jdbc/firstDs" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="user1" password="password1" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/firstApp" /&gt; &lt;Resource name="jdbc/secondDs" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="user2" password="password2" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/secondApp" /&gt; </code></pre> <p>Both of the apps use the JNDI datasource in the Datasource.groovy file as follows (everything is exactly the same, except for the jndiName):</p> <pre><code>dataSource { pooled = false } ... environments { ... production { dataSource { dbCreate = "update" jndiName = "java:comp/env/jdbc/firstApp" } } } </code></pre> <p>The <strong>ONLY</strong> difference I'm aware of between these 2 situations is that working app uses MyISAM tables, while the non-working app uses InnoDB tables. Has anyone experienced an issue with InnoDB and Tomcat connection pooling? I may try switching to MyISAM if I can't find anything else to try.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKaleb Brasee
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
      1. USskaz
      1. VTFavorite
    1. COThe exception stacktrace would be helpful. - I'd also log at the `warn` level, including `org.hibernate`, `org.springframework`, and `com.mysql`. If any, indicators ought to be at the end of the log file when the exception occurs.
      singulars
      1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
      1. USrobbbert
    2. COThis worked for me (not jndi, so I'm providing a comment instead of and answer): http://www.sylvioazevedo.com.br/?p=56
      singulars
      1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
      1. USBrad Rhoads
    3. CODon't switch to MyISAM - there's no way that has any effect.
      singulars
      1. POGrails/Tomcat/MySQL stale connection error, even when using JNDI?
      1. USBurt Beckwith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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