Bug 961683 - BPMS dashbuilder uses non-standard log file location
Summary: BPMS dashbuilder uses non-standard log file location
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER2
: 6.0.0
Assignee: David Gutierrez
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-10 09:26 UTC by Marek Winkler
Modified: 2014-08-06 20:09 UTC (History)
3 users (show)

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.
Clone Of:
Environment:
Last Closed: 2014-08-06 20:09:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Marek Winkler 2013-05-10 09:26:05 UTC 
Description of problem:

BPMS dashbuilder application uses non-standard log file location /tmp/dashboard-builder-jboss.log. This might cause issues when backing up application logs in production use; more importantly, the default log location should be intuitive for the user.

Version-Release number of selected component (if applicable):

BPMS 6.0.0.DR4

How reproducible:

Deploy dashbuilder.war application and look for its log file.
 
Actual results:

Log file is located at /tmp/dashboard-builder-jboss.log.

Expected results:

Log file should be located under EAP domain or profile directory (e.g. standalone/log/).
Comment 1 Lukáš Petrovický 2013-05-10 09:28:16 UTC 
Even more so, the app should log to the same file as any other app - server.log. Is it even using jboss-logging?
Comment 2 David Gutierrez 2013-07-16 17:53:25 UTC 
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
Comment 3 Jan Hrcek 2013-09-04 07:35:36 UTC 
Verified with BPMS 6.0.0.ER2
Note You need to log in before you can comment on or make changes to this bug.