OK, so it was already identified, thanks for the pointer.
It says it was fixed in JBoss 4.0, does that mean there will soon be a version 4.0.1? How does that generally work? It's obviously not fixed in the version available for download.
How about the "Hibernate lazy instantiation error" I'm getting? Could it be related or is it something completely different?
Hello - I am seeing the same problem with jboss-4.0.0 (which I recently downloaded). I am trying to use this with MySQL 4.0.13. Does anyone know how to fix this problem ? Also, would the inability to create the TIMERS table cause a JMS client to fail ?
Creating jndi context - alternatively use a jndi.properties
Looking up queue
Exception in thread "main" javax.naming.NameNotFoundException: queue not bound
Not sure if the JMS queue problem is caused by the previous problem.
Yes, there's a problem with non-standard SQLin JBoss 4.0
There are a couple of posts about it in the Persistence/JBoss thread.
Unfortunately still no sign of a solution of the JBoss people. Sigh.