By closing a session when the new MINA inputClosed() handler is triggered, we run
the risk of sending data to the peer. As that peer is known to be dead, this is
pointless (and potentially dangerous - deadlocks have been observed that are likely
related to this scenario).

To prevent sending data during session closure, the close() method has been
overloaded with an argument that indicates if the peer is known to be dead. When
set, its implementation will not attempt to send data.

The close listeners should not be called from within a synchronized block.

When a connection is closed, several events can be involved (and can be triggered).
Some of these events will attempt to close the connection (if it hadn't been already).
This, at best, least to multiple invocations of close-listeners. At worst, a loop of
close-calls is created.

This commit replaces the two-way boolean that guards closure (isClosed) with a
three-way guard. Now, a distinction is made between between a connection that is
closed, and one that is closing.

Additionally, some null pointer guards have been added, as I've seen those pop up in
my local logs during development.

MINA 2.0.8 introduces support for half-duplex close of TCP channels (see DIRMINA-785).
As part of this change, IoHandlers got a new method. The default behavior of the
IoHandlerAdapter closes the MINA session when this handler is triggered. However,
without an Openfire-specific extension (in ConnectionHandler), this fails to close
Openfire-maintained resources. As a result, CPUs could start to spin in NIO code,
resulting in 100% CPU cycles.

To fix this issue, ConnectionHandler now overrides the default functionality and
triggers a normal closure of the session (both in Openfire as well as MINA context).

Additionally, to prevent the CPU spin, MINA sessions need to be closed synchronously
(as opposed to the async closure Openfire had up until now). I cannot quite explain
the need for this change, other than a suspision of race conditions in the async
setup.

ofmeet plugin version 0.1.8

Fixed issue with room locking not working
Added conference UI customization to Meetings Settings Admin web page
Updated Jitsi Videobridge

ofmeet plugin version 0.1.7

Logs openfire meeting audit events with Openfire security auditor
Logs meeting SIP calls via SIP plugin
Added support for audio conferencing meetings (no video)
Updated Jitsi Videobridge

OF-862 Add support for XEP-313: Message Archive Management

ofmeet plugin version 0.1.6

Added support for media relaying using the JingleNodes plugin

jinglenodes plugin 0.1.3
Replaced jingle nodes relay library jar file with latest source code
Added dependencies smack.jar and smackx.jar

Updated jingleNodes plugin to work with Public/Private IP and Configurable Ports/Servers:

ofmeet plugin version 0.1.5

Implemented Meeting Planner and automatic invites. Requires bookmarks from the clientcontrol plugin
Fixed error modified setLocalDescription failed with desktop share
Prevents sending invalid presence packets, before MUC jid is defined
Added support for web+meet: protocol handling
Added support for iNum and eNum telephone numbers
Updated Jitsi Videobridge

Add openjdk headless dependency to avoid installing X libraries

OF-909: Include ack in BOSH response body element

Userservice plugin update with JSON support

Fixes the alternate (synchronous) write to the HTTP response output
stream.

Per spec, the ack attribute in the response <body/> allows a BOSH client
to verify that sent stanzas with the corresponding rid(s) have been
successfully received by the server.

Conflicts:
	build/build.xml
	src/java/org/jivesoftware/openfire/XMPPServer.java

* Made ports configurable via the admin interface
* Made STUN test server default to google and configurable via the admin interface (previous hardcoded server was dead)
* Made Local/Public IP logic work for a server behind a firewall (previous code was mixing local and remote IP concepts and would only work outside of a firewall)
* Added some logging to the verify code to make it easier to find out why verification failed

Openfire 3.10.0 GA Release!

Mutual authentication support depends on certificates being available in the client
truststore. Openfire does not ship with any by default, and does not provide any tools
to manage certificates in any of the truststores. This commit adds basic support, which
allows a user to add, remove and review certificates in any of the keystores that are
available in Openfire.