Cool, hopefully it does. Even with the hsql database extracted in temp, I
still see the error upon deployment time of my deployable. It doesn't
happen after that, but since the database is already created, who knows.
Anyhow, it's livable, so hopefully it will eventually go away.
Thanks!
Ryan
On Mon, Jan 12, 2009 at 8:27 AM, Martin Desruisseaux <
[email protected]> wrote:
> Ryan Moquin a écrit :
> > Yes, I've noticed actually that it appears that this error only occurs
> > once and it's during the creation of the database. So when I distribute
> > our app, I'll just do it in a tomcat container with the database already
> > created. I'd still like to know why it happens. My guess is that it
> > gets locked because a thread is trying to access while the database file
> > is being created.
>
> Maybe... I while ago, the access to the EPSG factory was synchronized, so
> maybe
> this error didn't occured at that time. Later one, the code has been made
> concurrent, which may have opened a hole here.
>
> My plan is to see if I can replace the HSQL database by the JavaDB one
> (a.k.a.
> Derby). If it allows to use directly a database embedded in the JAR file
> (this
> need to be verified), it may avoid this issue.
>
> Martin
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
