We are pleased to announce the release of Openfire 3.4.5! This release includes a brand new database connection pool implementation, which handles database outages in a much smoother manner. It also includes some admin interface robustness improvements and a small memory leak fix. You can view the full change log here.
The SparkWeb client included in the Enterprise edition has been updated too. A wealth of bug fixes and improvements have been made, including support for configuration of MUC rooms, MUC room search support, and autologin improvements. You can use the SparkWeb client from here.
i just updated from 3.4.4 and I have a small problem: The version shown in the admin panel is still 3.4.4. I never had that problem before and I just followed the steps in the upgrade guide in the documentation. Is this a problem with my installation or is there’s something wrong in the download package?
What do you see in the info.log? If you see there 3.4.5 but 3.4.4 in the admin console then your browser is caching an old page. To force a refresh press Shift-F5. Otherwise, for some reason the lib/openfire.jar file was not replaced with the new one.
Do you have enterprise? If so have you also upgraded the enterprise plugin to 3.4.5?
I can’t imagine why you’d be seeing 3.4.4 though. =/ Unless the old one is still running somewhere? Make sure there’s no lingering java processes from the old version. (or restart the server entirely if that’s easier)
No, I’m running the GPL version. I already restarted the server but the problem still exists. I deleted the entire folder of the former version it’s really weired.
actually, one could do a select 1 from dual as well.
DUAL is a table which is created by oracle along with the data dictionary. It consists of exactly one column whose name is dummy and one record. The value of that record is X. The owner of dual is SYS but dual can be accessed by every user. As dual contains exactly one row (unless someone fiddled with it), it is guaranteed to return exactly one row in select statements. Therefor, dual is the prefered table to select a pseudo column (such as sysdate
I don’t suppose I could ask if we have folk using and whether you had success with 3.4.5:
SQL Server (Microsoft’s server)
Sybase
Postgres
IBM’s DB2
Just for my own comfort, I’d like to hear someone give a thumbs up to each of these. From the research I just did, the rest -should- be fine. (IE, Oracle is the only one that doesn’t like a SELECT without a FROM)