|Re: BIRT usage of Web Services [message #904614 is a reply to message #904313]
||Tue, 28 August 2012 20:27
| Jason Weathersby
Registered: July 2009
I believe it would be a good idea to open a bugzilla request to help
determine why web service calls were causing threads to hang. BIRT uses
AJAX inside the viewer to call web services on the viewer to run a
report or retrieve a new page when you use page controls etc. If you
are only using charting from the viewer, you could try using the
/preview URL instead of the /run or frameset URL
On 8/28/2012 4:16 AM, Anthony Farrell wrote:
> Many thanks for any information you can provide Jason Weathersby.
> I have a couple of questions with regards to the run time architecture
> of BIRT, specifically with regards to what calls are made when BIRT
> reports are run asynchronously via AJAX calls.
> The background is that a production system was running slowly, it was
> found that some Web Service calls were causing threads to hang or to
> return very slowly (4 hours) to the WebSphere thread pool. The BIRT
> Viewer is deployed as a separate Web Application on WebSphere, with BIRT
> reports being integrated into the Main Application via client side
> aggregation, i.e. the main application embeds BIRT charts via embedded
> URL calls to the BIRT Viewer application..
> For the threads that were running very slowly, the Wepshere log files
> contain stack traces from BIRT where the "axis" package names appeared
> with the BIRT stack trace. My assumption was that BIRT uses some axis
> API's internally to support AJAX or some other purposes, can you confirm
> that no web service calls are made as part of the run time invocation of
> a BIRT report.
> Have you seen any other production system issues similar to the one we
> are seeing?
> We are also reviewing to see if we can allocate a seperate thread pool
> to the BIRT viewer appliction on Webpshere, the idea is to seperate any
> BIRT long running processso that they do not impact the main applicaion
> (which has strict performance requirements).
> Do you know if it is possible to allocate a thread pool to the BIRT
> Viewer web app (even if it uses web services? or does a web services
> call complicate he deployment configuration. Apologies for the array of
> We have verified that there are no BIRT reports that consume or
> reference Web Services, we are currently getting a list of the SQL
> statements that were running on the database at the time to verify that
> there were/are NO very inefficient blocks of SQL with any BIRT reports.
Powered by FUDForum
. Page generated in 0.02164 seconds