Bug 1140417

Summary: Upgrade jboss-logmanager from 1.5.2.Final-redhat-1 to 1.5.3.Final
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Perkins <jperkins>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact: Nikoleta Hlavickova <nziakova>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: brian.stansberry, jawilson, kkhan, myarboro, pkremens
Target Milestone: DR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:44:45 UTC Type: Component Upgrade
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1031448, 1143827    

Description James Perkins 2014-09-10 23:12:34 UTC
Updates the dependency to resolve some feature requests

Comment 1 Kabir Khan 2014-09-11 07:05:37 UTC
https://github.com/jbossas/jboss-eap/pull/1669

Comment 2 Kabir Khan 2014-09-15 08:02:11 UTC
The upgrade also changes the logmanager license from LGPL to Apache License 2.0:
https://github.com/jbossas/jboss-eap/pull/1671

Comment 3 Petr Kremensky 2014-09-19 07:00:21 UTC
Verified on EAP 6.4.0.DR1.1

Comment 4 James Perkins 2014-09-19 15:34:39 UTC
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

Comment 5 JBoss JIRA Server 2014-09-22 18:21:30 UTC
Brian Stansberry <brian.stansberry> updated the status of jira EAP6-150 to Resolved

Comment 6 JBoss JIRA Server 2015-04-28 15:03:42 UTC
John Doyle <jdoyle> updated the status of jira EAP6-220 to Closed

Comment 7 JBoss JIRA Server 2015-04-28 15:04:48 UTC
John Doyle <jdoyle> updated the status of jira EAP6-150 to Closed