Ignite Realtime

aSmack was initiated by Rene Treffer for the buddycloud project. The last available download from him on the aSmack project page on googlecode is from December 2010. Prior to that, the development has been moved to github. But the development stalled there also. The last commit is from Aug 2010. This is when Flow has forked the aSmack and Smack repositories on github and started to merge the changes introduced by Smack 3.2.0. He has also added the changes from the upstream. aSmack codebase is now in sync with Smack upstream development.

• Compiled jars for Android (may be outdated)
• aSmack build environment
• The used smack fork (where aSmack uses the "master" branch)
• README (highly suggesting to read this)

There are some reports that vanilla Smack does also work on Android. This could be true (though hasn't been tested by this developer), but most probably some convenient features of XMPP won't work (e.g. DNS SRV lookups).

Openfire up to and including version 3.6.4 (and looks like 3.7.0 too) suffers from a memory leak in its PEP component. If your Openfire server is crashing with OutOfMemoryExceptions, you might be having this problem.

As a workaround, you can disable PEP, by adding the system property xmpp.pep.enabled and setting it to false.

More information can be found in this discussion: Openfire 3.6.4 memory leak with Empathy

Only a few users have access for filing bugs in the tracker. New users should:

1) Create a forums account (only e-mail is a requirement, you can skip all the other fields).

2) Login to a forum account

3) Press New in your toolbar and choose Discussion

4) Choose Dev forum of the appropriate product (e.g. Openfire Dev). Though it doesn't really matter where you report a bug as usually widget show all threads in one place.

Same goes for the general support issues (usually posting in the Support sections of the forum, e.g. Spark Support).

Bug tracker is available for read and comment here. Search for your issues in the bug tracker before reporting, please.

Spark is constantly in development by a team of community contributors. While waiting for the next stable release you can always try the latest build from SVN (for the Windows installers go to SPARK-INSTALL4J-xxx, then to Artifacts tab and install4j link) or even compile the very latest version yourself.

If you think you have found a security vulnerability in any of igniterealtime.org software, you may report this as well as exploit proof of concept to this address - security _at_ igniterealtime.org