Bug 961683
Summary: | BPMS dashbuilder uses non-standard log file location | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marek Winkler <mwinkler> |
Component: | BAM | Assignee: | David Gutierrez <dgutierr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan Hrcek <jhrcek> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | lpetrovi, mwinkler, rzhang |
Target Milestone: | ER2 | ||
Target Release: | 6.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Approach for logging based on JCL/Log4J.
Consequence: App did use its own log file based on Log4J.
Fix: Migrate core logging service core to SLF4J
Result: Now, the app uses an standarized approach for logging. JBoss logging service will be taken by SLF4J.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-06 20:09:44 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
Marek Winkler
2013-05-10 09:26:05 UTC
Even more so, the app should log to the same file as any other app - server.log. Is it even using jboss-logging? Log4J has been completely removed and SLF4J has been taken instead. Logging service is now provided by JBoss. Github commits: https://github.com/droolsjbpm/dashboard-builder/commit/b351986016954b5c1366ad9b5d6d9a1c8e074d74 https://github.com/droolsjbpm/jbpm-dashboard/commit/a02b2e8649e5cfd5ee64a03a342716cef8f340c8 Verified with BPMS 6.0.0.ER2 |