[Springframework-developer] HSQLDB version

[Colin S. <col...@ex...>]

I believe the issue I mentioned below is due to the fact that JBoss 
3.2.5 and earlier was using HSQLDB 1.7.1 (from late 2002), while JBoss 
3.2.6 uses HSQLDB 1.7.2 (one of the point releases, dated some time in 
august. The last point release, from Oct is actually 1.7.2.7).

I was going to try slipping in 1.7.2 in our own codebase, which you 
would think would not be an issue going from 1.7.1 to 1.7.2, but in fact 
there are some major changes internally, and the new version barfs on 
the stored db as well as the setup script for petclinic for example, 
with an error on some of the formerly legal SQL.
  http://hsqldb.sourceforge.net/web/changelog.html
I think this kind of incompatibility is an major bad move for the 
developer of HSQLDB; this should have been called 1.8 then...

So I am wondering if we should try to make a switch, and what the 
implications really are. If we stay with 1.7.1, we can't run in the 
newer JBoss, and will not pick up any HSQLDB enhancements, plus Spring 
users are probably going to want to switch later if not now anyways. On 
the other hand, if we go to 1.7.2, I think that kills compatibility with 
older JBoss versions, and will kill db compatibility for somebody just 
upgrading the spring version and blindly dropping in the new jar, 
although they should be ok if they just copy over their old jar...

Any thoughts?


Colin Sampaleanu wrote:

> I am seeing extremely strange, completely repeatable behaviour, where 
> Petclinc in both the JDBC and the hibernate deployment, using HSQL, 
> starts up ok in JBoss 3.2.5, but hangs after a certain point in JBoss 
> 3.2.6. The ejbtest sample does exactly the same thing. Weird thing in 
> 3.2.6 is that if I shut down the external HSQL db (started with the 
> server.bat file), then the app starts fine (getting some obvious 
> errors since it can't actually talk to the db, but doesn't hang). This 
> means the issues are somehow related to HSQL in the 3.2.6 environment.