https://github.com/jbossas/jboss-eap/pull/1669

The upgrade also changes the logmanager license from LGPL to Apache License 2.0:
https://github.com/jbossas/jboss-eap/pull/1671

Verified on EAP 6.4.0.DR1.1

A documentation notes: 

The SyslogHandler (syslog-handler) has had a behavioral change. Previously if a syslog connection was lost you'd have to restart the server in order to reconnect the handler. The handler will now indefinitely attempt to reconnect on a lost connection.

The SyslogHandler (syslog-handler) also used to escape values less than ASCII dec 32. This no longer happens and values are sent as is over the connection. The main thing to note here is if a SyslogHandler was used as a custom-handler and the protocol is TCP this could truncate messages if they contain a \n (0x0a). This can be changed if the useCountingFraming is set to true and useDelimiter is set to false. It's worth noting too this does not affect the syslog-handler resource as it uses a UDP connection.

There's also a new format parameter for the PatternFormatter. The new parameters are %h and %H. %h resolves to the hostname while %H resovles to the qualified hostname.

There were also some bug fixes and more information can be found here https://issues.jboss.org/secure/ConfigureReport.jspa?versions=12323924&sections=all&style=none&selectedProjectId=12311070&reportKey=org.jboss.labs.jira.plugin.release-notes-report-plugin%3Areleasenotes&Next=Next

Brian Stansberry <brian.stansberry> updated the status of jira EAP6-150 to Resolved

John Doyle <jdoyle> updated the status of jira EAP6-220 to Closed

John Doyle <jdoyle> updated the status of jira EAP6-150 to Closed