project_key: JBPAPP6 AFAIR related to the order of starting caches and channels. Lets track here if we remove the logging and/or which build to get the fix to.
Link: Added: This issue Cloned from AS7-4815
Link: Added: This issue is incorporated by JBPAPP-7577
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
We will probably just move the logging to debug; making minor.
Release Notes Docs Status: Added: Not Yet Documented
Labels: Added: usability
The fix version is 6.0.1, the patch is ready but not picked up in 6.0.0.
Link: Added: This issue is a dependency of JBPAPP-9290
Link: Removed: This issue is incorporated by JBPAPP-7577
Release Notes Text: Added: Verified, closing.
reopening for release note updates
Writer: Added: sgilda
Writer: Removed: sgilda Added: tomwells
Release Notes Docs Status: Removed: Not Yet Documented Added: Needs More Info
Could someone please provide the Cause, Consequence, Fix, and Result of this JIRA for the release notes?
Release Notes Docs Status: Removed: Needs More Info Writer: Removed: tomwells Release Notes Text: Removed: Verified, closing. Docs QE Status: Removed: NEW
I'm still seeing this on {{INFO}} level with 6.0.1.ER4.1, see for example https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x-failover-http-granular-shutdown-repl-sync/14/console-perf20/ Neither this nor upstream issue (AS7-4815) links to the fix, so I have no clue how this was resolved. Edit: Added 6.0.1.ER4 to _Affects Version/s_, because we don't have 6.0.1.ER4.1 in JIRA (oh those point ER releases...).
Haven't seen this anywhere with ER1.