Bug 779899 (SOA-2259) - Failed to initialize BIRT service
Summary: Failed to initialize BIRT service
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2259
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: riftsaw
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.2.0 GA,5.2.0.ER4
Assignee: Jeff Yu
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-06 13:19 UTC by Zuzana Zoubkova
Modified: 2013-07-02 01:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-07 17:56:30 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2259 0 None None None Never

Description Zuzana Zoubkova 2010-09-06 13:19:06 UTC 
project_key: SOA

This warning appears during the startup of the soa platform:

2010-09-06 11:48:14,053 WARN  [org.jboss.bpm.report.ReportFacade] (main) Failed to initialize BIRT service. Please check the DEBUG log for further details.

It may be related to the issue RIFTSAW-111
Comment 1 Gary Brown 2010-09-07 16:03:19 UTC 
Hi Heiko - is it possible to just change this to an info message stating "BIRT service has not been activated"?

I know for RiftSaw2.2 we are likely to have the BIRT service included, for the BAM functionality, but for RiftSaw2.1 (which will be the tech preview in SOA 5.1) it may worry users.
Comment 2 Gary Brown 2011-02-24 16:48:52 UTC 
Jeff can you look into this one once the other console changes have been done. Thanks.
Comment 3 Jeff Yu 2011-06-22 04:52:13 UTC 
Link: Added: This issue depends RIFTSAW-392
Comment 4 David Le Sage 2011-08-18 05:59:31 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 5 Len DiMaggio 2011-10-07 17:56:30 UTC 
Cannot recreate the issue in 5.2.0.ER4
Note You need to log in before you can comment on or make changes to this bug.