Ok, it seems JDBCRealm is broken, at least when set in a webapp's context.xml. I suspect a classloader issue.
If you use a DatasourceRealm, and define a JNDI datasource, then it all works fine. On Apr 3, 10:18 am, Crusoe <[email protected]> wrote: > It is in the path. It is in my webapp, and I stuck in the > catalina_home/lib as well. > > Here is the url, and yes the server has been started > > jdbc:h2:tcp://localhost/~/h2-db/ms_Trailblaze;TRACE_LEVEL_FILE=3 > > Anyways, other drivers can seem to work in this system, what makes H2 > unique? > > On Apr 3, 5:21 am, Thomas Mueller <[email protected]> > wrote: > > > Hi, > > > > SEVERE: Exception opening database connection > > > java.sql.SQLException: org.h2.Driver > > > at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java: > > > 691) > > > This looks like an exception of the JDBCRealm, not from H2. > > > Where did you put the h2*.jar file? Maybe it's not in the classpath of > > the server. > > > > I am having a heck of > > > time of finding the logger name in the docs so my log4j.xml can pick > > > it up. > > > Try not to use slf4j / log4j until it works (maybe one of those jar > > files is not in the classpath?). Instead, using a database URL of the > > form jdbc:h2:~/test;TRACE_LEVEL_FILE=3 > > > Afterwards the .trace.db files (if you use the server mode, then there > > are two such files: one for the client, and one for the server). > > > Regards, > > Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
