I was using Spring/JPA/Eclipselink with MySql and I never experienced any problems starting up my application in Tomcat.
Then I switched to Spring/JPA/Hibernate. Eclipselink to Hibernate was the only change (confirmed). Now, when my application starts up in Tomcat, I intermittently get this error message:

Caused by: java.sql.SQLException: Can't create/write to file 'C:\tools\MySQL\MySQL Server 5.0\temp\#sql_da0_0.MYD' (Errcode: 13)

Most forum posts ( google, hibernate, mysql, javaranch... all sorts of forums ) on this issue say it has to do with your antivirus program and if you just disable it, or configure it to allow mysql access to the temp dir, then the problem is solved. However, I do not have any antivirus program running, never have. And the fact that it was working fine without *ever* having any problems when using Eclipselink, and only experiencing the problem as soon as I switched to hibernate, leads me to believe that hibernate is doing something differently upon startup.

Has anyone seen this and traced the root cause to hibernate? What are some of the things that hibernate does differently than Eclipselink on application startup?

My Environment:
WinXP Pro (dev env; production will be RHE5 -- i am only seeing this in dev. we have not deployed to production yet)
Mysql 5.0.83
Mysql-connector-java-5.1.6
Hibernate 3.2.7.ga
Spring 2.5.6.SEC01
Java 1.6.0_16