Wildfire 2.4.0...upgrade even possible?

Openfire Openfire Support
1

My wildfire server is just one of those things - it was never as important as other systems upgrades I kept up with…

So now here I sit, horribly out of date, wanting to go to openfire. Is this even possible? I’m currently using a jdbc connection to my oracle database - will I need to upgrade that schema?

Or am I basically starting from scratch.

I tried just installing openfire and making the changes to my config, but it’s having a fit over the oracle driver…I’m running a 9i client…

Thoughts ?

2008.05.27 12:03:04 org.jivesoftware.util.log.util.CommonsLogFactory$1.error(CommonsLogFactory.java: 92) Couldn’t load class oracle.jdbc.driver.OracleDriver

java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Unknown Source)

at org.logicalcobwebs.proxool.ConnectionPool.setDefinition(ConnectionPool.java:740 )

at org.logicalcobwebs.proxool.ConnectionPool.<init>(ConnectionPool.java:115)

at org.logicalcobwebs.proxool.ConnectionPoolManager.createConnectionPool(Connectio nPoolManager.java:93)

at org.logicalcobwebs.proxool.ProxoolFacade.registerConnectionPool(ProxoolFacade.j ava:109)

at org.logicalcobwebs.proxool.ProxoolFacade.registerConnectionPool(ProxoolFacade.j ava:97)

at org.logicalcobwebs.proxool.ProxoolDriver.connect(ProxoolDriver.java:77)

at java.sql.DriverManager.getConnection(Unknown Source)

at java.sql.DriverManager.getConnection(Unknown Source)

at org.jivesoftware.database.DefaultConnectionProvider.getConnection(DefaultConnec tionProvider.java:76)

at org.jivesoftware.database.DbConnectionManager.setConnectionProvider(DbConnectio nManager.java:484)

at org.jivesoftware.database.DbConnectionManager.getConnection(DbConnectionManager .java:78)

at org.jivesoftware.util.JiveProperties.loadProperties(JiveProperties.java:330)

at org.jivesoftware.util.JiveProperties.init(JiveProperties.java:72)

at org.jivesoftware.util.JiveProperties$JivePropertyHolder.<clinit>(JiveProp erties.java:39)

at org.jivesoftware.util.JiveProperties.getInstance(JiveProperties.java:51)

at org.jivesoftware.util.JiveGlobals.getProperty(JiveGlobals.java:525)

at org.jivesoftware.openfire.XMPPServer.initialize(XMPPServer.java:333)

at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:447)

at org.jivesoftware.openfire.XMPPServer.<init>(XMPPServer.java:161)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.openfire.starter.ServerStarter.start(ServerStarter.java:106)

2

The old versions of openfire/wildfire are still available. Maybe it does help to make the updates step by step.

However, at least the newer versions of Openfire can update their database schema themselves, if they have the necessary access rights. I’m not sure since when this feature is available, maybe it was already in Wildfire.

3

Thanks for your response - I just managed to get my wildfire version up to 3.2.0 - I applied all of the necessary schema updates to the database and I’m feeling pretty cool righ now.

From what I’m reading I can go straight into openfire now, yes? And the database updates will just magically happen? I’ll give it a go…

R