no really, I *do* need jdbc!
After I upgraded to snv_110, I was having a heckuvatime trying to figure out why my Roller instance wasn’t behaving properly. I saw scads and scads of java stacktrace errors, along with
SEVERE: Servlet.service() for servlet jsp threw exception java.lang.IllegalStateException: Roller Weblogger has not been bootstrapped yet
I saw loads of messages in forum posts about this, several of which said something like “oh, figured it out, our db was down, all good now.” Which was great, except I could confirm very easily that my db backend was up, I could connect to it using the appropriate dbname, username and password. I tried switching from my own tomcat instance to the integrated version – no joy. I tried deploying roller using a WAR rather than unpacked – still no joy. Checked and re-checked my roller-custom.properties, but it was all to no avail.
Eventually I re-read the instructions and something clicked – I should check the jdbc jar files. Well lookee here, that’ll be the problem! My snv_106 instance had a symlink for the postgresql.jar file, and that hadn’t been replicated in the snv_110 environment. Duh!
So I quickly added the postgresql.jar file to my WAR archive, re-deployed it and suddenly, it’s all good again.
Nice to know that it was a simple solution, I’m just annoyed it took me so long for the lights to go on