Skip navigation

Ignite Realtime Blog

14 Posts tagged with the release tag
Guus der Kinderen
1

Good things come to those who wait!

 

The Ignite Realtime Community is pleased to announce the beta for the next release of Openfire. This release contains a number of important  fixes and improvements to stability and XMPP protocol compliance. You can find a full list of fixed issues here. This beta is also the first version of Openfire to be released by the Ignite Realtime community under the Apache License v2.0.

 

You can download the 3.7.0 beta release here. Please provide us your feedback on the Ignite Realtime support forums. It would be helpful if you would tag your comments, discussions and questions with a tag that reads "openfire370beta"

 

As always, but particularly since this is a beta release, make sure to backup any existing version of Openfire and the persistent storage that it uses, before upgrading!

 

Some important security related notes to this release:

  • Openfire no longer ignores the system property to disallow password changes via XMPP. With previous releases, it was not possible to prevent users from changing their password via their XMPP connection. (CVE-2009-1596)
  • Fixed a XSS attack on the admin console login form.

 

Protocol compliance improvements:

  • Publish Subscribe (PubSub)
  • BOSH (http-bind) xml namespace compliance fix.

 

Some highlights of this beta release:

  • Improves how Openfire handles "idle" connections. Some of you may have  the system property xmpp.client.idle set to -1 to work around  previously broken behaviour. You may now let it default to 6 minutes or  set it to your preference.
  • Improved Openfire's caching to be less prone to memory exhaustion by correctly calculating cache size usage.
  • Fixed a bug where admin console login into a newly installed Openfire server would fail until restarted.
  • Fixed a bug with shared rosters within a LDAP environment.
  • Openfire now ships with the latest JRE (1.6.0u21).
  • A memory leak with the Personal Eventing Protocol (PEP) was fixed.
  • Openfire's custom log interface has been replaced with SLF4J and a Log4J backend.
  • Fix issues with self signed SSL certificates.
  • A number of improvements and fixes were made to the Multi-User Chat (MUC) configuration pages on the admin console
  • There were also some improvements made to the plugins.
  • There are also French, Russian, and Lithuanian langauge translation fixes for Openfire and some of the plugins.
2620 Views 1 Comments Permalink Tags: planetjabber, xmpp, openfire, update, release, beta, openfire370beta
Mark Walters
1

 

We are pleased to announce the release of XIFF 3.0.0!

This major release includes many bug fixes, improvements, and features over the previous beta release, including Digest-MD5 support and removal of all Flex dependencies for pure AS3 project support. This release also includes a new class namespace (igniterealtime instead of jivesoftware).

You can view the full change log here.

 

Download XIFF from here.

 

Nightly builds are also maintained for XIFF now. You can access those here.

 

Enjoy!

832 Views 1 Comments Permalink Tags: planetjabber, xiff, update, release
Guus der Kinderen
1

We  have just released Tinder  1.2.2, which is a maintenance release. It  fixes a number of bugs, features improved performance and has a number  of new features.

 

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

684 Views 1 Comments Permalink Tags: planetjabber, update, release, tinder
Guus der Kinderen
0

We have just released version 1.2.1 of Tinder. This version is a bugfix release, that improvement the AbstractComponent implementation that was added in version 1.2.0.

12405 Views 0 Comments Permalink Tags: planetjabber, update, release, tinder
Guus der Kinderen
8

I'm happy to announce the release of version 1.2.0 of Tinder. This new version brings interesting new features, a number of bugs fixes and general performance improvement.

 

Recently, I published a document describing a problem that I dubbed Openfires Achilles' heel. Tinder 1.2 introduces the AbstractComponent implementation, which will allow you to circumvent this problem easily. Additionally, AbstractComponent removes the need for the repetitive work that traditionally goes with implementing a full featured, spec-compliant component. Have a look at the Component Developer Guide for a detailed description.

 

Tinder 1.2 no longer depends on Openfire-specific logging. Instead, Simple Logging Facade is used, which will allow you to integrate with your existing logging framework easily. Finally, caching strategy and implementation have been modified to give you better performance.

 

A detailed list of changes can be found in the Tinder Release Notes. Did I mention that starting with 1.2 we're releasing the code under the Apache 2.0 license?

4784 Views 8 Comments Permalink Tags: planetjabber, update, release, tinder
Guus der Kinderen
2
We've just released the second version of Tinder, the new XMPP library that was introduced two months ago. This release focusses on Java concurrency (threading) issues and fixes a number of important bugs from 1.0.0. More detailed information is available in the release notes.
9832 Views 2 Comments Permalink Tags: planetjabber, update, release, tinder
Guus der Kinderen
32

Java-monitor.com has released a new, free Openfire plugin that allows you to monitor your Openfire instance remotely. The plugin will notify you if your server goes off-line. It also allows you to keep a close eye on a number of important health indicators, such as the usage pattern of the Openfire worker threads, JVM memory usage and garbage collection statistics, JVM thread and Openfire's database connection pool usage.

 

Unlike most monitoring tools, you don't have to set up a monitoring server yourself for this to work. Java-monitor.com provides the infrastructure to do the monitoring for you. The probe that's integrated in the Openfire plugin sends statistics to java-monitor.com. Everything else is handled there. You can view the data from their website, as shown below.

Java-Monitor architecture

To get started, register an account at http://java-monitor.com/install.html. After you've registered, you'll be able to download a personalized Java-Monitor probe package, which includes an Openfire plugin. Add this plugin to your Openfire installation, and you're done! The plugin will automatically start collecting data. Java-monitor allows you to monitor Openfire from anywhere - all you need is a javascript enabled browser.

14850 Views 32 Comments Permalink Tags: openfire, plugin, release, monitoring
Guus der Kinderen
6

We've just released a new project, named Tinder. Tinder is a new Java based XMPP library, providing an implementation for XMPP stanzas and components.

 

Tinders origins lie in code that's shared between Jive Software's Openfire and Whack implementations. The implementation that's provided in Tinder hasn't been written again from scratch. Instead, code has been moved from the original projects into Tinder, preserving al of the existing features and functionality. Most of the code that's now in Tinder is based on the org.xmpp package implementation that previously existed in Openfire and Whack. This is the code that defines classes such as Packet, JID, IQ, Component and their extensions. Additionally, some multi-purpose code (such as the DataForm and Result Set Management implementations have been moved to Tinder as well.

 

Why a new project?

 

Parts of the code of Openfire are useful in other contexts than that of an XMPP server implementation. Developers might, for instance, want to use the XMPP stanza implementation within other projects. Having to include Openfire as a dependency of such a project is quite a bit of overkill. In such an example, it would be useful to have a small project that you can include, that offers you a lightweight XMPP object implementation, without the rest of the features that Openfire offers. Enter Tinder. Tinder will allow developers to re-use parts of Openfire, without having to include Openfire itself.

 

There's other benefits to Tinder though:

 

Tinder will replace some most of the duplicate code that's currently shared in Openfire, Whack and ConnectionManager projects. Removing duplicate code will make it easier to maintain and develop these projects. By delegating the implementation and maintenance of the low-level XMPP implementation, Openfire, Whack and other developers will be able to focus on the development that adds value to their project.

 

On the flip-side of that medal, you can argue that the 'core' code that will make up Tinder deserves a bit of dedicated development attention (unit tests, bug-tracking, stuff like that). This would benefit any attempt to really fine-tune the code, for example for high-performance tuning. Currently, the code is a bit put in the shadows of the other projects (of which they are part of).

 

So, will this replace Smack (the library that provides the base of Spark)?

 

No, definitely not. Smack offers a full-fledged XMPP client implementation, while Tinder only defines some XMPP building blocks. Tinder provides some basic objects on which a client library such as Smack could be build. However, Smack does not share the same code base as Openfire and Whack do. It's therefor unlikely that Tinder and Smack will be merged in the foreseeable future - there's simply to much difference.

 

What's next?

 

We've wrapped up a initial roadmap, in which we capture the first steps of the development of Tinder. As always, you're invited to contribute. We're looking forward to hear your suggestions, thoughts and ideas. If you're interested, you can find more information on the new Tinder-related community space and project page that have been opened on IgniteRealtime.org.

8393 Views 6 Comments Permalink Tags: planetjabber, xmpp, release, announcement, tinder, project
Daniel Henninger
14

We are very pleased to announce the release of Openfire 3.6.0!  It has been a long time coming and may well include the highest number of bug fixes and improvements we've ever had in a single release.  Don't quote me on that, but it's certainly the largest number I recall seeing.  =)  While the bulk of them are bug fixes, there are a couple of big improvements I would like to highlight!

 

Clearspace Integration Improvements

We've improved upon the integration between Openfire and Clearspace quite a bit.  Most are bug fixes and performance improvements, but also some new backend features that further solidify the bond if it is set up.  Openfire now includes a Clearspace tab when integration is enabled so help make sure the link is performing properly.  On top of that, there are a lot of features in place in preparation for the addition of real time chat support in Clearspace.  More information will come on that at a later date.  We've also renamed the tables Openfire uses to make it easier to install it alongside other products in the same database, if you so choose.  The automatic upgrade procedures will take care of all of the hard work for you, so you shouldn't need to give it a second though.

 

LDAP Support Improvements

Openfire's LDAP support had some holes in it here and there that should be filled now.  Altbasedn, for example, was not used everywhere.  There is now support for alias following (or rather, turning it off), paged results (to make sure to get all of the available results instead of a subset), and a number of bug fixes for existing functionality.  Internally, a lot of the code has been cleaned up.  I still have a couple of things up my sleeve here and there for a future release, but I'm quite pleased with how this is looking now.

 

Multiple Conference Services

Every wished you could have more than one conference service set up with different rules?  Maybe you wanted one for public access with no room creation rules and restrictions, but also wanted an internal "protected" service that abided by strict rules.  Maybe you just wanted to set up some sort of specialized set.  Maybe you never wanted -any- conference services and just wanted to delete them.  Whatever the reason you might have, you can now set up as many or as little as you want.  In some cases, plugins may even be able to take advantage of a specialized service setup.

 

BOSH (HTTP Binding) Improvements

With many thanks to our Google Summer of Code student, Safa Sofuoglu, we now have updated BOSH 1.6 support, and a ton of misc bug fixes and improvements.  Improvements in this area were also performed on the connection managers!  I encourage you all to read about it in his report:

GSoC 2008 Report: Openfire and SparkWeb

 

More Configuration in Database

The openfire.xml config file was getting bloated and a lot of the configuration in it could easily have been moved into the database.  As a result, we've moved just about everything that doesn't fall into a category of:

  • how to connect to the database itself
  • config info specific to host itself

 

Why you might ask?  In a clustered environment, it makes it so you can set Openfire up once and now have to reconfigure the providers and such for each cluster member individually.  It also paves the way for support for things like, admins stored in the database, which means you can update the admin list on the fly, instead of having to edit openfire.xml and then restart the server.

 

Plugin Updates

It's important to update the following plugins to account for changes in the 3.6.0 API:

  • User Search
  • IM Gateway
  • Fastpath
  • Monitoring

 

Where Do I Get It?

 

You can download Openfire 3.6.0 here.

You can see the entire changelog here.

You can view the documentation for 3.6.0 here.

Plugins can be downloaded from the admin console or here.

14064 Views 14 Comments Permalink Tags: openfire, release
Daniel Henninger
45

We are pleased to announce the release of Openfire 3.5.1, now with even more openness!  This release represents the first stage of the Enterprise plugin split into open source plugins.  We're very excited to be able to provide these to everyone for free, and seeing what the community does with them, both in terms of contributed code and use case scenarios.  So lets talk about some specifics.

 

New Plugins!

 

  • Monitoring: Adds support for server statistics and chat archiving and reports.

  • Fastpath: Support for managed queued chat requests, such as a support team might use.

 

These are the first two pieces of the open sourced Enterprise plugin.  Client management is coming very soon, as is clustering.  SparkWeb will also be released tomorrow as a separate product.  So you might be wondering, hey, why is there an Openfire Enterprise 3.5.1?  Well, due to the lack of all of the plugins being available right now, we've provide 3.5.1 for existing enterprise customers to make use of.  It includes some important clustering fixes though!  (as will the clustering plugin when it is release)

 

Important, Seriously, Pay Attention, Read This

 

 

If you install the Monitoring and/or Fastpath plugin, make absolute sure that you read the readme first!  There are included instructions for how to migrate your database from the Enterprise plugin to the new plugin database tables.  If you have ever run the Enterprise plugin or the old Fastpath plugin before it was integrated with Enterprise, make sure you don't forget this or you will be unhappy!

 

 

Big Connection Manager Improvements

 

The connection managers have been updated to bring HTTP binding up to date and a couple of library upgrades that include a number of improvements.  It is important to note though that the conf/manager.xml file has been updated and you will need to update yours as well.  The new http binding section that you will need to add is described here.

 

Ok Fine, Where Do I Get It?

 

You can download Openfire 3.5.1 here.

You can see the entire changelog here.

You can view the documentation for 3.5.1 here.

Plugins can be downloaded from the admin console or here.

8781 Views 45 Comments Permalink Tags: planetjabber, openfire, release
David Smith
20

SparkWeb Open Source

Posted by David Smith Apr 22, 2008

Earlier today I exported our svn repository for SparkWeb and committed the intial import to the new open source repository! Instructions for getting and building the source are available. Getting and Building SparkWeb. A chat room for discussion of SparkWeb development can be found at sparkweb@conference.igniterealtime.org. I'm looking forward to seeing what the community can do!

9861 Views 20 Comments Permalink Tags: planetjabber, xmpp, sparkweb, open_source, release
Daniel Henninger
0

As you may have already seen, Openfire 3.5.0 was released today alongside it's good friend Clearspace 2.0!  We are excited to put out this release as it strolls alongside a number of new announcements, new features, and is sporting a brand new outfit in the form of a new look and feel for the admin interface.

 

Now, in light of the announcements regarding the Enterprise plugin becoming open source, you may be wondering why you can see an updated Enterprise plugin available.  We are providing this plugin for our existing enterprise customers until the separate split-up plugins are released.  Those of you waiting for the open source releases, please stay tuned!

 

For our Clearspace customers, this new version of Openfire integrates at a much more intense level than before.  Instead of simply providing presence to Clearspace, and requiring you to point both Clearspace and Openfire at something like LDAP to have the same login setup, you can now have Openfire speak directly to Clearspace.  It will pull it's users and groups, as well as pass authentication through Clearspace.  Setup is a breeze, as you have one screen of setup in Clearspace and one screen of setup in Openfire and you are done.  And we're not stopping there.  Future releases will include even more integrations between the two!

 

Is Clearspace integration the only new thing in Openfire 3.5.0?  Of course not!  We've now got the ability to disable accounts, security audit logs for admin events, easy to take advantage of invisibility, and did I mention the pretty new admin interface?  We went over a lot of these new features in a previous blog post, so I won't bore you with a complete rehash of all of them. 

 

One word of warning, due to the nature of CSS not wanting to easily refresh itself, you may need to shift-reload in your browser for the new admin console to look correct.  And don't forget to update your plugins after upgrading to 3.5.0!  Some of them are affected by API changes!  (specifically: User Search, IM Gateway, MOTD, and SIP)

 

This has been a very exciting day for us here at Jive and we hope exciting for you as well!

 

You can download Openfire 3.5.0 here.

You can see the entire changelog here.

You can view the documentation for 3.5.0 here.

Plugins can be downloaded from the admin console or here.

4744 Views 0 Comments Permalink Tags: planetjabber, openfire, release
David Smith
9

XIFF 3 Beta

Posted by David Smith Apr 2, 2008

I'm happy to announce that we've just released an initial beta of XIFF 3.0, our open source ActionScript library for building XMPP clients. Continuing along the path set by Sean and the previous developers of XIFF, we've moved to embrace ActionScript 3 and Flex, while adding significant functionality improvements at the same time. Highlights include BOSH support, VCard support, and redesigned APIs. Feedback is strongly requested; It has been quite a while since a XIFF release, and a lot of things have changed, so I will be interested to see how the community feels about the direction we've taken things.

 

Some parts of this new release are still in a transitional stage. For example, SASL support is only available for BOSH connections at the moment. As more code is generalized between the BOSH and Socket connections, this limitation will go away.

6192 Views 9 Comments Permalink Tags: planetjabber, xmpp, flex, sparkweb, actionscript, xiff, webapps, release, beta
Daniel Henninger
20

We are pleased to announce the availability of Openfire 3.5.0 RC1 off of the beta downloads page, along with Openfire Enterprise 3.5.0 RC1 off of the beta plugins page.  The official release is slated for late March or early April, depending on when the official release date of Clearspace 2.0 is.  There are a number of new features and bug fixes in this release.  A couple of the highlights are as follows:

 

New Security Features

 

3.5.0 includes two new improvements to the overall security of Openfire.  One is a new lock out manager, which allows administrators to lock out (disable) accounts, thereby preventing them from logging in.  This can be for a period of time, or "forever".  Another new security feature is a new auditor for actions performed in the admin console.  This will allow you to keep track of what has changed in your server's configuration, and who performed the change.

 

For more information, see: Big Brother In 3.5.0

 

Invisibility

 

3.5.0 includes the ability to connect without sending an available presence.  This provides an easy means for being "invisible" to other XMPP users, and visible specifically to those you intend on speaking to.  This support needs to be built into clients or programs that you might be using to be of direct use, but the capabilities are now available!

 

For more information, see: Playing Casper in 3.5.0

 

Clearspace Integration Improvements

 

Clearspace 2.0 and Openfire 3.5.0 can now work together harmoniously to share users, groups, vcards, presence, and various other functionality.  Not only that, but Clearspace and Openfire will configure their integration in a semi-automatic mode, where you provide a minimal configuration of Openfire and Clearspace and they take care of the rest!  You will see a new option during initial setup where you can choose Clearspace integration that will lead you through the steps.  Please note that Clearspace 2.0 or higher is required for this integration to function properly!

 

For more information, see: Clearspace 2.0 Public Beta

 

Performance Improvements

 

A number of improvements have been made to the overall performance of Openfire in 3.5.0.  An important index was added to one of the database tables that improves roster loading speed by a large degree. The networking framework used for external component connections has also been replaced with MINA, drastically improving the performance of external component connections.

 

Fixed Double-Byte Character Problems

 

3.5.0 includes fixes for double-byte characters not being handled correctly.  This should solve a number of problems with messages that include chinese characters, or other double-byte character encodings.

 

SparkWeb Enhancements

 

SparkWeb 3.5.0 includes a number of reliability improvements, especially with http binding, and also improved support for MUC functionality, such as moderation controls (kick/ban/etc).

 

New Admin Console Look and Feel

 

3.5.0 sports a brand new look and feel for it's administrative console.  Those who have used Clearspace before will be familiar with it, as it's mirrored in concept and general look after Clearspace's administrative console.  The new menu layout is much less cluttered than before, and should involve a lot less scrolling down the page to find what you want.  Warning: Due to changes in the CSS files, and browsers wanting to hold onto CSS files for dear life in their caches, you will likely need to hit shift-reload on your browser when visiting the new admin console.

 

And more!

 

You can view the full changelog here.

You can view the updated documentation (javadocs et al) here.

Plugin updates required for Openfire 3.5.0 are available on the betaplugins page.

The specific plugins that need to be updated are:

  • IM Gateway

  • User Search

  • Enterprise

  • MOTD

  • SIP

 

Happy testing and please let us know of any issues you run into by posting in the  Openfire support forum!

 

Thanks!

-The Openfire Team

7086 Views 20 Comments Permalink Tags: planetjabber, openfire, release


Popular Blog Posts