Update the BOSH connector (HttpBindManager) to properly initialize and
restart after applying a configuration change.

OF-626: Incorporate review feedback

REST API plugin version 1.0.0

jmxweb plugin

Added xalan.jar (ver 2.7.1) to ANT build lib folder

Add -Dhalt.on.plugin.error=true to travis ant script

So that travis-CI will error out when a plugin fails to build.  The default
action is to silently ignore and continue building.

jmxweb plugin version 0.0.1

ofmeet plugin version 0.0.9

Fixed error when webcam is not available
Jitsi Videobridge server code refresh

- cleanup lib versions to remove obsolete MINA notes
- use C2S compression policy rather than S2S compression policy for BOSH
connector

OF-626: BOSH enhancements

OF-866: Prevent "session not found" errors

- Removed non-functional stream-based compression in favor of HTTP
transport compression (per spec
http://xmpp.org/extensions/xep-0206.html#create).
- Prevent runaway session initiation storms (via strophe) by returning a
400 HTTP error if a client attempts to deliver stanza(s) without a valid
sid (per spec http://xmpp.org/extensions/xep-0124.html#session-request).
- Use maxRequests to determine how many pending stanzas to preserve
while enabling delivery via multiple BOSH connections (per spec
http://xmpp.org/extensions/xep-0124.html#rids-broken)

Fixes a race condition by adding a newly authenticated session into the
core routing table before removing it from the list of
pre-authentication sessions.

3.10.0 Beta Release

Removed chopping by @ character in the URL, to get MUC Plugin running

OF-864: Cleanup routes to defunct cluster nodes

ofmeet plugin version 0.0.8

Fixed race condition causing focus xmpp connection to fail
Increased response timeout for focus
Improved error handling for read-only user providers like LDAP
Disable SIP gateway with a property
(org.jitsi.videobridge.ofmeet.sip.enabled)
Latest jitsi-videobridge server code

Ensure that all packets are handled by the backup routing mechanism in
the event that an exception occurs during primary packet processing.

When a peer server leaves the cluster, drop all routing references
corresponding to that node from the remaining members.

Bump JingleNodes version to pick up fix for OF-444

OF-857: Synchronize connection/session cleanup

- Use !equals() rather than != for JID comparison
- Ignore carbons for the offline delivery mechanism

When a connection is closed, any further packets to be delivered need to
be handled by the "backup" packet deliverer. The original implementation
simply tried to reuse the primary delivery/routing mechanism, which
resulted in a recursive call. This has been replaced with a packet
deliverer that will route undeliverable message packets into the offline
store.

The connection close listener initiates a presence broadcast to
advertise its "unavailable" status. The current connection must be
marked closed before this occurs, so the presence stanza will not be
delivered to the newly closed connection.

Note that the synchronized block alone does not accomplish this because
the presence broadcast is delivered via that same thread that is
currently closing the connection, thus it already possesses the sync
object lock.

Also, note that the SessionManager should exclude the originating JID
when sending presence broadcasts to the user's other available
session(s).

This patch is to prevent a stack overflow in certain exception cases
where a connection has been closed, but its corresponding session is
still present in the routing table.

OF-855/OF-857 improvements

Also decrease the size of the critical section the lock protects.

Related to OF-857.

and remove null checks.

Related to OF-855.

This patch fixes several NullPointerExceptions that were observed in an
cluster when running under high load and latency, including related
issues in the BOSH connector and hazelcast plugin. Some related logging
improvements are also included.

Some of the NPEs were generated during the startup phase before the
server was fully initialized. These have been corrected by checking
appropriate "ready state" indicators.

In general, sessions hosted in remote cluster nodes that cannot be
addressed due to timeouts during remote task execution should be
considered temporarily "unavailable" to the cluster member that
initiated the call.

Check the underlying connection for a given session before delivering a
packet; if the connection is missing, clean up session and resend packet

Use a lock to ensure the integrity of IoSession (MINA), especially when
using compression or TLS filters

OF-474 OpenFire still provides entry forms for already-registered room users