The thread pool that performs processing of data received through the HTTP-based
connections of BOSH (as provided by Jetty) should not have a hardcoded upper bound.
Instead, the pool size should be configurable.

For other connection types, this is managed by properties named as such:
 - xmpp.client.processing.threads (client sockets)
 - xmpp.multiplex.processing.threads (connection managers)
 - xmpp.component.processing.threads (components)

BOSH does have a similar property: httpbind.client.processing.threads
It's value however is not used to configure the amount of worker threads. It is
used to configure the amount of (NIO) acceptors instead. In NIO, acceptor
threads handle network IO, and hand off processing to the worker threads.

There's little benefit in being able to configure the amount of acceptors, as
Jetty will default to a platform-specific default (based on the number of CPUs
that are available). There is greater benefit in being able to configure the
amount of worker threads (as that's more likely to affect throughput).

xml:lang in stream header should conform to a language tag.

toString() was called on the Locale here, resulting e.g. in "de_DE".
Instead it should be "de-DE".

Improving logging for S2S / dialback

Add explanation to setup about default admin password

Fix twice sending of messages on route.really-all-resources=true

The S2S (federation) code was not big on logging. This commit
introduces new logging, and structures the logged messages.
This commit does not introduce functional changes.

Add explanation to setup about default admin password
https://igniterealtime.org/issues/browse/OF-1016

If route.really-all-resources enabled it's not requere process message again via priority algorithm.
We already processed in 560 line. 
If we not stop (return) than session.process() call twice (first in line 560 and next in next other)

ofmeet plugin removal
Looks like I have to approve this myself. Here goes

Move openfire meetings from core repository

OF-1011: Trim each line of a PEM representation

Admin console: SSLv2Hello isn't a protocol, but an option.

OF-1006: Improve handling for pooled resources

OF-856: Cherry Picking of linuschien solution

Optimized configuration for XMPPPacketReader pool; improved exception
handling and reporting.

OF-1009: Ignore the exception indicating an error

This commit is a cosmetic change to the admin panel. If the JVM supports
SSLv2Hello, it is no longer presented as an encryption protocol, but rather
as an option.

Although not 'properly ended', the handshake failed in an expected manner.
This should be processed as a 'normal' handshake failure (not an exceptional
one).

OF-1010: Cannot re-init default SSLContext

OF-1008: Prevent loops of message failure

OF-793: Improve exception message

When the local user that is sent a message delivery failure report is
not online, drop the stanza. This prevents loops where the failure
to deliver the failure message triggers another failure message.

This commit makes handling of stanzas that could not be delivered uniform,
in regards to logging. Other than log levels and messages, this commit does
not make a functional change.

A default SSLContext object cannot be re-initialized. This causes LDAPS to fail.

When a peer sends a non-encrypted data where we expected encrypted,
a confusing exception is logged. This commit wraps that exception,
giving a clear explanation.

This typically occurs during a failed TLS handshake, where the peers
should be closing the connection without sending data, but does not
so (typically, the exceptions that are logged indicate that
</failure or </stream is received in plain text).

OF-1007: Supplement existing client-to-server whitelisting with blacklisting

This complements the existing whitelist with blacklist functionality for
client-to-server connections.

The code that verifies if an IP is on an (anonymous) whitelist is duplicated. That
code should be centralized, similar to its non-anonymous cousin in LocalClientSession.

Instead of a Set, the existing code uses a Map with empty string values 'for performance'.
I am not buying it. Perhaps true in some performance test long, long ago, but there won't
be any significant performance increase in doing this (it's just as likely to introduce
a performance penalty). In any case, when we're running into a performance bottleneck here,
we've got bigger fish to fry.

OF-1005: Removing reference to file that's no longer used.

OF-1004: Reduce complexity of connection configuration

OF-1005: Rolling back modules.xml

My original implementation had options to both include as well as exclude specific
encryption protocols and cipher suites. This proved to be to much - Configuration
becomes a nightmare and setups ended up with having no enabled suites at all. This
commit simplifies things: a connection listener now gets a list of protocols and
suites that are enabled - that's it. When no setting is provided, the JVM default
is used (which itself is tweakable through generic Java configuration revolving
around the file JRE_HOME/lib/security/java.security )