Patched up note on dangling database connections

Always close jdbc Statement/ResultSet in finally

Add note for SizeAndTimeBasedFNATP#createArchiveRemover

Add note for LOGBACK-466

Documentation: Fix syntax issue with GEventEvaluator example in filters documentation.

for the cases where the automatic detection goes over this limit. UDP
messages are limited to 65536 bytes, but that includes the UDP headers
themselves, so the value of 65000 is used instead (this is the value
that used to be statically used)

LOGBACK-802 Documentation: Replace usage of Javascript's String.trim() with JQuery's trim() to allow support for older web browsers

Add note for LOGBACK-927

LOGBACK-927 Update the logback-access Common Log Format to use MMM rather than MM. Update the documentation to reflect this and to remove errors regarding the %date/%t behavior with the PatternLayout

Add notes for LOGBACK-768 and LOGBACK-928

LOGBACK-768 Documentation: Fix mistake in the definition of the combined log format (missing brackets)

Add note for pull request #136 (LOGBACK-885)

Add note for pull request #156

Add notes for LOGBACK-926 and LOGBACK-904

LOGBACK-926 Update SyslogAppender to set the maxMessageSize to be the system default UDP size to prevent logs from being dropped if they are too large.

"<includes>" should've been "<include>"

We were null-checking the current status manager instead of the one
passed in.

This prevents a NullPointerException from being thrown, and allows the
socketNodeClosing method to be called for the SocketNode.

The constructor creates an ObjectInputStream, and this blocks until the stream
header is received from the client.

If the client doesn't send a stream header, construction of the SocketNode will
hang, preventing SimpleSocketServer from accepting new clients.

This change moves the construction of the ObjectInputStream into
SocketNode.run. As SimpleSocketServer runs this method in a new thread, a rogue
client won't prevent subsequent ones being able to connect.

Fixed issue "Failed to instantiate LoggerContext" because of " java.lang.SecurityException: AccessController.checkPermission is unsupported." (LOGBACK-760) using the solution provided in the comment by ori.

amendment for LOGBACK-644: suppress errors for nonexistent resource includes

* changed direct access of timestamp field to use getTimstamp() instead inside of calculateElapsedTime.