Bug 1013941
| Summary: | Full HA configuration does not log into the console | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Configuration | Assignee: | Julian Coleman <jcoleman> |
| Status: | CLOSED UPSTREAM | QA Contact: | Matej Melko <mmelko> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | ldimaggi, michael.finn, ncross, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If you start the server with the -c standalone-full-ha.xml options, the start-up process hangs. This is because the CONSOLE logging handler has been omitted from the standalone-full-ha.xml configuration. To work around this, avoid using this start-up configuration.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:28:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jiri Pechanec
2013-10-01 05:44:17 UTC
So it seems that the issue relates to logging - according to server.log file the server is started. But I have observed another behaviour - sometimes there is nothing printed to the console at all. No HA for Beta. Not a Beta Blocker. However, we need to investigate this. The culprit is completely omitted CONSOLE logging handler in standalone-full-ha.xml config. Is it intentional? CONSOLE is still missing from the ER8 configuration. The configuration settings reflects the choices made for EAP. For example, looking at the EAP configuration, console logging is not configured in the standalone-full-ha case. For those looking for a workaround/fix, adding this into standalone-full-ha.xml under profile/logging subsystem seems to resolve (server starts up, log output to console):
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</console-handler>
Nevermind the above. Adding in the console logger does NOT fix it. Now that I am past my idiocy, does anyone have tips to get past this? Is the only answer to not use standalone-full-ha? We need it. Mike (In reply to Mike Finn from comment #9) > For those looking for a workaround/fix, adding this into > standalone-full-ha.xml under profile/logging subsystem seems to resolve > (server starts up, log output to console): > > <console-handler name="CONSOLE"> > <level name="INFO"/> > <formatter> > <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) > %s%E%n"/> > </formatter> > </console-handler> (In reply to Mike Finn from comment #10) > Nevermind the above. Adding in the console logger does NOT fix it. > > Now that I am past my idiocy, does anyone have tips to get past this? Is the > only answer to not use standalone-full-ha? We need it. > > Mike > > > > (In reply to Mike Finn from comment #9) > > For those looking for a workaround/fix, adding this into > > standalone-full-ha.xml under profile/logging subsystem seems to resolve > > (server starts up, log output to console): > > > > <console-handler name="CONSOLE"> > > <level name="INFO"/> > > <formatter> > > <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) > > %s%E%n"/> > > </formatter> > > </console-handler> Just to make sure, have you also included <root-logger> <level name="INFO"/> <handlers> <handler name="CONSOLE"/> <handler name="FILE"/> </handlers> </root-logger> ? This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |