Community
Participate
Working Groups
On starting the 0.9.4 application server (postgresql version), and using a database created with 0.9.0 and used with 0.9.1, the following exception occurs multiple times when the 0.9.4 client is started: Wed Jun 09 14:55:13 BST 2010 org.eclipse.osee.framework.branch.management.internal.Activator SEVERE org.eclipse.osee.framework.branch.management.cache.DatabaseBranchAccessor loadBranches (109) The column name baseline_transaction_id was not found in this ResultSet. org.eclipse.osee.framework.core.exception.OseeDataStoreException: The column name baseline_transaction_id was not found in this Resu ltSet. at org.eclipse.osee.framework.database.internal.core.OseeStatementImpl.getInt(OseeStatementImpl.java:229) at org.eclipse.osee.framework.branch.management.cache.DatabaseBranchAccessor.loadBranches(DatabaseBranchAccessor.java:106) at org.eclipse.osee.framework.branch.management.cache.DatabaseBranchAccessor.load(DatabaseBranchAccessor.java:70) at org.eclipse.osee.framework.core.cache.AbstractOseeCache.reloadCache(AbstractOseeCache.java:270) at org.eclipse.osee.framework.core.cache.AbstractOseeCache.ensurePopulated(AbstractOseeCache.java:243) at org.eclipse.osee.framework.core.cache.AbstractOseeCache.getAll(AbstractOseeCache.java:170) at org.eclipse.osee.framework.manager.servlet.OseeCacheServlet.createResponse(OseeCacheServlet.java:214) at org.eclipse.osee.framework.manager.servlet.OseeCacheServlet.sendUpdates(OseeCacheServlet.java:191) at org.eclipse.osee.framework.manager.servlet.OseeCacheServlet.doPost(OseeCacheServlet.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.eclipse.osee.framework.core.server.internal.InternalOseeHttpServlet.service(InternalOseeHttpServlet.java:79) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:380) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:748) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:219) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520) Caused by: org.postgresql.util.PSQLException: The column name baseline_transaction_id was not found in this ResultSet. at org.postgresql.jdbc2.AbstractJdbc2ResultSet.findColumn(AbstractJdbc2ResultSet.java:2503) at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getInt(AbstractJdbc2ResultSet.java:2367) at org.eclipse.osee.framework.database.internal.core.OseeStatementImpl.getInt(OseeStatementImpl.java:227) ... 29 more Has the database structure changed between 0.9.1 and 0.9.4?
You need to run the database importer to upgrade your database. I think Ryan Brooks mentioned it in his release announcement, but he's currently on vacation.
Thanks Ryan Bug retargetted at website, as needing to use the database export/import should really be made apparent on the Downloads page (in my view, others may disagree!). It was more intuitive when database incompatibilities were marked with a major rev.