This should be fixed by this commit upstream: https://github.com/jboss-logging/jboss-logmanager/commit/8599d3c93ab9acec4d42f32524edcb375916eb6b
QA NACK: * Upstream commit changes API for format method, no backward compatibility - with default encoding set to UTF-8 * Upstream commit contains new functionality - Add support for TCP and SSL connections on the Syslog handler.
Does the fact that this feature is tech preview make a difference on the backward compatibility issue? The bug described here renders the syslog handler useless for anyone that might ever include a multi-byte character in a log message, so it would be great to get this fixed. Perhaps as an alternative, we could at least fix the bug as a separate commit to the internal git repo rather than cherry picking an upstream commit.
TP decreases backward compatibility issue argument but still - fixing it isn't such a big problem ... New functionality should go to minor releases so EAP 6.2 should be appropriate target for support of TCP and SSL connections. For 6.1.1 I would like to see commit just for message length fix for multi-byte characters Referenced commit is done in master and not yet back-ported to 1.4 branch - https://github.com/jboss-logging/jboss-logmanager/commits/1.4 I think James could back-port just fix without new features.
Any progress on this ? PR without new functionality is fine from QE PoV.
Not yet. I need to find a good way to back port it without any added functionality. Not impossible, but I just need to take some time to have a good look at it.
https://github.com/jboss-logging/jboss-logmanager/commit/fb105198d6d3d75b703a18dfa251afba0aed9e5b is fix for this issue, granting qa ack
Verified on EAP 6.1.1 ER4