Well I just found that the bug isn't in the newest version of the jar, which I thought I had. But now my roller log looks like
INFO 2008-05-23 14:13:17,891 DatabaseProvider:successMessage - SUCCESS: loaded JDBC driver class [oracle.jdbc.driver.OracleDriver] FATAL 2008-05-23 14:13:29,590 RollerContext:contextInitialized - Roller Weblogger bootstrap failed org.apache.roller.weblogger.business.BootstrapException: Error instantiating default provider: org.apache.roller.weblogger.business.GuiceWebloggerProvider at org.apache.roller.weblogger.business.WebloggerFactory.bootstrap(WebloggerFactory.java:92) at org.apache.roller.weblogger.ui.core.RollerContext.contextInitialized(RollerContext.java:156) and I'm not sure what to do with this. -Tim ________________________________________ From: Timothy Mizas [EMAIL PROTECTED] Sent: Friday, May 23, 2008 1:42 PM To: [email protected] Subject: RE: Oracle configuration problem I tried changing my driver to classes12 and that is letting it connect. But now I get java.lang.NumberFormatException at java.lang.Integer.parseInt(libgcj.so.7rh) at java.lang.Integer.parseInt(libgcj.so.7rh) at org.apache.roller.weblogger.business.startup.DatabaseInstaller.getDatabaseVersion(DatabaseInstaller.java:1169) It seems this is an error in the driver causing this. I've found that I should be able to TOMCAT_OPTS=-Doracledatabasemetadata.get_lob_precision=false but that isn't working. Is there a way to disable the version check? -Tim ________________________________________ From: Simon Haslam [EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 5:16 AM To: [email protected] Subject: RE: Oracle configuration problem Timothy Mizas wrote: > > I managed to get roller working fine with no issues on my personal > machine. But as soon as I move it to the red hat server, with the same > settings, I still get this in roller.log > > java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 > ORA-12705: invalid or unknown NLS parameter value specified > > It says DriverManager.getConnection() is throwing this error. I've tried > completely turning off the firewall to make sure it was able to freely > connect too. Has anyone been able to get roller working on RHEL 5? > Yes, I've got Roller running on RHEL5 (actually OEL5) and to 10.2 of the database but using OC4J 10.1.3 instead of Tomcat. Have you looked on Metalink, e.g. notes 158654.1 "ORA-12705 - Common Reasons and How to Resolve Them" and 21558.1 "OERR: ORA 12705 "invalid or unknown NLS parameter value specified""? You don't say what locale you're in etc but have you tried NLS_LANG = AMERICAN_AMERICA.US7ASCII (the default)? When you say it worked fine on your PC how different is that environment - Windows or Linux, did you have an Oracle client installed on it, is it in the same subnet as the app server, etc? Finally have you tried writing a small, standalone java test program to prove that you can connect to the database using the same driver/connection URL. This would then indicate whether the problem is in Roller/Tomcat configuration. :Simon -- View this message in context: http://www.nabble.com/Oracle-configuration-problem-tp17325911s12275p17359243.html Sent from the Roller - User mailing list archive at Nabble.com.
