search

b3nzchr3ur / agiletrackingtool

Automatically exported from code.google.com/p/agiletrackingtool
0 stars 0 forks source link

java.io.EOFException at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1934) #15

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
On deployment this exception occurs:

java.io.EOFException 
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1934) 

Also check out:
http://forums.mysql.com/read.php?39,52805,273371#msg-273371

Seems to be a configuration issue with mysql connection pooling.

Original issue reported on code.google.com by agiletra...@gmail.com on 16 Mar 2010 at 7:02

GoogleCodeExporter commented 8 years ago 
This exception occured after login. 
Workaround: when logging in again the connection can be made.

Original comment by ben.schreur@gmail.com on 16 Mar 2010 at 7:03

GoogleCodeExporter commented 8 years ago

Original comment by ben.schreur@gmail.com on 17 Mar 2010 at 8:51

Attachments:

GoogleCodeExporter commented 8 years ago 
http://refactor.com.au/blog/idiots-guide-tomcat-6-grails-jndi-datasource

Original comment by ben.schreur@gmail.com on 20 Mar 2010 at 1:42

GoogleCodeExporter commented 8 years ago 
Changed DataSource.groovy configuration to use jndi. 
See DataSource.jndi.groovy.

Original comment by ben.schreur@gmail.com on 21 Mar 2010 at 12:31

GoogleCodeExporter commented 8 years ago 
After JNDI migration still exception. See attachment.

Original comment by ben.schreur@gmail.com on 22 Mar 2010 at 8:13

Attachments:

GoogleCodeExporter commented 8 years ago 
http://wordpress.transentia.com.au/wordpress/2009/09/30/tweaking-the-grails-data
source-
to-cope-with-mysqls-foibles/

Original comment by ben.schreur@gmail.com on 22 Mar 2010 at 8:42

GoogleCodeExporter commented 8 years ago 
Using the solution as suggested in comment 6 seems to resolve to issue.

Original comment by ben.schreur@gmail.com on 24 Mar 2010 at 9:25

GoogleCodeExporter commented 8 years ago

Original comment by ben.schreur@gmail.com on 24 Mar 2010 at 9:26

GoogleCodeExporter commented 8 years ago 
Note: this issue is not strictly related to the grails project. It's caused by 
automatic closing of mysql of open connections and the way tomcat deals with 
this.

Original comment by ben.schreur@gmail.com on 24 Mar 2010 at 9:27