Skip navigation
Up to Discussions in Openfire Support
29802 Views 79 Replies Latest reply: Sep 18, 2008 10:15 AM by Coolcat RSS
Daniel Henninger KeyContributor
Daniel Henninger
2,972 posts since
Aug 10, 2005
Currently Being Moderated

Aug 29, 2008 5:26 AM

Openfire 3.6.0a has been released!

Folk, as of now Openfire 3.6.0a is available.  All this release is is a ton of database upgrade fixes (and some LDAP fixes) from 3.6.0.  After upgrading to 3.6.0a, you will still see 3.6.0 in the admin console, so please don't be confused by that.  The packages themselves will have the version 3.6.0a in them.  Those of you who successfully upgraded to 3.6.0 already most likely do not need this release.  Those who had problems, this one's for you.  =)  For all practical purposes, I am replacing 3.6.0 with 3.6.0a.


Important!  Please Read!

 

A number of you upgraded and "part of the upgrade" completed before you had a failure, so I wanted to touch on those scenarios a bit so you have an idea of what to do.  First off, if you upgraded to 3.6.0, had it fail, and reverted back to a backup you made -including reverting the database-, you should be good to go and can just install this 3.6.0a package to upgrade what you have.  If you upgraded 3.6.0, had it fail, and then just reinstalled 3.5.2 with the existing database that 3.6.0 already touched, that is where you may have some problems.  I will go over each database individually, what probably happened, and what you can do about it.  By all means it would be better if you can downgrade to your database as it was when you were running 3.5.2 before upgrading to 3.6.0a though.  If you can do this you can skip all of this.

 

MySQL

As far as I can tell, MySQL had no problems with the upgrade.  Most likely. if you had problems with 3.6.0 they were due to LDAP, and you should be good to go to upgrade to 3.6.0a to fix those issues.

 

Postgres

Postgres did not appear to have any problems before.  If it did, it probably failed on update 17.  You can check your jiveVersion table to verify if that's the case.  (it will say "openfire" and "16")  If you don't have a jiveVersion table, well you probably have an ofVersion table and the update should have completed successfully.

 

Oracle

There's a good chance part of update 17 occurred if you had tried Openfire 3.6.0.  An easy way to recover from this and let the updates run like they should is to, before starting up 3.6.0a, but after you install the package, go into your install root/resources/database/upgrade/17/openfire_oracle.sql and delete everything above:

-- update all entries in mucRoom to be set to the default conference service

And also the line:


ALTER TABLE mucRoom DROP CONSTRAINT mucRoom_pk;

 


SQL Server


The SQL server scripts had problems in version 18, which will automatically take care of itself when you upgrade to 3.6.0a.


 


DB2


As far as I can tell from the reports that came in, no one tried this.  This is good because it's upgrade was complex.  If you are having trouble with the DB2 upgrade, post a reply here and we'll work through it.


 


 


Embedded DB (HSQLDB)


Similar to the Oracle issues, you will need to, after upgrading the openfire package, edit resources/database/upgrade/17/openfire_hsqldb.sql and remove everything above:


// add new indexed column to mucRoom
ALTER TABLE mucRoom ADD COLUMN serviceID BIGINT BEFORE roomID;
CREATE INDEX mucRoom_serviceid_idx ON mucRoom(serviceID);

 

Ok, How Can I Get It?

 

You can read more about the highlights here.

 

The complete set of changes can be found at: http://www.igniterealtime.org/builds/openfire/docs/latest/changelog.html

Download Openfire from: http://www.igniterealtime.org/downloads/index.jsp

Download Connection Manager from: http://www.igniterealtime.org/projects/openfire/connection_manager.jsp

 

 

Many thanks to everyone who helped debug issues, provide patches, and generally work with me getting this cleaned up!

Tags: openfire, release
  • Daniel Henninger KeyContributor
    Daniel Henninger
    2,972 posts since
    Aug 10, 2005
    Currently Being Moderated
    Aug 28, 2008 9:35 PM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    And -please- back up your installation root and database (if you need help with that, it's in the upgrade docs) before upgrading always.  It's always an excellent idea to be ready to back out in case there are problems!  (with any server software updates!)  =)  Let me know if you run into problems and I'll try to help you in the morning.

  • Jonas Silver
    Jonas
    110 posts since
    Oct 19, 2006
    Currently Being Moderated
    Aug 29, 2008 8:23 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    If it helps for your mood Daniel:

     

    I updated from 3.6.0 to 3.6.0a and it seems to work flawlessly now (or lets say...almost. Let's not get too enthusiastic ).

     

    LDAP errors are gone, Login works, groups are synced, external messengers work, admin login works and even the TEST-Button for LDAP works (°yay°)

     

    I'll keep an eye on the system to see if no other new issues occur...

     

     

    2 issues:

     

    1. Everything ONLY works with ldap.encloseDNs set to false. I have no idea if that causes any other issues, but I think you set it true for a reason? Removing it or setting it to true brakes everything.

     

    2. My backend keeps saying that it is 3.6.0 and that 3.6.0a is now available, even though I am pretty sure I downloaded/installed the right file (the *.deb to be precise)

     

     

    EDIT:

     

    Oh and FYI:

     

    If you remember my 2 entries for LDAP Debugging in the DB:

     

    Changing the LDAP Debug Button in the Adminbackend toggles the ldap.ldapDebugEnabled in the DB and leaves the ldap.debugEnabled untouched, so this might be a kind of leftover...

  • scottr Bronze
    scottr
    28 posts since
    Jun 8, 2007
    Currently Being Moderated
    Aug 29, 2008 9:27 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    MySQL 4.1.22 on Mac OS X Server 10.4.11 hates the upgrade. Manually applying the database changes resulted in an upgrade/14/openfire_mysql.sql error:

     

    ERROR 1170 (42000) at line 5: BLOB/TEXT column 'jid' used in key specification without a key length

     

    I ignored this, which later resulted in upgrade/19/openfire_mysql.sql errors:

     

    ERROR 1091 (42000) at line 39: Can't DROP 'jiveRoster_jid_idx'; check that column/key exists

    ERROR 1170 (42000) at line 42: BLOB/TEXT column 'jid' used in key specification without a key length

    Note that this is all the same index. Attempting to change the 'jid' column from "text" to "varchar(1024)" on my system didn't change a thing (it's still a "text' column).
    I've gotten it running without the index for now. Not sure what this will break.

  • Nulani t'Acraya Bronze
    Nulani t'Acraya
    20 posts since
    Jan 7, 2008
    Currently Being Moderated
    Aug 29, 2008 9:38 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Has anyone had any luck upgrading using the .deb package on Debian Etch? It seems to absolutely refuse to have anything to do with my database - that is, once it's given the login information it does nix-nada.

     

    Upgrade is from 3.5.2 and the database is MySQL.

  • wroot KeyContributor
    wroot
    7,044 posts since
    Jan 24, 2005
    Currently Being Moderated
    Aug 29, 2008 11:10 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Just FYI, clean 3.5.2 (not touched, embedded-db) upgrade to 3.6.0a. All fine. Just Admin Console shows that there is 3.6.0a available

     

    Upgraded IM Gateway - fine too.

     

    Now i'll digg the changelog and check out all the changes and new features. Btw, about backups. I dont like to do them, or i never do them before upgrade. Because i have setup them (backup scripts) to do this automatically for me

    • kkimber Bronze
      kkimber
      17 posts since
      Aug 27, 2008
      Currently Being Moderated
      Aug 30, 2008 3:49 AM (in response to wroot)
      Re: Openfire 3.6.0a has been released!

      I don't believe you.

       

      3.5.2 to 3.6.0a installing (normally failed, .sql file editing) done.

       

      Updating im gateway 1.2.4.c

       

      but all users, im gateway plugin registrations gone! and cannot adding im gateway registrations server side or client side (spark 2.5.8/2.6beta).

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:42 PM (in response to wroot)
      Re: Openfire 3.6.0a has been released!

      wroot wrote:

       

      Just FYI, clean 3.5.2 (not touched, embedded-db) upgrade to 3.6.0a. All fine. Just Admin Console shows that there is 3.6.0a available

       

      Upgraded IM Gateway - fine too.

       

      Now i'll digg the changelog and check out all the changes and new features. Btw, about backups. I dont like to do them, or i never do them before upgrade. Because i have setup them (backup scripts) to do this automatically for me

      *laugh*  Well that's good that you do regular backups, and IMO is just as good in this scenario as long as you don't mind losing the data from "right before upgrade" to "last backup".  =)

  • jaysonben Bronze
    jaysonben
    3 posts since
    Aug 29, 2008
    Currently Being Moderated
    Aug 29, 2008 3:56 PM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    I ran the upgrade from 3.5.2 to 3.6.0a and everything went smoothly until I tried to log into the admin console.  All admin passwords had been erases.  I went into the conf\openfire.xml and modified it so I could rerun the setup.  Did that and then set myself up as an admin again.  I tried logging in a little later and my password had been deleted again.  The really funny thing is, I could still log into Spark and chat.  I have Openfire running in a Windows domain envrionment.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:35 PM (in response to jaysonben)
      Re: Openfire 3.6.0a has been released!

      jaysonben wrote:

       

      I ran the upgrade from 3.5.2 to 3.6.0a and everything went smoothly until I tried to log into the admin console.  All admin passwords had been erases.  I went into the conf\openfire.xml and modified it so I could rerun the setup.  Did that and then set myself up as an admin again.  I tried logging in a little later and my password had been deleted again.  The really funny thing is, I could still log into Spark and chat.  I have Openfire running in a Windows domain envrionment.

       

      do you see anything in the error logs when you try to log in?  it most certainly should not "lose" your admin user list.  One thing you can check is under system properties there will be a property called 'admin.authorizedJIDs', make sure that that has the proper list of users in it.

  • Marcelo Terres Bronze
    Marcelo Terres
    26 posts since
    Nov 8, 2007
    Currently Being Moderated
    Aug 30, 2008 6:57 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Hi.

     

    I downloaded and installed version 3.6.0a (using .tar.gz). Now when I log in admin console the version still appears as 3.6.0 and the message to upgrade to version 3.6.0a is still there.

     

    I did it 3 times in 2 different servers with the same results. What could be wrong ?

     

    Regards,

     

    Marcelo Terres

    • wroot KeyContributor
      wroot
      7,044 posts since
      Jan 24, 2005
      Currently Being Moderated
      Aug 30, 2008 7:08 AM (in response to Marcelo Terres)
      Re: Openfire 3.6.0a has been released!

      mhterres wrote:

       

      I did it 3 times in 2 different servers with the same results. What could be wrong ?

      You should read the first message.

       

      Daniel wrote:

       

      After upgrading to 3.6.0a, you will still see 3.6.0 in the admin console, so please don't be confused by that.


      Until 3.6.1 is realeased you shouldn't bother about that message in Admin Console. 3.6.0a was a fix of 3.6.0 so that's why it is showing as 3.6.0 i suppose.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:45 PM (in response to Marcelo Terres)
      Re: Openfire 3.6.0a has been released!

      mhterres wrote:

       

      Hi.

       

      I downloaded and installed version 3.6.0a (using .tar.gz). Now when I log in admin console the version still appears as 3.6.0 and the message to upgrade to version 3.6.0a is still there.

       

      I did it 3 times in 2 different servers with the same results. What could be wrong ?

       

      Regards,

       

      Marcelo Terres

      Hi I mentioned that in the release announcement =P  It will show as 3.6.0 'cause frankly, there's no way to make it be 3.6.0 officially in the code.  So 3.6.0a is really just a "replacement bugfix" for 3.6.0.  So basically, no need to be concerned over that!

  • tnt Bronze
    tnt
    14 posts since
    Aug 23, 2006
    Currently Being Moderated
    Aug 30, 2008 10:37 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    since upgrade from 3.5.2 to 3.6.0 users are getting disconnected the same second they login.

     

    many of them have "reconnect if disconnected" set so then keep loging in and out.

     

     

    • tnt Bronze
      tnt
      14 posts since
      Aug 23, 2006
      Currently Being Moderated
      Aug 30, 2008 1:03 PM (in response to tnt)
      Re: Openfire 3.6.0a has been released!

      same problem with 3.6.0a

       

      • Daniel Henninger KeyContributor
        Daniel Henninger
        2,972 posts since
        Aug 10, 2005
        Currently Being Moderated
        Sep 1, 2008 4:46 PM (in response to tnt)
        Re: Openfire 3.6.0a has been released!

        tnt wrote:

         

        same problem with 3.6.0a

         

        Seeing anything in your error logs?  Thre should be some exceptions indicating why it's doing that.

        • tnt Bronze
          tnt
          14 posts since
          Aug 23, 2006
          Currently Being Moderated
          Sep 2, 2008 12:43 PM (in response to Daniel Henninger)
          Re: Openfire 3.6.0a has been released!

          jadestorm wrote:

           

          tnt wrote:

           

          same problem with 3.6.0a

           

          Seeing anything in your error logs?  Thre should be some exceptions indicating why it's doing that.

           

           

          my server was 3.5.2 and worked flawlessly until upgrade to 3.6.0 when user-disconnecting issue appeared.

          after upgrading to 3.6.0a situatin is the same. you've asked for logs, so here they are (I know that there's a lot of unresolved DNS reqs, but they were around for a quite long time and everything worked well).

           

          I've blocked ports 5222 and 5223 for everyone except me and started openfire (3.6.0a).

          everything went fine and I got no new lines in error and warn logs, just following in info log:

           

          tail -f -n0 /opt/openfire/logs/info.log
          2008.09.02 21:22:21 Publish-Subscribe domain: pubsub.b44.bg.wi
          2008.09.02 21:22:21 Multi User Chat domain: conference.b44.bg.wi
          2008.09.02 21:22:21 Openfire 3.6.0 [Sep 2, 2008 9:22:21 PM]
          2008.09.02 21:22:23 Admin console listening at:
            http://b44.bg.wi:9090
            https://b44.bg.wi:9091
          2008.09.02 21:22:25 Packet Filter loaded...
          2008.09.02 21:22:26 Started server (unencrypted) socket on port: 5269
          2008.09.02 21:22:26 Started plain (unencrypted) socket on port: 5222
          2008.09.02 21:22:26 Started SSL (encrypted) socket on port: 5223

           

           

          then I've tried to connect my client (PSI 0.12) to openfire and got this in error log:

           

          tail -f -n0 /opt/openfire/logs/error.log
          2008.09.02 21:35:49 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: julino.bg.wi(DNS lookup: julino.bg.wi:5269)
          java.net.ConnectException: Connection refused
                  at java.net.PlainSocketImpl.socketConnect(Native Method)
                  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
                  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:49 [org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHand ler.java:135)] Closing connection due to error while processing message: <iq xmlns="jabber:client" type="result" to="no1@b70.bg.wi/Miranda" >
          <query xmlns="jabber:iq:version">
          <name>Psi</name>
          <version>0.12</version>
          <os>Gentoo Base System release 2.0.0</os>
          </query>
          </iq>
          java.lang.NullPointerException
                  at java.util.concurrent.ConcurrentHashMap.remove(ConcurrentHashMap.java:922)
                  at org.jivesoftware.openfire.IQRouter.handle(IQRouter.java:284)
                  at org.jivesoftware.openfire.IQRouter.route(IQRouter.java:101)
                  at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:68)
                  at org.jivesoftware.openfire.net.StanzaHandler.processIQ(StanzaHandler.java:311)
                  at org.jivesoftware.openfire.net.ClientStanzaHandler.processIQ(ClientStanzaHandler .java:79)
                  at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:276)
                  at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:175)
                  at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:133)
                  at org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.messageReceived (AbstractIoFilterChain.java:570)
                  at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
                  at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
                  at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
                  at org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
                  at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
                  at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
                  at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
                  at org.apache.mina.filter.codec.support.SimpleProtocolDecoderOutput.flush(SimplePr otocolDecoderOutput.java:58)
                  at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecF ilter.java:185)
                  at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
                  at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
                  at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
                  at org.apache.mina.common.IoFilterAdapter.messageReceived(IoFilterAdapter.java:80)
                  at org.jivesoftware.openfire.plugin.RawPrintFilter.messageReceived(RawPrintFilter. java:57)
                  at org.apache.mina.common.support.AbstractIoFilterChain.callNextMessageReceived(Ab stractIoFilterChain.java:299)
                  at org.apache.mina.common.support.AbstractIoFilterChain.access$1100(AbstractIoFilt erChain.java:53)
                  at org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.messageReceive d(AbstractIoFilterChain.java:648)
                  at org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java :239)
                  at org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(Execut orFilter.java:283)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:49 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: eon.bg.wi(DNS lookup: eon.bg.wi:5269)
          java.net.UnknownHostException: eon.bg.wi
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:50 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: ap3.lb.bg.wi(DNS lookup: ap3.lb.bg.wi:5269)
          java.net.ConnectException: Connection refused
                  at java.net.PlainSocketImpl.socketConnect(Native Method)
                  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
                  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:50 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: zemun.bg.wi(DNS lookup: zemun.bg.wi:5269)
          java.net.SocketException: Network is unreachable
                  at java.net.PlainSocketImpl.socketConnect(Native Method)
                  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
                  at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:50 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: b30.bg.wi(DNS lookup: b30.bg.wi:5269)
          java.net.UnknownHostException: b30.bg.wi
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:50 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: titel.wi(DNS lookup: titel.wi:5269)
          java.net.UnknownHostException: titel.wi
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:51 [org.jivesoftware.openfire.net.SocketReadingMode.negotiateTLS(SocketReadingMode .java:77)] Error while negotiating TLS: org.jivesoftware.openfire.net.SocketConnection@7bff1855 socket: Socket[addr=/10.5.44.66,port=39988,localport=5269] session: org.jivesoftware.openfire.session.LocalIncomingServerSession@68fae256 status: 1 address: b44.bg.wi/578d762c id: 578d762c
          javax.net.ssl.SSLException: Unsupported record version Unknown-47.115
                  at com.sun.net.ssl.internal.ssl.EngineInputRecord.bytesInCompletePacket(EngineInpu tRecord.java:97)
                  at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:754 )
                  at com.sun.net.ssl.internal.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:669)
                  at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:607)
                  at org.jivesoftware.openfire.net.TLSStreamHandler.doHandshake(TLSStreamHandler.jav a:214)
                  at org.jivesoftware.openfire.net.TLSStreamHandler.start(TLSStreamHandler.java:160)
                  at org.jivesoftware.openfire.net.SocketConnection.startTLS(SocketConnection.java:1 69)
                  at org.jivesoftware.openfire.net.SocketReadingMode.negotiateTLS(SocketReadingMode. java:74)
                  at org.jivesoftware.openfire.net.BlockingReadingMode.readStream(BlockingReadingMod e.java:127)
                  at org.jivesoftware.openfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 63)
                  at org.jivesoftware.openfire.net.SocketReader.run(SocketReader.java:120)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:51 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)] Error trying to connect to remote server: wi(DNS lookup: wi:5269)
          java.net.UnknownHostException: wi
                  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
                  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
                  at java.net.Socket.connect(Socket.java:519)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
                  at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:185)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
                  at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
                  at java.lang.Thread.run(Thread.java:619)
          2008.09.02 21:35:51 [org.jivesoftware.openfire.net.SocketReadingMode.negotiateTLS(SocketReadingMode .java:77)] Error while negotiating TLS: org.jivesoftware.openfire.net.SocketConnection@48bfba23 socket: Socket[addr=/10.5.22.1,port=51981,localport=5269] session: org.jivesoftware.openfire.session.LocalIncomingServerSession@4344a263 status: 1 address: b44.bg.wi/e6a3a0a3 id: e6a3a0a3
          javax.net.ssl.SSLException: Unsupported record version Unknown-47.115
                  at com.sun.net.ssl.internal.ssl.EngineInputRecord.bytesInCompletePacket(EngineInpu tRecord.java:97)
                  at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:754 )
                  at com.sun.net.ssl.internal.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:669)
                  at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:607)
                  at org.jivesoftware.openfire.net.TLSStreamHandler.doHandshake(TLSStreamHandler.jav a:214)
                  at org.jivesoftware.openfire.net.TLSStreamHandler.start(TLSStreamHandler.java:160)
                  at org.jivesoftware.openfire.net.SocketConnection.startTLS(SocketConnection.java:1 69)
                  at org.jivesoftware.openfire.net.SocketReadingMode.negotiateTLS(SocketReadingMode. java:74)
                  at org.jivesoftware.openfire.net.BlockingReadingMode.readStream(BlockingReadingMod e.java:127)
                  at org.jivesoftware.openfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 63)
                  at org.jivesoftware.openfire.net.SocketReader.run(SocketReader.java:120)
                  at java.lang.Thread.run(Thread.java:619)

           

           

          and this in info log:

           

          2008.09.02 21:35:51 Packet sent to unreachable address
          <iq type="get" id="214-14237" to="tnt@b44.bg.wi/Psi" from="centar.bg.wi">
            <query xmlns="http://jabber.org/protocol/disco#info"/>
          </iq>
          2008.09.02 21:35:51 Packet sent to unreachable address
          <iq type="get" id="768-14238" to="tnt@b44.bg.wi/Psi" from="centar.bg.wi">
            <query xmlns="http://jabber.org/protocol/disco#info"/>
          </iq>
          2008.09.02 21:35:51 Packet sent to unreachable address
          <iq type="get" id="275-5582" to="tnt@b44.bg.wi/Psi" from="bkosa.bg.wi">
            <query xmlns="http://jabber.org/protocol/disco#info"/>
          </iq>
          2008.09.02 21:35:51 Packet sent to unreachable address
          <iq type="get" id="833-5583" to="tnt@b44.bg.wi/Psi" from="bkosa.bg.wi">
            <query xmlns="http://jabber.org/protocol/disco#info"/>
          </iq>

           

           

          again, server configuration is:

           

          Server version: 5.0.60 Gentoo Linux mysql-5.0.60-r1

           

          Portage 2.1.4.4 (default/linux/amd64/2008.0, gcc-4.2.4, glibc-2.7-r2, 2.6.24-gentoo-r8 x86_64)
          =================================================================
          System uname: 2.6.24-gentoo-r8 x86_64 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
          Timestamp of tree: Tue, 02 Sep 2008 01:00:01 +0000
          distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
          app-shells/bash:     3.2_p33
          dev-java/java-config: 1.3.7, 2.1.6
          dev-lang/python:     2.4.4-r13, 2.5.2-r6
          dev-python/pycrypto: 2.0.1-r6
          sys-apps/baselayout: 1.12.11.1
          sys-apps/sandbox:    1.2.18.1-r2
          sys-devel/autoconf:  2.61-r2
          sys-devel/automake:  1.9.6-r2, 1.10.1
          sys-devel/binutils:  2.18-r3
          sys-devel/gcc-config: 1.4.0-r4
          sys-devel/libtool:   1.5.26
          virtual/os-headers:  2.6.23-r3

  • sab0900 Bronze
    sab0900
    7 posts since
    Jan 10, 2008
    Currently Being Moderated
    Aug 30, 2008 8:25 PM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Links to download the update still don't work.  But after looking at this thread, I would say the links not working is a good thing for now.  It appears that testing on 4 systems doesn't equate to a proper beta test.  This is why most software companies beta test on 10's or 100's of systems before an official stable release.

     

    This reminds me of this programmer I once worked with.  His most common response to an inquiry as to why his "stable release" apps didn't work was, "Well it works on my laptop."

    • wroot KeyContributor
      wroot
      7,044 posts since
      Jan 24, 2005
      Currently Being Moderated
      Aug 31, 2008 1:54 AM (in response to sab0900)
      Re: Openfire 3.6.0a has been released!

      Well, i think we can count 10 or more users (including me), who can say "it works on my laptop". So there is no difference 4 or 100, you still cant simulate every environment and situation.

       

      Also, everyone reporting a problem should specify more information about they setup and upgrade process (DB, OS, which version it was upgraded to first).

      • wroot KeyContributor
        wroot
        7,044 posts since
        Jan 24, 2005
        Currently Being Moderated
        Aug 31, 2008 1:56 AM (in response to wroot)
        Re: Openfire 3.6.0a has been released!

        Oh, i just agree with Daryl and others, that this release (3.6.0) should be released as Beta first. As this is a community driven software (should be), so beta test could be done by 100's completely different systems.

        • Daniel Henninger KeyContributor
          Daniel Henninger
          2,972 posts since
          Aug 10, 2005
          Currently Being Moderated
          Sep 1, 2008 4:49 PM (in response to wroot)
          Re: Openfire 3.6.0a has been released!

          wroot wrote:

           

          Oh, i just agree with Daryl and others, that this release (3.6.0) should be released as Beta first. As this is a community driven software (should be), so beta test could be done by 100's completely different systems.

          I agree.  Things got away from us and messed up our release procedure.  Doesn't really matter what the reasons are though, should have gotten one out.  I apologize for that.

      • tnt Bronze
        tnt
        14 posts since
        Aug 23, 2006
        Currently Being Moderated
        Aug 31, 2008 3:34 PM (in response to wroot)
        Re: Openfire 3.6.0a has been released!

        upgrade was from openfire 3.5.2 to 3.6.0

         

        Server version: 5.0.60 Gentoo Linux mysql-5.0.60-r1

         

        Portage 2.1.4.4 (default/linux/amd64/2008.0, gcc-4.2.4, glibc-2.7-r2, 2.6.24-gentoo-r8 x86_64)
        =================================================================
        System uname: 2.6.24-gentoo-r8 x86_64 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
        app-shells/bash:     3.2_p33
        dev-java/java-config: 1.3.7, 2.1.6
        dev-lang/python:     2.4.4-r13, 2.5.2-r6
        dev-python/pycrypto: 2.0.1-r6
        sys-apps/baselayout: 1.12.11.1
        sys-apps/sandbox:    1.2.18.1-r2
        sys-devel/autoconf:  2.61-r2
        sys-devel/automake:  1.9.6-r2, 1.10.1
        sys-devel/binutils:  2.18-r3
        sys-devel/gcc-config: 1.4.0-r4
        sys-devel/libtool:   1.5.26
        virtual/os-headers:  2.6.23-r3

         

         

        My users and me can see list of online contacts for about one second before disconnecting.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:47 PM (in response to sab0900)
      Re: Openfire 3.6.0a has been released!

      sab0900 wrote:

       

      Links to download the update still don't work.  But after looking at this thread, I would say the links not working is a good thing for now.  It appears that testing on 4 systems doesn't equate to a proper beta test.  This is why most software companies beta test on 10's or 100's of systems before an official stable release.

       

      This reminds me of this programmer I once worked with.  His most common response to an inquiry as to why his "stable release" apps didn't work was, "Well it works on my laptop."

      *laugh*  I think you read too much into that.  I tested it live on 4 servers that I run.  I tested it locally on 8 separate installs with different data.  Then another 12 iterations.

  • jcorreia Bronze
    jcorreia
    113 posts since
    Mar 29, 2005
    Currently Being Moderated
    Aug 31, 2008 7:53 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    just to add some feedback.

    Clean install in Centos5 is working ok.

     

    Although I had an error on intall with the .rpm version : "JAVA_HOME not found "(or something like that) error . It´s odd, but I fixed it putting "JAVA_HOME=/opt/openfire/jre" in /etc/sysconfig/openfire.

    Thanks

  • Ville Walveranta Bronze
    Ville Walveranta
    9 posts since
    Jun 24, 2008
    Currently Being Moderated
    Sep 1, 2008 2:30 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Ok, upgrade complete... but it wasn't a totally smooth upgrade.

     

    Firstly, for some reason my database was using version 14 (I was upgrading from 3.5.2), so I had to manually apply update scripts from 15 onward. Everything went fine until script 19 where I got lots of errors:

     

    ---

    Found old database version 18 for openfire. Upgrading to version 20...
    Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.
    java.lang.IllegalArgumentException: java.sql.SQLException: Invalid object name 'ofID'.
        at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:710)
        at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:427)
        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)
        at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:51)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
        at com.exe4j.runtime.WinLauncher.main(Unknown Source)
    Caused by: java.sql.SQLException: Invalid object name 'ofID'.
        at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
        at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
        at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)
        at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)
        at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
        at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatem ent.java:777)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:100)
        at org.logicalcobwebs.proxool.ProxyStatement.intercept(ProxyStatement.java:57)
        at $java.sql.Statement$$EnhancerByProxool$$67135b2b.executeQuery(<generated>)
        at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:700)
        ... 16 more
    Error starting the server. Please check the log files for more information.
    Server halted

    ---

     

    Even though it said "Found old database version 18 for openfire.", the 3.5.2 database was version 14 (i.e. changes from script 14 were present, but not those from script 15). Perhaps it was supposed to be that way, and perhaps the Openfire upgrade process had upgraded the database from 14 to 18, and since script 19 had failed, it had stopped there.

     

    The problem with the script 18 was number of "Incorrect syntax near 'sp_rename'." errors and nothing got done. Looking on the web I found this page where it was suggested that "exec" could be added in front of sp_rename commands. I did so, and the script 19 (and then subsequently the script 20) completed (i.e. the table renames were done).  With the script 19 I did still get lots of warnings, but perhaps they can be safely ignored:

     

    ---

    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Warning! The maximum key length is 900 bytes. The index 'ofRoster_jid_idx' has maximum length of 2048 bytes. For some combination of large values, the insert/update operation will fail.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Warning! The maximum key length is 900 bytes. The index 'ofSASLAuthorized_pk' has maximum length of 4128 bytes. For some combination of large values, the insert/update operation will fail.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.
    Caution: Changing any part of an object name could break scripts and stored procedures.

     

    Query OK, -1 rows affected (515 ms)

    ---

     

    As far as I can tell, Openfire 3.6.0 is now working ok on my server.

     

    This is small LAN server running a Windows 2003 Standard edition with SQL Server 2005.

     

    Thanks for the new version!

     

    Ville

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:53 PM (in response to Ville Walveranta)
      Re: Openfire 3.6.0a has been released!

      *blink*  I wonder why it thought you were at 18??  Any chance you had attempted the upgrade before and had it fail?  I wonder if it found ofVersion from a previous attempt and was reading from there?  Either way I'm glad you got running and sorry for the trouble!

      Ville wrote:

       

      Ok, upgrade complete... but it wasn't a totally smooth upgrade.

       

      Firstly, for some reason my database was using version 14 (I was upgrading from 3.5.2), so I had to manually apply update scripts from 15 onward. Everything went fine until script 19 where I got lots of errors:

       

      ---

      Found old database version 18 for openfire. Upgrading to version 20...
      Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.
      java.lang.IllegalArgumentException: java.sql.SQLException: Invalid object name 'ofID'.
          at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:710)
          at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:427)
          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)
          at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:51)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
          at java.lang.reflect.Method.invoke(Unknown Source)
          at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
          at com.exe4j.runtime.WinLauncher.main(Unknown Source)
      Caused by: java.sql.SQLException: Invalid object name 'ofID'.
          at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
          at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
          at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)
          at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)
          at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
          at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatem ent.java:777)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
          at java.lang.reflect.Method.invoke(Unknown Source)
          at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:100)
          at org.logicalcobwebs.proxool.ProxyStatement.intercept(ProxyStatement.java:57)
          at $java.sql.Statement$$EnhancerByProxool$$67135b2b.executeQuery(<generated>)
          at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:700)
          ... 16 more
      Error starting the server. Please check the log files for more information.
      Server halted

      ---

       

      Even though it said "Found old database version 18 for openfire.", the 3.5.2 database was version 14 (i.e. changes from script 14 were present, but not those from script 15). Perhaps it was supposed to be that way, and perhaps the Openfire upgrade process had upgraded the database from 14 to 18, and since script 19 had failed, it had stopped there.

       

      The problem with the script 18 was number of "Incorrect syntax near 'sp_rename'." errors and nothing got done. Looking on the web I found this page where it was suggested that "exec" could be added in front of sp_rename commands. I did so, and the script 19 (and then subsequently the script 20) completed (i.e. the table renames were done).  With the script 19 I did still get lots of warnings, but perhaps they can be safely ignored:

       

      ---

      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Warning! The maximum key length is 900 bytes. The index 'ofRoster_jid_idx' has maximum length of 2048 bytes. For some combination of large values, the insert/update operation will fail.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Warning! The maximum key length is 900 bytes. The index 'ofSASLAuthorized_pk' has maximum length of 4128 bytes. For some combination of large values, the insert/update operation will fail.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.
      Caution: Changing any part of an object name could break scripts and stored procedures.

       

      Query OK, -1 rows affected (515 ms)

      ---

       

      As far as I can tell, Openfire 3.6.0 is now working ok on my server.

       

      This is small LAN server running a Windows 2003 Standard edition with SQL Server 2005.

       

      Thanks for the new version!

       

      Ville

      • Ville Walveranta Bronze
        Ville Walveranta
        9 posts since
        Jun 24, 2008
        Currently Being Moderated
        Sep 1, 2008 5:23 PM (in response to Daniel Henninger)
        Re: Openfire 3.6.0a has been released!

        Not to this version. The restored database was 3.5.2, and it had never been attempted to be upgraded. Of course, it may have been that on the *first* start of Openfire 3.6.0 it correctly would've showed the level (14 or whatever) but since the 19th upgrade script didn't work, it stalled there, and on the next try (when I paid attention to the version) it was then 18.

         

        Do you think it might be a good idea to prefix the sp_rename commands with "exec" in the future?

        • Daniel Henninger KeyContributor
          Daniel Henninger
          2,972 posts since
          Aug 10, 2005
          Currently Being Moderated
          Sep 2, 2008 5:05 AM (in response to Ville Walveranta)
          Re: Openfire 3.6.0a has been released!

          Ville wrote:

           

          Not to this version. The restored database was 3.5.2, and it had never been attempted to be upgraded. Of course, it may have been that on the *first* start of Openfire 3.6.0 it correctly would've showed the level (14 or whatever) but since the 19th upgrade script didn't work, it stalled there, and on the next try (when I paid attention to the version) it was then 18.

           

          Do you think it might be a good idea to prefix the sp_rename commands with "exec" in the future?

          So when you added exec it started working ok?  What version of SQL server are you using?

          • Ville Walveranta Bronze
            Ville Walveranta
            9 posts since
            Jun 24, 2008
            Currently Being Moderated
            Sep 2, 2008 11:30 AM (in response to Daniel Henninger)
            Re: Openfire 3.6.0a has been released!

            Yes, with sp_rename's prefixed with "exec" the script 19 completed, though with warnings (as listed in the original comment). The tables were renamed, despite of the warnings, so it seems it completed ok. The script 20 completed after that, and Openfire is working as far as I can tell.

             

            I'm using SQL Server 2005 Enterprise (the exact version is SQL Server 9.0.3068).

  • VeNT Bronze
    VeNT
    2 posts since
    Sep 1, 2008
    Currently Being Moderated
    Sep 1, 2008 5:33 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    Double Post

    • VeNT Bronze
      VeNT
      2 posts since
      Sep 1, 2008
      Currently Being Moderated
      Sep 1, 2008 5:34 AM (in response to VeNT)
      Re: Openfire 3.6.0a has been released!

      I'm now getting a really annoying issue

      no-ones showing as online!

      all my users can login but non can send messages!

      logs showing these messages but I don't know what they mean!

       

      line
      2241
      2242
      2243
      2244
      2245
      2246
      2247
      2248
      2249
      2250
      2251
      2252
      2253
      2254
      2255
      2256
      2257
      2258
      2259
      2260
      2261
      2262
      2263
      2264
      2265
      2266
      2267
      2268
      2269
      2270
      2271
      2272
      2273
      2274
      2275
      2276
      2277
      2278
      2279
      2280
      2281
      2282
      2283
      2284
      2285
      2286
      2287
      2288
      2289
      2290      		at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      2008.09.01 13:26:47 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
      ] Error trying to connect to remote server: office(DNS lookup: office:5269)
      java.net.UnknownHostException: office
      at java.net.PlainSocketImpl.connect(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      2008.09.01 13:26:58 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
      ] Error trying to connect to remote server: office(DNS lookup: office:5269)
      java.net.UnknownHostException: office
      at java.net.PlainSocketImpl.connect(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      2008.09.01 13:27:37 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
      ] Error trying to connect to remote server: office(DNS lookup: office:5269)
      java.net.UnknownHostException: office
      at java.net.PlainSocketImpl.connect(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
      at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
      at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      2008.09.01 13:29:13 [org.jivesoftware.util.log.util.CommonsLogFactory$1.error(CommonsLogFactory.jav a:88)
      ] Line=19 The content of element type "dwr" must match "(init?,allow?,signatures?)".
      • Daniel Henninger KeyContributor
        Daniel Henninger
        2,972 posts since
        Aug 10, 2005
        Currently Being Moderated
        Sep 1, 2008 4:57 PM (in response to VeNT)
        Re: Openfire 3.6.0a has been released!

        Is your server called "office"?  What does it say in the admin console?  Does it say office there?  What appears to be happening is it's trying a server to server connection for what is probably supposed to be itself, which is clearly wrong behavior, but I want to get the whole scenario first.

        VeNT wrote:

         

        I'm now getting a really annoying issue

        no-ones showing as online!

        all my users can login but non can send messages!

        logs showing these messages but I don't know what they mean!

         

        line
        2241
        2242
        2243
        2244
        2245
        2246
        2247
        2248
        2249
        2250
        2251
        2252
        2253
        2254
        2255
        2256
        2257
        2258
        2259
        2260
        2261
        2262
        2263
        2264
        2265
        2266
        2267
        2268
        2269
        2270
        2271
        2272
        2273
        2274
        2275
        2276
        2277
        2278
        2279
        2280
        2281
        2282
        2283
        2284
        2285
        2286
        2287
        2288
        2289
        2290        		at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        2008.09.01 13:26:47 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
        ] Error trying to connect to remote server: office(DNS lookup: office:5269)
        java.net.UnknownHostException: office
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        2008.09.01 13:26:58 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
        ] Error trying to connect to remote server: office(DNS lookup: office:5269)
        java.net.UnknownHostException: office
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        2008.09.01 13:27:37 [org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSes sion(LocalOutgoingServerSession.java:258)
        ] Error trying to connect to remote server: office(DNS lookup: office:5269)
        java.net.UnknownHostException: office
        at java.net.PlainSocketImpl.connect(Unknown Source)
        at java.net.SocksSocketImpl.connect(Unknown Source)
        at java.net.Socket.connect(Unknown Source)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.createOutgoingSess ion(LocalOutgoingServerSession.java:253)
        at org.jivesoftware.openfire.session.LocalOutgoingServerSession.authenticateDomain (LocalOutgoingServerSession.java:144)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:239)
        at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        2008.09.01 13:29:13 [org.jivesoftware.util.log.util.CommonsLogFactory$1.error(CommonsLogFactory.jav a:88)
        ] Line=19 The content of element type "dwr" must match "(init?,allow?,signatures?)".
  • Steve Major Bronze
    Steve Major
    19 posts since
    Aug 17, 2005
    Currently Being Moderated
    Sep 1, 2008 4:00 PM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    I understand that the admin console will only show 3.6.0, but should Openfire keep IM'ing my Admin account daily that 3.6.0a is available?  It's annoying, but only every 24 hours or so.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 1, 2008 4:56 PM (in response to Steve Major)
      Re: Openfire 3.6.0a has been released!

      majorsl wrote:

       

      I understand that the admin console will only show 3.6.0, but should Openfire keep IM'ing my Admin account daily that 3.6.0a is available?  It's annoying, but only every 24 hours or so.

      I must admit I don't know why it's doing that --- except that it's confused between what can be locally represented and what the package is called.  Sigh.  Try going into system properties and setting this to false: update.notify-admins

       

      That'll shut up the notifications!

  • kevgau Bronze
    kevgau
    3 posts since
    Jul 16, 2008
    Currently Being Moderated
    Sep 2, 2008 2:41 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    I had a quick and bad experience upgrading from 3.5.2 to 3.6.0a (Win2003, embedded db) :

    - unstable client connections

    - search plugin not working

    - random ldap authentication, my admin account and workstation IP becoming blacklisted because of too many bad connection attempts.

     

    So I reverted the server to my 3.5.2 backup... which could not start anymore (main class not found).

     

    I had to restart the 3.5.2 install executable and copy the backed-up conf and embedded db to make things work again.

     

    Next time, please put a "beta" label on early releases.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 2, 2008 5:06 AM (in response to kevgau)
      Re: Openfire 3.6.0a has been released!

      Hrm, well there's not a lot I can do to try to track down what's actually going on here if you aren't providing me with any debug information or error logs.  Sorry you had a bad experience but good that you actually backed up as is suggested in the upgrade docs.

      kevgau wrote:

       

      I had a quick and bad experience upgrading from 3.5.2 to 3.6.0a (Win2003, embedded db) :

      - unstable client connections

      - search plugin not working

      - random ldap authentication, my admin account and workstation IP becoming blacklisted because of too many bad connection attempts.

       

      So I reverted the server to my 3.5.2 backup... which could not start anymore (main class not found).

       

      I had to restart the 3.5.2 install executable and copy the backed-up conf and embedded db to make things work again.

       

      Next time, please put a "beta" label on early releases.

  • MCapelle Bronze
    MCapelle
    1 posts since
    Sep 2, 2008
    Currently Being Moderated
    Sep 2, 2008 8:33 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    I was one of the unfortunate who tried to go to 3.6.0 right away from 3.5.2.  My install broke and I read the forums saying there would be a fix release.  I just tried the 3.6.0a rpm, but I am still broken .

     

    The error.log spews out "java.sql.Exception: Table not found in statement [SELECT count(*) FROM ofID]" errors and info.log has "Found old database version 16 for openfire.  Upgrading to version 20..." and "Server halted" errors.

     

    My suspicion for my broken installation is the old DB.  I am using the embedded DB btw.  I am no DBA, but from what I gather I can run the upgrade manually?   How would I do that?  I tried the embedded-db-viewer.sh script located in the openfire /bin directory, but that errors out with "Exception in thread "main" java.lang.NoClassDefFoundError: org/hsqldb/util/DatabaseManagerSwing".

     

    What are my options?  

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 2, 2008 10:30 AM (in response to MCapelle)
      Re: Openfire 3.6.0a has been released!

      If it says upgrading from 16 to 20, and doesn't upgrade anything, then 17 is the script that's causing you problems.  Embedded db --- did you follow the instructions at the beginning of this thread?  Look for the instructions for "Embedded DB (HSQLDB)"  making those changes should get you upgraded!

      MCapelle wrote:

       

      I was one of the unfortunate who tried to go to 3.6.0 right away from 3.5.2.  My install broke and I read the forums saying there would be a fix release.  I just tried the 3.6.0a rpm, but I am still broken .

       

      The error.log spews out "java.sql.Exception: Table not found in statement [SELECT count(*) FROM ofID]" errors and info.log has "Found old database version 16 for openfire.  Upgrading to version 20..." and "Server halted" errors.

       

      My suspicion for my broken installation is the old DB.  I am using the embedded DB btw.  I am no DBA, but from what I gather I can run the upgrade manually?   How would I do that?  I tried the embedded-db-viewer.sh script located in the openfire /bin directory, but that errors out with "Exception in thread "main" java.lang.NoClassDefFoundError: org/hsqldb/util/DatabaseManagerSwing".

       

      What are my options?  

  • rculpepper Bronze
    rculpepper
    51 posts since
    Jun 24, 2008
    Currently Being Moderated
    Sep 2, 2008 8:46 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    3.5.2 -> 3.6.0a upgrade: woes and heartache

     

    I've got 3.5.2 on Solaris... using the tar version, and embedded database

     

    I followed the upgrade guide exactly, but after starting openfire back up I can't get into the web interface. I simply get the following:

     

    HTTP ERROR: 503

    SERVICE_UNAVAILABLE

    RequestURI=/

     

    So I stopped openfire, modified the openfire.xml file to have <setup>false</setup> and the same thing occurs.

     

    stdoutt.log reads:

     

    Openfire 3.6.0 [Sep 2, 2008 9:25:13 AM]
    Admin console listening at:
      http://127.0.0.1:9090
      https://127.0.0.1:9091

     

    When it used to read:

     

    Openfire 3.5.2 [Sep 2, 2008 12:00:35 AM]
    Admin console listening at:
      http://my.hostname.org:9090
      https://my.hostname.org:9091
    Starting Client Control Plugin
    Starting Monitoring Plugin

     

    info.log, similarly, shows that the admin console is now listening on the loopback. Other than that there is nothing strange in the logs.

    • Daniel Henninger KeyContributor
      Daniel Henninger
      2,972 posts since
      Aug 10, 2005
      Currently Being Moderated
      Sep 2, 2008 10:33 AM (in response to rculpepper)
      Re: Openfire 3.6.0a has been released!

      Are you connecting to it from the local machine?  (ie that the loopback might work)  Try setting, in your openfire.xml, the following, removing the comment out lines and add the proper interface.  There's also a chance that having old monitoring and client control plugins is breaking it, so make sure you upgrade those.

          <!--
    <network>
        <interface></interface>
    </network>
    -->

      rculpepper wrote:

       

      3.5.2 -> 3.6.0a upgrade: woes and heartache

       

      I've got 3.5.2 on Solaris... using the tar version, and embedded database

       

      I followed the upgrade guide exactly, but after starting openfire back up I can't get into the web interface. I simply get the following:

       

      HTTP ERROR: 503

      SERVICE_UNAVAILABLE

      RequestURI=/

       

      So I stopped openfire, modified the openfire.xml file to have <setup>false</setup> and the same thing occurs.

       

      stdoutt.log reads:

       

      Openfire 3.6.0 [Sep 2, 2008 9:25:13 AM]
        Admin console listening at: 
      http://127.0.0.1:9090
      https://127.0.0.1:9091

       

      When it used to read:

       

      Openfire 3.5.2 [Sep 2, 2008 12:00:35 AM]
        Admin console listening at: 
      http://my.hostname.org:9090
      https://my.hostname.org:9091
      Starting Client Control Plugin
      Starting Monitoring Plugin

       

      info.log, similarly, shows that the admin console is now listening on the loopback. Other than that there is nothing strange in the logs.

      • rculpepper Bronze
        rculpepper
        51 posts since
        Jun 24, 2008
        Currently Being Moderated
        Sep 2, 2008 2:11 PM (in response to Daniel Henninger)
        Re: Openfire 3.6.0a has been released!

        D'oh! I had forgotten to upgrade the plugins before starting the server. That, however, was only half the battle and the battle doesn't seem to be complete.

         

         

        I noticed that on the first openfire start after untarring the upgrade, the stdoutt.log file still said 3.5.2 and all my plugins would fail (they require 3.6.0). I stopped openfire and started it again, and stdoutt.log then noted 3.6.0 and some database upgrades. Sweet!

         

        However, when it finished all that it tries to start up the plugins and never quite makes it all the way through - the last line of output in my stdoutt.log file is

         

        Starting Monitoring Plugin

         

        I'm not sure if it's getting stuck on the monitoring plugin or the whichever plugin it goes to next, but I cannot get openfire to start or get past this point.

         

        My total list of plugins is: broadcast, clientControl, gateway, monitoring, search, and userimportexport (userimportexport is probably not needed since it didn't do what I was hoping to trick it in to doing).

         

        Is it possible to remove the plugin .jar files, add them in after the upgrade and the console is running, and still have them pull old date (like old archives for the monitoring plugin...)???

         

        edit: it looks like the monitoring plugin is the one stalling...

        edit2: I removed the monitoring plugin, as well as some others, and the 503 error is still there. *sigh*

         

        edit3: VICTORY

         

        I tried one more time...

         

        From 3.5.2 I untared 3.6.0a on top. Restored the exodus.xml file and resources/security directory. Moved in the brand new versions of each plugin I have that had a brand new version.

         

        Started openfire and let it spit out "plugin whatever: requires server version 3.6.0" into stdoutt.log for about 15 minutes.

         

        Stopped and restarted openfire. Let it update the database (took just a few seconds) and sit for another few minutes.

         

        Then everything started working.

         

         

        All the old archives and rosters seem to be there... I will probably wait to hear more about this user-disconnect issue, but everything looks good so far.

  • Branin Bronze
    Branin
    2 posts since
    Sep 5, 2008
    Currently Being Moderated
    Sep 5, 2008 11:47 AM (in response to Daniel Henninger)
    Re: Openfire 3.6.0a has been released!

    I'm having a problem.  When 3.6.0 came out, I tried to upgrade, unsuccessfully.  I then reinstalled 3.5.2 and everything started working again.  I did not make a backup of anything before attempting the 3.6.0 upgrade.  Now, when I am trying to upgrade 3.5.2 to 3.6.0a, I am still having database problems.  I am using SQL Server 2005.  I've tried both the 17 upgrade that comes with 3.6.0a as well as the fixed files from Jerry Zeiszler.  Both file have the same error message (as shown below).  Any ideas?

     

    Thanks.

     

    Found old database version 16 for openfire. Upgrading to version 20...
    Database setup or configuration error: Please verify your database settings and check the logs/error.log file for detailed error messages.
    java.lang.IllegalArgumentException: java.sql.SQLException: Invalid object name 'ofID'.
        at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:710)
        at org.jivesoftware.openfire.XMPPServer.start(XMPPServer.java:427)
        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)
        at org.jivesoftware.openfire.starter.ServerStarter.main(ServerStarter.java:51)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
        at com.exe4j.runtime.WinLauncher.main(Unknown Source)
    Caused by: java.sql.SQLException: Invalid object name 'ofID'.
        at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
        at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
        at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)
        at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)
        at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
        at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatem ent.java:777)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reElferrotrc Ns.ttaarvtiieentM gohth dsAerecvceersso .PIlrepams.el nicheck the log filsv efkoor( emnoUknow nre nioSofurce)
    ar    t su.mnaetrfoienl.tc.

     

    DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.logicalcobwebs.proxool.ProxyStatement.invoke(ProxyStatement.java:100)
        at org.logicalcobwebs.proxool.ProxyStatement.intercept(ProxyStatement.java:57)
        at $java.sql.Wrapper$$EnhancerByProxool$$2774e49c.executeQuery(<generated>)
        at org.jivesoftware.openfire.XMPPServer.verifyDataSource(XMPPServer.java:700)
        ... 16 more
    Server halted

    • Branin Bronze
      Branin
      2 posts since
      Sep 5, 2008
      Currently Being Moderated
      Sep 5, 2008 11:50 AM (in response to Branin)
      Re: Openfire 3.6.0a has been released!

      By the way, SELECT Version from jiveVersion where name = 'openfire' is 16, if that helps at all.

    • Ville Walveranta Bronze
      Ville Walveranta
      9 posts since
      Jun 24, 2008
      Currently Being Moderated
      Sep 5, 2008 11:56 AM (in response to Branin)
      Re: Openfire 3.6.0a has been released!

      Sounds like the same problem I was having. See my message earlier in this thread. Basically there were two thing to do: 1) Prefix the sp_rename commands in the upgrade scripts with "exec", and 2) execute the upgrade scripts manually from the point where they're not correctly reflected in your database (look at scripts backwards and compare to the db to see if they've been implemented, if not, start executing them manually using Enteprise Manager or other SQL Server tool from that point on).

More Like This

  • Retrieving data ...

Bookmarked By (0)